This Patch series is an update to the mikroBUS driver
with support for serdev devices and fixed regulator.

RFC v1 Patch : https://lkml.org/lkml/2020/7/24/518

 .
The mikrobus driver is updated to add mikrobus ports from device-tree
overlays, the debug interfaces for adding mikrobus ports through sysFS
is removed, and the driver considers the extended usage of mikrobus
port pins from their standard purposes.

change log:
        v2: support for adding mikroBUS ports from DT overlays,
        remove debug sysFS interface for adding mikrobus ports,
        consider extended pin usage/deviations from mikrobus standard
        specifications,
        use greybus CPort protocol enum instead of new protcol enums
        Fix cases of wrong indendation, ignoring return values, freeing
        allocated resources in case of errors and other style suggestions
        in v1 review.

Signed-off-by: Vaishnav M A <vaishnav@beagleboard.org>

This reverts commit 956b200a

.

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Reference: v5.15.60
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Reference: v5.15.60
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Reference: v5.10.136
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v5.10.x-ti-arm64

https://github.com/beagleboard/BeagleBoard-DeviceTrees/commit/afd78388676fd4888239c688816a806d9ec1f08d


Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=68a8f2f89cc58989bf4c1ade4757b2d5b680127e


Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

https://github.com/cifsd-team/ksmbd/commit/55202de3b8e54a2808421c01e6bb726fb2d7e38f


Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

https://github.com/statropy/bcfserial/commit/aded88429a8a00143596b41f4c1f50d9ae3d4069


Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

From
https://github.com/statropy/wpanusb

https://github.com/statropy/wpanusb/commit/251f0167545bf2dcaa3cad991a59dbf5ab05490a


Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

https://github.com/sfjro/aufs5-standalone/commit/fb85ad143726cce75aa74fffe45103ca935d8680


Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

The following has been done in this commit:
1) Add new nodes definitions for enabling all 6 EHRPWM instances
2) Add rules to disable all the instances for non SK platforms
3) Add rules to enable instances 2 and 3 for the SK platform
4) Add mux settings for enabling channel A from instances 2 and 3
   for the RPi extension header on the SK platform

v4l:vxd-dec:Flushing all the IO buffers and releasing all the held buffers while joing v4l2 job_abort.

This patch does the fulsh operation by releasing all the
locked up buffers in the driver.
It throws the v4l2 harmless traces while trying to
re-release the released buffers.

Signed-off-by: Prashanth Kumar Amai <prashanth.amai@ti.com>

Add DTB overlay file with pin mux details for RPi expansion header
defaulting to GPIO mode

Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>

This is driver allows user-space to attach a DMA-BUF and
receive back its CPU physical address. This is a temporary
solution to allow CMEM like functionality from allocated
buffers. This is a hack and this will be removed when proper
solutions are implemented.

Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>

Driver allowing user-space attaching of dmabuf fd's returning CPU
physical addresses. The reasoning for making this act like a regular
device described by DT is so the virtual device that binds the buffer
can be made to act as if it is out on a bus or behind an IOMMU, for
example.

Add this binding here. This is a hack and marked as such.

Signed-off-by: Gowtham Tammana <g-tammana@ti.com>

Signed-off-by: Keerthy <j-keerthy@ti.com>

Confine the memory map changes into a separate rtos-memory-map.dts
which describes the common memory map for all RTOS remoteprocs.

vision-apps.dtbo uses this and also disables capture and display
related peripherals from Linux so that it can be used by RTOS.

edgeai-apps.dtbo expects these devices to be owned by linux, so
it uses the rtos-memory-map customization only.

Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>

TI-Feature: platform_base
TI-Branch: platform-ti-linux-5.10.y

* 'platform-ti-linux-5.10.y' of ssh://bitbucket.itg.ti.com/lcpdpublicdom/platform

:
  misc: sram: dma-heap-export: Make our dma_buf_ops static
  HACK: dma-buf: heaps: carveout: Make our dma_buf_ops static
  HACK: dma-buf: heaps: carveout: Add support for cached carveout heaps

Signed-off-by: Texas Instruments Auto Merger <lcpd_integration@list.ti.com>

TI-Feature: connectivity
TI-Branch: connectivity-ti-linux-5.10.y

* 'connectivity-ti-linux-5.10.y' of ssh://bitbucket.itg.ti.com/lcpdpublicdom/connectivity

:
  arm64: dts: ti: Disable UHS speed modes on MMCSD1 instance
  dmaengine: ti: k3-udma: Reset UDMA_CHAN_RT byte counters to prevent overflow
  phy: ti: phy-j721e-wiz: stop name conflict if multiple serdes are initialized

Signed-off-by: Texas Instruments Auto Merger <lcpd_integration@list.ti.com>

Aswath Govindraju authored 2 years ago and Vignesh Raghavendra committed 2 years ago

Instabilities were observed on a few SD cards when UHS speed modes were
enabled. Therefore, disable UHS modes by adding the tag no-1-8-v tag, in
sdhci1 device tree node.

Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Tested-by: Bryan Brattlof <bb@ti.com>

Vaishnav Achath authored 2 years ago and Vignesh Raghavendra committed 2 years ago

UDMA_CHAN_RT_*BCNT_REG stores the real-time channel bytecount statistics.
These registers are 32-bit hardware counters and the driver uses these
counters to monitor the operational progress status for a channel, when
transferring more than 4GB of data it was observed that these counters
overflow and completion calculation of a operation gets affected and the
transfer hangs indefinitely.

This commit adds changes to decrease the byte count for every complete
transaction so that these registers never overflow and the proper byte
count statistics is maintained for ongoing transaction by the RT counters.

Earlier uc->bcnt used to maintain a count of the completed bytes at driver
side, since the RT counters maintain the statistics of current transaction
now, the maintenance of uc->bcnt is not necessary.

Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

Matt Ranostay authored 2 years ago and Vignesh Raghavendra committed 2 years ago

When multiple serdes instances are initialized the first will succeed but
additional will conflict over clocks names and probing fails.

Signed-off-by: Matt Ranostay <mranostay@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

This is only used locally, mark static.

Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Andrew Davis <afd@ti.com>

This is only used locally, mark static.

Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Andrew Davis <afd@ti.com>

Remove the "no-map" property from the carveout DT node to have kernel
and userspace mappings cached.

This is currently a hack as I have not yet added a good way to clean
these buffers out of the CPU cache. These should only be used on
io-coherent platforms such as AM65x and J7x.

Signed-off-by: Andrew Davis <afd@ti.com>

TI-Feature: connectivity
TI-Branch: connectivity-ti-linux-5.10.y

* 'connectivity-ti-linux-5.10.y' of ssh://bitbucket.itg.ti.com/lcpdpublicdom/connectivity

: (24 commits)
  Input: ili210x - use one common reset implementation
  Input: ili210x - reduce sample period to 15ms
  Input: ili210x - improve polled sample spacing
  Input: ili210x - special case ili251x sample read out
  Input: ili210x - add ili251x firmware update support
  Input: ili210x - export ili251x version details via sysfs
  Input: ili210x - use resolution from ili251x firmware
  drm/tidss: Add support for AM625 DSS
  dt-bindings: display: ti,am65x-dss: Add am625 dss compatible
  arm64: dts: ti: k3-j7200: Add SR2.0 SERDES changes
  arm64: dts: ti: k3-j7200: Add SR1.0 specific DT Overlays
  phy: cadence-torrent: Add USXGMII(156.25MHz) + SGMII/QSGMII(100MHz) multilink config for TI J7200
  dt-bindings: phy: cadence-torrent: Add compatible for "ti,j7200-serdes-10g"
  phy: ti: phy-j721e-wiz: set PMA_CMN_REFCLK_DIG_DIV based on reflk rate
  phy: cadence-torrent: Add USXGMII(156.25MHz) + SGMII/QSGMII(100MHz) multilink configuration
  phy: cadence-torrent: Add PCIe(100MHz) + USXGMII(156.25MHz) multilink configuration
  phy: cadence-torrent: use key:value pair table for all settings
  phy: ti: phy-j721e-wiz: add support for j7200-wiz-10g
  dt-bindings: phy: ti, phy-j721e-wiz: Add support for ti,j7200-wiz-10g
  dt-bindings: phy: ti, phy-j721e-wiz: deprecate clock MUX nodes
  ...

Signed-off-by: Texas Instruments Auto Merger <lcpd_integration@list.ti.com>

TI-Feature: platform_base
TI-Branch: platform-ti-linux-5.10.y

* 'platform-ti-linux-5.10.y' of ssh://bitbucket.itg.ti.com/lcpdpublicdom/platform

:
  arm64: dts: ti: k3-am625-sk: mark MCU and WKUP watchdogs as reserved
  arm64: dts: ti: k3-am62: add watchdog nodes

Signed-off-by: Texas Instruments Auto Merger <lcpd_integration@list.ti.com>

Marek Vasut authored 2 years ago and Vignesh Raghavendra committed 2 years ago

commit	b26ff913

 upstream

Rename ili251x_hardware_reset() to ili210x_hardware_reset(), change its
parameter from struct device * to struct gpio_desc *, and use it as one
single consistent reset implementation all over the driver. Also increase
the minimum reset duration to 12ms, to make sure the reset is really
within the spec.

Signed-off-by: Marek Vasut <marex@denx.de>
Link: https://lore.kernel.org/r/20220518210423.106555-1-marex@denx.de


Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>