6.1.80-ti-arm64-r40 bb.org_defconfig
TI SDK: 09.02.00.009
6.1 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/1c154b1fe4c462d8b383515bb388e289816e4b01...2e423244f8c09173a344e7069f0fe2bdf26cccee
BBDTBS: BeagleBoard-DeviceTrees@342df984
WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/commit/?id=73529a882f83afa26402b18680025334b0215d92
WPANUSB: beagleconnect/linux/wpanusb@6aa9bf65



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>

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

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

We want to enable use of the Android ashmem and binder drivers to
support Anbox, but they should not be built-in as that would waste
resources and increase security attack surface on systems that don't
need them.

Export the currently un-exported symbols they depend on.

We want to enable use of the Android ashmem and binder drivers to
support Anbox, but they should not be built-in as that would waste
resources and increase security attack surface on systems that don't
need them.

- Add a MODULE_LICENSE declaration to ashmem
- Change the Makefiles to build each driver as an object with the
  "_linux" suffix (which is what Anbox expects)
- Change config symbol types to tristate

Update:
In upstream commit 721412ed titled "staging: remove ashmem" the ashmem
driver was removed entirely. Secondary commit message:
"The mainline replacement for ashmem is memfd, so remove the legacy
code from drivers/staging/"
Consequently, the ashmem part of this patch has been removed.

Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>

add of_find_serdev_controller_by_node to obtain a
serdev_controller from the device_node, which
can help if the serdev_device is not described
over device tree and instantiation of the device
happens from a different driver, for the same purpose
an option to not delete an empty serdev controller
is added.

Signed-off-by: Vaishnav M A <vaishnav@beagleboard.org>
Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>

This externalizes and exports the symbol
of_find_spi_controller_by_node() from the SPI core akin to how
of_find_i2c_adapter_by_node() is already available. As we will
need this also for non-dynamic OF setups, we move it under a
CONFIG_OF check.

Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>

Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>

Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>

Lets drive Sierra clock output and workaround a TIFS/DM bug for now.

Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

"PM runtime functions" has been added in sdhci-omap driver in 5.16
f433e8aa ("mmc: sdhci-omap: Implement PM runtime functions") along
with "card power off and enable aggressive PM" 3edf588e
("mmc: sdhci-omap: Allow SDIO card power off and enable aggressive PM").

Since then, the sdhci-omap driver doesn't work using mmc-hs200 mode
due to the tuning values being lost during a pm transition.
See the report on the linux-omap mailing list [1].

As for the sdhci_am654 driver, request a new tuning sequence before
suspend (sdhci_omap_runtime_suspend()), othwerwise the device will
thigger cache flush errors:

  mmc1: cache flush error -110 (ETIMEDOUT)
  mmc1: error -110 doing aggressive suspend

followed by I/O errors produced by fdisk -l /dev/mmcblk1boot1:

  I/O error, dev mmcblk1boot0, sector 64384 op 0x0:(READ) flags 0x80700 phys_seg 1
  prio class 2
  I/O error, dev mmcblk1boot1, sector 64384 op 0x0:(READ) flags 0x80700 phys_seg 1
  prio class 2
  I/O error, dev mmcblk1boot1, sector 64384 op 0x0:(READ) flags 0x0 phys_seg 1
  prio class 2
  Buffer I/O error on dev mmcblk1boot1, logical block 8048, async page read
  I/O error, dev mmcblk1boot0, sector 64384 op 0x0:(READ) flags 0x0 phys_seg 1
  prio class 2
  Buffer I/O error on dev mmcblk1boot0, logical block 8048, async page read

Don't re-tune if auto retuning is supported in HW (when SDHCI_TUNING_MODE_3
is available).

[1] https://lore.kernel.org/all/2e5f1997-564c-44e4-b357-6343e0dae7ab@smile.fr

Fixes: f433e8aa

 ("mmc: sdhci-omap: Implement PM runtime functions")
Signed-off-by: Romain Naour <romain.naour@skf.com>

Add the Greybus host driver for BeaglePlay board by BeagleBoard.org.

The current greybus setup involves running SVC in a user-space
application (GBridge) and using netlink to communicate with kernel
space. GBridge itself uses wpanusb kernel driver, so the greybus messages
travel from kernel space (gb_netlink) to user-space (GBridge) and then
back to kernel space (wpanusb) before reaching CC1352.

This driver directly communicates with CC1352 (running SVC Zephyr
application). Thus, it simplifies the complete greybus setup eliminating
user-space GBridge.

This driver is responsible for the following:
- Start SVC (CC1352) on driver load.
- Send/Receive Greybus messages to/from CC1352 using HDLC over UART.
- Print Logs from CC1352.
- Stop SVC (CC1352) on driver load.

Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>
Link: https://lore.kernel.org/r/20231017101116.178041-3-ayushdevel1325@gmail.com


Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Add DT bindings for Texas Instruments Simplelink CC1352P7 wireless MCU

BeaglePlay has CC1352P7 co-processor connected to the main AM62 (running
Linux) over UART. In the BeagleConnect Technology, CC1352 is responsible
for handling 6LoWPAN communication with beagleconnect freedom nodes as
well as their discovery.

Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Nishanth Menon <nm@ti.com>
Link: https://lore.kernel.org/r/20231017101116.178041-2-ayushdevel1325@gmail.com


Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Reference: rpi-6.1.y
Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

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

"uio" for generic use
"ti,pruss-shmem" for backwards compatibility

the of_id module parameter is still supported to add another id

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

https://openbeagle.org/beagleboard/BeagleBoard-DeviceTrees/-/tree/v6.1.x-Beagle

BeagleBoard-DeviceTrees@342df984


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

https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/commit/?id=73529a882f83afa26402b18680025334b0215d92


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

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

beagleconnect/linux/wpanusb@6aa9bf65


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

The driver drops RX frames due to flags not being cleared during XDP
buffer init. XDP framework provides helper APIs to initialize and
prepare XDP buffer.

Fix the RX frame drops by calling these helper APIs.

Fixes: 78264a12

 ("net: ethernet: ti: icssg_prueth: Add AF_XDP support")
Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
Reviewed-by: Ravi Gunasekaran <r-gunasekaran@ti.com>

Enable I2C5 node for OV10635 camera EVM so that it can standalone work
with the am57xx-beagle-x15.dtb.

Signed-off-by: Sukrut Bellary <sbellary@baylibre.com>

Add missing 'cdns,max-bit-rate' property for mhdp phy. If not
specified, the default value taken is 8100 Mbps which often leads to
phy link training errors like "CR: max swing reached" and eventually
falls back to 1620 Mbps which limits the maximum supported resolution
to 1920x1200 which is way less than what hardware can actually support
theoretically i.e. 4K.
Adding 2700 (as a HACK) instead of 5400 like other platforms as the
latter causes CRTC SYNC LOST issue for 3840x2160@60fps resolution.
So limiting the phy-rate for max resolution of 3840x2160@30fps as it
is better to have a stable low fps than flaky high fps.
The HACK can be removed when 4K@60fps is stable.

Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>

AM69-SK has a 2 Lane PCIe M.2 Key M PCIe instance (PCIe1) and a 1 Lane
PCIe M.2 Key E PCIe instance (PCIe3), both of which are interfaced via a
shared Serdes instance namely Serdes0. Update the Serdes0 link to enable
Multilink PCIe configuration.

Signed-off-by: Dasnavis Sabiya <sabiya.d@ti.com>
Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>

From: Swapnil Jakhade <sjakhade@cadence.com>

Add register sequences for PCIe multilink + USB configuration for 100MHz
reference clock. The same SSC is used for both PCIe and USB.

Signed-off-by: Swapnil Jakhade <sjakhade@cadence.com>
Signed-off-by: Dasnavis Sabiya <sabiya.d@ti.com>
Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>

From: Swapnil Jakhade <sjakhade@cadence.com>

Add register sequences to support multi link PCIe configuration for
100MHz refclk. Maximum two PCIe links are supported.

Signed-off-by: Swapnil Jakhade <sjakhade@cadence.com>
Signed-off-by: Dasnavis Sabiya <sabiya.d@ti.com>
Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>

The CPSW Ethernet Switch on TI's K3 SoCs supports two mechanisms to
timestamp packets received on external ports. The first mechanism which
is currently enabled by the am65-cpsw-nuss driver is that of timestamping
all received packets by setting the "TSTAMP_EN" bit in the CPTS_CONTROL
register, which directs the CPTS module to timestamp all received packets,
followed by passing the timestamps via the DMA descriptors. This mechanism
is responsible for triggering errata i2401:
"CPSW: Host Timestamps Cause CPSW Port to Lock up"

The workaround is to use the second mechanism for timestamping received
packets. The second mechanism utilizes the CPTS Event FIFO that records
timestamps corresponding to certain events, with one such event being the
reception of an Ethernet packet with the EtherType field set to Precision
Time Protocol (PTP).

Hence, switch to the second mechanism to address the errata.

The errata affects all K3 SoCs. Link to errata for AM64x:
https://www.ti.com/lit/er/sprz457h/sprz457h.pdf

Fixes: b1f66a5b

 ("net: ethernet: ti: am65-cpsw-nuss: enable packet timestamping support")
Signed-off-by: Chintan Vankar <c-vankar@ti.com>
Reviewed-by: Ravi Gunasekaran <r-gunasekaran@ti.com>

Add OX05B1S device tree bindings.

Signed-off-by: Abhishek Sharma <abhishek.sharma@ti.com>

OX05B1S is a raw (4x4 RGB-IR bayer) sensor. The LI-OX05B1S-MIPI-137H
module [1]  uses  a LI-FPC22-IPEX-PI [2] adapter cable for connection
with CSI port on the board.

[1] Link: https://www.mouser.com/ProductDetail/Leopard-Imaging/
LI-OX05B1S-MIPI-137H?qs=VJzv269c%252BPbBVMoFtZszhQ%3D%3D

[2] Link: https://www.leopardimaging.com/product/nvidia-jetson-cameras/


nvidia-jetson-orin-nx-camera-kit/li-fpc22-ipex-pi/

Signed-off-by: Abhishek Sharma <abhishek.sharma@ti.com>