6.6.32-ti-rt-arm64-r12 bb.org_defconfig
TI SDK: 10.00.08
6.6 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/6de6e418c80edfbe08f4a5f851c721bd60c0123b...db88712931433e92a5f73cec57c82c5c7ebee593
BBDTBS: BeagleBoard-DeviceTrees@f93301b4
RT: patch-6.6.32-rt32.patch.xz
WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/commit/?id=bf55ed481432cbd91e05b54c5f7bccd687c69bb7
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>

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: Robert Nelson <robertcnelson@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>

Commit 85e6b8d4

 ("HACK: drm/bridge: ite-it66121: Add drm_connector
support") and related patches seem to have broken HPD. hack the same
in.

NOTE: This hack is not perfect, if the HDMI is not plugged in at the
very start of the boot, we seem to manually need to trigger the
following (path to display depends on platform and configuration)

echo connected|sudo tee /sys/class/drm/card0-HDMI-A-1/status

Signed-off-by: Jared McArthur <j-mcarthur@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>

The it66121 and replaced with it66122. The part is register compatible
with what we have for it66121. pid 0x0612 on the 66121 device to
0x0622 on the 66122 device, but I guess it makes sense to someone.

Signed-off-by: Nishanth Menon <nm@ti.com>

commit ba2d3e67

 upstream

If a specific design doesn't wire IT66121's interrupt signal output pin up
to the display controller side, then we should not register the interrupt
handler. Such a decision is valid usage, as we can fall back to polling
mode. So, don't make the assumption that a specific board always supports
HPD. Carry out a sanity check on 'client->irq' before using it, fall back
to polling mode if client->irq < 0 is true. Such a design increases the
overall flexibility.

Signed-off-by: Sui Jingfeng <sui.jingfeng@linux.dev>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Link: https://lore.kernel.org/r/20240316160536.1051513-1-sui.jingfeng@linux.dev


Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20240316160536.1051513-1-sui.jingfeng@linux.dev


[nm@ti.com: Backport from upstream next-20240502]
Signed-off-by: Nishanth Menon <nm@ti.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>

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

beagleboard/BeagleBoard-DeviceTrees@f93301b4


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

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


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

patch-6.6.32-rt32.patch.xz

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>

Add bootloader-backdoor-gpios which is required for enabling bootloader
backdoor for flashing firmware to cc1352p7.

Also fix the incorrect reset-gpio.

Signed-off-by: Ayush Singh <ayush@beagleboard.org>

bootloader-backdoor-gpio (along with reset-gpio) is used to enable
bootloader backdoor for flashing new firmware.

The pin and pin level to enable bootloader backdoor is configured using
the following CCFG variables in cc1352p7:
- SET_CCFG_BL_CONFIG_BL_PIN_NO
- SET_CCFG_BL_CONFIG_BL_LEVEL

Acked-by: Conor Dooley <conor.dooley@microchip.com>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
Signed-off-by: Ayush Singh <ayush@beagleboard.org>

BeagleBoard.org BeagleY-AI is an easy to use, affordable open source
hardware single board computer based on the Texas Instruments AM67A,
which features a quad-core 64-bit Arm CPU subsystem, 2 general-purpose
digital-signal-processors (DSP) and matrix-multiply-accelerators (MMA),
GPU, vision and deep learning accelerators, and multiple Arm Cortex-R5
cores for low-power, low-latency GPIO control.

https://beagley-ai.org/
https://openbeagle.org/beagley-ai/beagley-ai



Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
Reviewed-by: Roger Quadros <rogerq@kernel.org>
Reviewed-by: Jared McArthur <j-mcarthur@ti.com>
Link: https://lore.kernel.org/r/20240829213929.48540-2-robertcnelson@gmail.com


Signed-off-by: Nishanth Menon <nm@ti.com>

This board is based on ti,j722s family using the am67a variation.

https://beagley-ai.org/
https://openbeagle.org/beagley-ai/beagley-ai



Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
Reviewed-by: Jared McArthur <j-mcarthur@ti.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Link: https://lore.kernel.org/r/20240829213929.48540-1-robertcnelson@gmail.com


Signed-off-by: Nishanth Menon <nm@ti.com>

The C7xv deep learning engine dsp core in AM62A has a local reset line
from power state controller. In the absence of using the local reset,
it is in an unknown state and when the module is turned on, CPU starts
executing and may go into a bad state. Set local reset to 'true' for
AM62A, so that the remote proc driver properly asserts the local reset
before enabling the module to load the firmware. And it is deasserted
after firmware load is complete to start the core.

Signed-off-by: Hari Nagalla <hnagalla@ti.com>

update the compatible string for c7xv deep learning DSP core in J722S.

Signed-off-by: Hari Nagalla <hnagalla@ti.com>

J722S uses the C7xv DSP based deep learning engine similar to AM62A,
but the reset and module enable integration in the SoC is little
different. It does not have local reset from power state controller.
So, add a new compatible string to distinguish this difference.

Signed-off-by: Hari Nagalla <hnagalla@ti.com>

J722S uses the C7xv DSP based deep learning engine similar to AM62A,
but the reset and module enable integration in the SoC is little
different. It does not have local reset from power state controller.
So, add a new compatible string to distinguish this difference.

Signed-off-by: Hari Nagalla <hnagalla@ti.com>

Move cqspi_restore_context() to cqspi_runtime_resume(), so that it can
be called for both system resume and runtime resume.

Also, add a call to cqspi_phy_set_dll_master() from
cqspi_restore_context() for SDR mode.

Signed-off-by: Santhosh Kumar K <s-k6@ti.com>

After the PHY calibration process, store the final tuning point in
the flash private data's phy_setting (f_pdata->phy_setting)

Signed-off-by: Santhosh Kumar K <s-k6@ti.com>

PHY DLL Master Control Register contains the details like bypass mode,
delay element, master delay line locks on full/half cycle, which is
configured before the calibration process.

Move the configuration part to cqspi_phy_set_dll_master() to reuse it
during runtime_resume restore_contest call.

Signed-off-by: Santhosh Kumar K <s-k6@ti.com>

This is no longer needed as we have PHY enabled for NAND SDR read and
write and PHY can operate at 166 MHz.

This reverts commit a34768f6

.

Signed-off-by: Prasanth Babu Mantena <p-mantena@ti.com>
Acked-by: Santhosh Kumar K <s-k6@ti.com>

Revert back the frequency settings that were done to work with OSPI NAND
8s mode. As we have enabled PHY for NAND read and write, we can now
operate at 166 MHz.

Reverts commit 742bc197

 ("arm64: dts: ti: k3-j784s4: Update Nand node for Octal SDR")

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

Revert back the frequency settings that were done to work with OSPI NAND
8s mode. As we have enabled PHY for NAND read and write, we can now
operate at 166 MHz.

Reverts commit dc50d257

 ("arm64: dts: ti: k3-j721s2: Update Nand node for Octal SDR")

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

Add status register check by polling the busy bit. This returns the
completion status of the operation and data can be read only after this
step.

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

Depending on the probing order of dma vs ospi, dma failure is seen when
ospi controller probes first and checks for available dma channel and
fails. This patch fixes it by sending EPROBE_DEFER, which helps acquire
dma channel after the dma controller probes.

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

Introduce minimal devicetree initializing only UART and SD capability
for minimal platform board bring-up. SD features are reduced to 3.3V
signaling and 25 MHz legacy mode.

Signed-off-by: Logan Bristol <l-bristol@ti.com>