6.6.58-ti-arm64-r19 bb.org_defconfig
TI SDK: 10.01.10
6.6 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/d32074b73785eb57c675cef603517247f5f4f33b...a7758da17c2807e5285d6546b6797aae1d34a7d6
BBDTBS: beagleboard/BeagleBoard-DeviceTrees@48ccd978
WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/commit/?id=f67f40d009199ee75c906f1ac898b38be981a7f7



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>

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

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

beagleboard/BeagleBoard-DeviceTrees@48ccd978


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

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


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>

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

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

Saravana Kannan authored 5 months ago and Vignesh Raghavendra committed 5 months ago

In attempting to optimize fw_devlink runtime, I introduced numerous cycle
detection bugs by foregoing cycle detection logic under specific
conditions. Each fix has further narrowed the conditions for optimization.

It's time to give up on these optimization attempts and just run the cycle
detection logic every time fw_devlink tries to create a device link.

The specific bug report that triggered this fix involved a supplier fwnode
that never gets a device created for it. Instead, the supplier fwnode is
represented by the device that corresponds to an ancestor fwnode.

In this case, fw_devlink didn't do any cycle detection because the cycle
detection logic is only run when a device link is created between the
devices that correspond to the actual consumer and supplier fwnodes.

With this change, fw_devlink will run cycle detection logic even when
creating SYNC_STATE_ONLY proxy device links from a device that is an
ancestor of a consumer fwnode.

Reported-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Closes: https://lore.kernel.org/all/1a1ab663-d068-40fb-8c94-f0715403d276@ideasonboard.com/
Link: https://lore.kernel.org/all/20241030171009.1853340-1-saravanak@google.com/


Fixes: 6442d79d ("driver core: fw_devlink: Improve detection of overlapping cycles")
Tested-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Signed-off-by: Saravana Kannan <saravanak@google.com>
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
Signed-off-by: Swamil Jain <s-jain1@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

Enable mcu domain pinmux by default to be able to access mcu domain
peripherals from main domain.

Signed-off-by: Sai Sree Kartheek Adivi <s-adivi@ti.com>

Enable MTD tests drivers to be built as modules.
This module is required for running NAND performance
MTD tests.

Signed-off-by: Judith Mendez <jm@ti.com>

Commit f3f11cfe ("remoteproc: k3-r5: Acquire mailbox handle during
probe routine") introduced a check in the "k3_r5_rproc_mbox_callback()"
and "k3_r5_rproc_kick()" callbacks, causing them to exit if the remote
core's state is "RPROC_DETACHED". However, the "__rproc_attach()"
function that is responsible for attaching to a remote core, updates the
state of the remote core to "RPROC_ATTACHED" only after invoking
"rproc_start_subdevices()".

The "rproc_start_subdevices()" function triggers the probe of the Virtio
RPMsg devices associated with the remote core, which require that the
"k3_r5_rproc_kick()" and "k3_r5_rproc_mbox_callback()" callbacks are
functional. Hence, drop the check in the callbacks.

Fixes: f3f11cfe ("remoteproc: k3-r5: Acquire mailbox handle during probe routine")
Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>

If controller looses power during PM suspend then re-initialize
it. We use the DEBUG_CFG register to track if controller lost power
or was reset in PM suspend.

Signed-off-by: Roger Quadros <rogerq@kernel.org>

The .get_frame_desc hook is called to propagate information
to the downstream element in the camera pipeline. Support it for
OV5640.

Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com>

Up to 4 TEVI-OV5640 sensors can be connected to AM62P using the
Arducam V3Link (Fusion Mini) daughter board. Add overlays for the
TEVI-OV5640 sensors.

Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com>

Up to 4 OV5640 sensors can be connected to AM62P using the Arducam
V3Link (Fusion Mini) daughter board. Add overlays for the OV5640
sensors.

Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com>

The PHY DLL Master Control Register includes details such as bypass
mode, delay element, and whether the master delay line locks on a half
or full cycle. This register is configured before the PHY Calibration
process by cqspi_phy_set_dll_master(). So, call it in
cqspi_restore_context() for NOR flashes as well.

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

This is the 6.6.58 stable release

* tag 'v6.6.58': (2621 commits)
  Linux 6.6.58
  ALSA: hda/conexant - Use cached pin control for Node 0x1d on HP EliteOne 1000 G2
  nilfs2: propagate directory read errors from nilfs_find_entry()
  selftests: mptcp: remove duplicated variables
  selftests: mptcp: join: test for prohibited MPC to port-based endp
  selftests: mptcp: join: change capture/checksum as bool
  tcp: fix mptcp DSS corruption due to large pmtu xmit
  serial: qcom-geni: fix receiver enable
  serial: qcom-geni: fix dma rx cancellation
  serial: qcom-geni: revert broken hibernation support
  serial: qcom-geni: fix polled console initialisation
  irqchip/sifive-plic: Unmask interrupt in plic_irq_enable()
  irqchip/gic-v4: Don't allow a VMOVP on a dying VPE
  pinctrl: apple: check devm_kasprintf() returned value
  pinctrl: stm32: check devm_kasprintf() returned value
  pinctrl: ocelot: fix system hang on level based interrupts
  x86/bugs: Use code segment selector for VERW operand
  tty: n_gsm: Fix use-after-free in gsm_cleanup_mux
  x86/entry_32: Clear CPU buffers after register restore in NMI return
  x86/entry_32: Do not clobber user EFLAGS.ZF
  ...

Arducam V3Link camera adapter (Tx) is a dedicated board with UB953
serializer, that support RPi 22-pin compatible sensors. It is shipped
with an IMX219 sensor. [1]

Add overlays for interfacing these boards with the 4x different RX ports
on second V3Link mini fusion board connected to CSI Port 1 in a  dual
V3Link mini fusion board configuration. AM68 SK, AM69 SK and J722S SK
can support dual V3Link mini fusion board up to 8 cameras.

[1]: https://docs.arducam.com/V3Link-Camera-Solution/V3Link-Camera-Solution-on-TI-Platform/Introduction/



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

Fixes bug where GPIO state would reset upon resume from low power. GPIO
state should be maintained through system suspend/resume. The bug stems
from disabling IO isolation which would reset the GPIO state. Fix is
calling GPIO resume before disabling IO isolation in ti_sci_resume.

Labeled as HACK because davinci_gpio_resume is exposed and is being called
within ti_sci_resume. A flag has been added to the davinci_gpio_controller
to track if it has already restored context in order to not restore context
twice when resuming. In the process of finding a better way to fix the bug
where each driver is independent of each other.

Signed-off-by: Kendall Willis <k-willis@ti.com>
Reviewed-by: Dhruva Gole <d-gole@ti.com>