6.6.32-ti-arm64-r6 bb.org_defconfig
TI SDK: 10.00.03
6.6 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/51479baa13b77d89091fef60bac4a5707870b15a...4bd0d44f69cbda913ca7fcb809ae0fa682416b14
BBDTBS: beagleboard/BeagleBoard-DeviceTrees@53659df8
WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/commit/?id=f8ef7da3d44ce3a003b3dea5ab0d5301931bff14
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: Nishanth Menon <nm@ti.com>

When frequency is not exact, the debug information is informative,
but not necessarily informational to the end user. Lower the severity
down.

Fixes: 3e9bee11

 ("ASoC: davinci-mcasp: Restructure the davinci_mcasp_calc_clk_div()")

Signed-off-by: Nishanth Menon <nm@ti.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>

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

beagleboard/BeagleBoard-DeviceTrees@53659df8


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

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


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

ieee802154_xmit_hw_error() is the right helper to call when a transmission
has failed for a non-determined (and probably not IEEE802.15.4 specific)
reason. Let's use this helper instead of open-coding it.

Based on: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.5-rc1&id=35f34ee102a5b2376f4b4700ac017b8f2770e754



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>

This reverts commit c2eb70fa.

Proper solution is already part of
commit cde91a89

 ("remoteproc: core: Add DMA-BUF attachment
interface to cdev")

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

edgeai_rtos_ipc_memory_region: Reserved for Interprocessor communication
between DM R5, MCU R5, C7x.

edgeai_memory_region: Reserved for remote core logging, allocating
descriptor structs (tiovx based) which are shared between remote cores.

edgeai_shared_region: Reserved for I/O buffers for e.g. to carry
framebuffer data.

edgeai_core_heaps: Reserved for heap memory allocation from remote cores
such as C7x, DM R5F and MCU R5F and also scratch memory usage for C7x.

Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
Reviewed-by: Rahul T R <r-ravikumar@ti.com>
Acked-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

Add DTB overlay to enable EHRPWM 2 and 3 and add pinmux
to bring them out on RPi expansion header

Signed-off-by: Rahul T R <r-ravikumar@ti.com>
Tested-by: Shreyash Sinha <s-sinha@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

Dhruva Gole authored 9 months ago and Vignesh Raghavendra committed 9 months ago

Saving all the required phy settings like the rx, tx and read_delay
comes in handy when latter on suspend and resuming the controller is
needed. It is now possible to easily restore the phy_settings during
resume simply by using the f_pdata's phy_setting

Signed-off-by: Dhruva Gole <d-gole@ti.com>
Signed-off-by: Santhosh Kumar K <s-k6@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

Mark BCDMA CSI RX as real-time traffic using OrderID 8/15.
This ensures CSI traffic takes dedicated RT path towards DDR ensuring
proper priority when under competing system load.

Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Signed-off-by: Jai Luthra <j-luthra@ti.com>

gpio-14 for exp2 is hogged for audio making it busy for mux1 mux-controller
causing can-phy3 probe failure.
So, instead of hogging the gpio as high, mark its idle-state as high in
mux1 node so that it can be used by mux-controller and McASP clock signals
are routed as well irrespective of the mcan being used or not.

Fixes: 100e2c90

 ("arm64: dts: ti: k3-j784s4-evm: Enable analog audio support")
Signed-off-by: Jayesh Choudhary <j-choudhary@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 Davis <afd@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Signed-off-by: Rahul T R <r-ravikumar@ti.com>

With werror flag, compilation will fail due to platform device
not declared. So add platform device header file.

Cc: Mattijs Korpershoek <mkorpershoek@ti.com>
Cc: Guillaume La Roque <glaroque@ti.com>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>

Fusion application board [1] can be used to connect multiple FPDLink-III
based sensors to TI EVMs. Upto 12x sensors can simultaneously stream
over the three CSI RX ports on J784S4/AM69, add an overlay to support
the fusion board connected to CSI port 2(CSI_AUX port) on AM69 SK to
enable 12 camera applications with AM69 SK.

Link: https://svtronics.com/portfolio/evm577pfusion-v1-0-fusion/

 [1]

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

Arducam's UC-A09 is a V3Link "mini" fusion board. [1]
It can be used to connect multiple V3Link (and FPD-III)
based cameras to TI EVMs using a single 22-pin FFC (4-lane)
CSI2 connector. Add an overlay to support it on AM68 SK, same
overlay can be used with AM69 SK as well.

[1] https://www.arducam.com/downloads/datasheet/Arducam_V3Link_Datasheet.pdf



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

Fusion application board [1] can be used to connect multiple FPDLink-III
based sensors to TI EVMs. Up to 8x sensors can simultaneously stream
over the two CSI RX ports on J721E SK, AM68 SK and AM69 SK. CSI2RX
connectivity is same on all three platforms, so the same fusion overlay
can be reused.

Link: https://svtronics.com/portfolio/evm577pfusion-v1-0-fusion/

 [1]

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

Add OV5640 overlays for AM69 SK which have MIPI CSI
connector to which LI OV5640 camera can be attached for
CSI2RX based streaming.

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

Add OV5640 overlays for AM68 SK which have MIPI CSI
connector to which LI OV5640 camera can be attached for
CSI2RX based streaming.

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

Add OV5640 overlays for J721E SK which have MIPI CSI
connector to which LI OV5640 camera can be attached for
CSI2RX based streaming.

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

J722S has an OSPI NAND flash on its SOM connected the OSPI0 instance,
add dts node for the flash. This NAND flash is muxed with OSPI NOR flash
through a physical switch (SW3.1). SW3.1 when set as 1 connects the NAND
flash to the SoC.

Signed-off-by: Prasanth Babu Mantena <p-mantena@ti.com>

J721s2 has an OSPI NAND flash on its SOM connected the OSPI0 instance,
add dts node for the flash. This NAND flash is muxed with OSPI NOR flash
through a physical switch (SW3.1). SW3.1 when set as 1 connects the NAND
flash to the SoC.

Signed-off-by: Prasanth Babu Mantena <p-mantena@ti.com>