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

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

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

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

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

https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/tree/v5.10.x-ti-unified

https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/commit/cbad981e7f6bcdd2fc5dd6e0b757f12ba585c6c1


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

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


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

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

https://github.com/cifsd-team/ksmbd/commit/c5864a9e60afd9bd8b66f524f9985df778480c66


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/aufs-standalone/commit/2c2dfeb062b323e07fd1e3a0d1c3eb816da25a8b


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>

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>

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: connectivity
TI-Branch: connectivity-ti-linux-5.10.y

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

:
  PCI: j721e: correct PCIe lane selection mask
  net: ethernet: ti: am65-cpsw: set correct devlink flavour for unused ports

Signed-off-by: LCPD 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-j721s2: Fix the interrupt ranges property for main & wkup gpio intr

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

The parent's input irq number is wrongly subtracted with 32 instead of
using the exact numbers in:

https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721s2/interrupt_cfg.html



The GPIO interrupts are not working because of that. The toggling works
fine but interrupts are not firing. Fix the parent's input irq that
specifies the base for parent irq.

Tested for MAIN_GPIO0_6 interrupt on the j721s2 EVM.

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

TI-Feature: rpmsg
TI-Branch: rpmsg-ti-linux-5.10.y-intg

* 'rpmsg-ti-linux-5.10.y-intg' of git://git.ti.com/rpmsg/rpmsg

:
  arm4: dts: ti: Reduce reserved area for R5F by 1Mb

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

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

PCIe lane mask should be based on the maximum number of lanes and not the
currently selected lane count, since we have no idea what the bootloader may
have initialized to this register.

Reported-by: Vignesh Raghavendra <vigneshr@ti.com>
Fixes: 3c97d831

 ("PCI: j721e: correct lane count mask based on lane numbers")
Signed-off-by: Matt Ranostay <mranostay@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

Matthias Schiffer authored 2 years ago and Vignesh Raghavendra committed 2 years ago

commit 7e777b1b upstream.

am65_cpsw_nuss_register_ndevs() skips calling devlink_port_type_eth_set()
for ports without assigned netdev, triggering the following warning when
DEVLINK_PORT_TYPE_WARN_TIMEOUT elapses after 3600s:

    Type was not set for devlink port.
    WARNING: CPU: 0 PID: 129 at net/core/devlink.c:8095 devlink_port_type_warn+0x18/0x30

Fixes: 3e8e73d1

 ("net: ethernet: ti: am65-cpsw: Fix devlink port register sequence")
Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

In the previous version of devicetree, reserved area for wakeup
R5F was stating from 0x9db00000, so to provide compatibility
with older version of devicetree being used with new wakeup R5F
firmware, the wakeup R5F reserved area is reduced by 1Mb and that
1Mb is moved to MCU M4F reserved area.

Signed-off-by: Devarsh Thakkar <devarsht@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

:
  spi: spi-omap2-mcspi: Use EOW interrupt for completion when DMA enabled
  dmaengine: ti: k3-udma: Respond TX done if DMA_PREP_INTERRUPT is not requested
  arm64: dts: ti: k3-j784s4-evm: Add eMMC mmc0 support
  arm64: dts: ti: k3-j784s4-evm: Add OSPI0 flash support

Signed-off-by: LCPD 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

:
  ti_config_fragments: v8_audio_display: Trim out defaults
  ti_config_fragments: audio_display: Move option pruning into prune.cfg
  ti_config_fragments: Clone audio_display.cfg for ARMv8
  ti_config_fragments: v8_baseport: Trim out defaults
  ti_config_fragments: baseport: Trim out defaults
  ti_config_fragments: baseport: Move option pruning into prune.cfg
  ti_config_fragments: real_time: Remove explicit page size setting

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

With the same justification as the previous patches in this series.
Move option pruning into the prune.cfg file and remove the remaining
option additions that do not change defaults.

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

While pruning is useful for making small and fast-building kernels for
our SDK releases, these are not so useful for general purpose or distro
kernels where these options might still be needed.

Move all the pruning from audio_display.cfg into multi_v7_prune.cfg.

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

The one audio_display.cfg is used in both v7 and v8 maps. This prevents
more fine-grain pruning. For example v8 does not need OMAPDRM, but we
cannot remove it without removing it also from v7.

Make a clone of audio_display.cfg for use in the v8 map.

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

All carried changes to the upstream kernel that are needed to boot it on
TI platforms should be considered tech debt. Changes to the default ARMv8
configuration are no different. We need to reduced these over time by
working to get these options in the upstream defconfig. To start to see
where we stand today, lets remove all the options that do not change the
upstream default. Then anything remaining in this file should be
investigated for appropriateness in upstream and sent accordingly.

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

All carried changes to the upstream kernel that are needed to boot it on
TI platforms should be considered tech debt. Changes to the default ARMv8
configuration are no different. We need to reduced these over time by
working to get these options in the upstream defconfig. To start to see
where we stand today, lets remove all the options that do not change the
upstream default. Then anything remaining in this file should be
investigated for appropriateness in upstream and sent accordingly.

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

While pruning is useful for making small and fast-building kernels for
our SDK releases, these are not so useful for general purpose or distro
kernels where these options might still be needed.

For these cases one would only want to apply our additions to gain
support for our platforms but not trim out support for others. To make
this separation clean, move all the pruning from baseport.cfg into
multi_v7_prune.cfg.

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

4K pages are now the default, no need to explicitly set the same.

Signed-off-by: Andrew Davis <afd@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

:
  dmaengine: k3-udma: Add system suspend/resume support
  arm64: dts: ti: k3-j784s4-*: Add GPU node
  arm64: dts: ti: Add support for AM62A7-SK
  arm64: dts: ti: Introduce AM62A7 family of SoCs
  dt-bindings: pinctrl: k3: Introduce pinmux definitions for AM62A
  dt-bindings: arm: ti: Add bindings for AM62A7 SoC
  dt-bindings: arm: ti: Rearrange IOPAD macros alphabetically

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

The K3 platforms configure the DMA resources with the
help of the TI's System Firmware's Device Manager(DM)
over TISCI. The group of DMA related Resource Manager[1]
TISCI messages includes: INTA, RINGACC, UDMAP, and PSI-L.
This configuration however, does not persist in the DM
after leaving from Suspend-to-RAM state. We have to restore
the DMA channel configuration over TISCI for all configured
channels when entering suspend.

The TISCI resource management calls for each DMA type (UDMA,
PKTDMA, BCDMA) happen in device_free_chan_resources() and
device_alloc_chan_resources(). In pm_suspend() we store
the current udma_chan_config for channels that still have
attached clients and call device_free_chan_resources().
In pm_resume() restore the udma_channel_config from backup
and call device_alloc_chan_resources() for those channels.
Drivers like CPSW do their own DMA resource management,
so use the late system suspend/resume hooks.

[1] https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/index.html#resource-management-rm



Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
[g-vlaev@ti.com: Add udma_chan_config backup]
[g-vlaev@ti.com: Supend only channels with clients]
Signed-off-by: Georgi Vlaev <g-vlaev@ti.com>