This series switches all Amlogic SoCs to use the new PWM controller
binding. The main benefits of the new binding are:
- the pwm controller driver now picks the best possible clock to
  achieve the most accurate pwm output
- board.dts don't have to know about the pwm clock inputs anymore (as
  the driver picks the best one automatically)
- new SoCs only need a new compatible string but no pwm-meson driver
  changes, assuming only the clock inputs differ from older IP
  revisions

This silences the following warning(s) at boot (for each pwm
controller instance):
  using obsolete compatible, please consider updating dt

I have tested this on two devices:
- meson8b: odroidc1 (boots fine and cycling through all CPU
  frequencies and thus voltages works fine)
- meson-sm1: x96-air-gbit (boots and the rtw8822cs SDIO card is
  detected, so the 32kHz clock for the SDIO card works)

Since I cannot test all devices I'm asking for this series to be
applied so the Kernel CI board farm can help verify it works on all
boards available there.


Martin Blumenstingl (5):
  ARM: dts: amlogic: meson8: switch to the new PWM controller binding
  ARM: dts: amlogic: meson8b: switch to the new PWM controller binding
  arm64: dts: amlogic: gx: switch to the new PWM controller binding
  arm64: dts: amlogic: axg: switch to the new PWM controller binding
  arm64: dts: amlogic: g12: switch to the new PWM controller binding

 arch/arm/boot/dts/amlogic/meson8.dtsi         | 18 ++++++++--
 arch/arm/boot/dts/amlogic/meson8b-ec100.dts   |  2 --
 arch/arm/boot/dts/amlogic/meson8b-mxq.dts     |  2 --
 .../arm/boot/dts/amlogic/meson8b-odroidc1.dts |  2 --
 arch/arm/boot/dts/amlogic/meson8b.dtsi        | 18 ++++++++--
 arch/arm64/boot/dts/amlogic/meson-axg.dtsi    | 24 +++++++++++---
 .../boot/dts/amlogic/meson-g12-common.dtsi    | 33 ++++++++++++++++---
 .../boot/dts/amlogic/meson-g12a-fbx8am.dts    |  4 ---
 .../dts/amlogic/meson-g12a-radxa-zero.dts     |  4 ---
 .../boot/dts/amlogic/meson-g12a-sei510.dts    |  4 ---
 .../boot/dts/amlogic/meson-g12a-u200.dts      |  2 --
 .../boot/dts/amlogic/meson-g12a-x96-max.dts   |  4 ---
 .../amlogic/meson-g12b-a311d-libretech-cc.dts |  2 --
 .../dts/amlogic/meson-g12b-bananapi-cm4.dtsi  |  4 ---
 .../boot/dts/amlogic/meson-g12b-bananapi.dtsi |  4 ---
 .../dts/amlogic/meson-g12b-khadas-vim3.dtsi   |  4 ---
 .../boot/dts/amlogic/meson-g12b-odroid.dtsi   |  4 ---
 .../dts/amlogic/meson-g12b-radxa-zero2.dts    |  8 -----
 .../boot/dts/amlogic/meson-g12b-w400.dtsi     |  6 ----
 .../dts/amlogic/meson-gx-libretech-pc.dtsi    |  6 ----
 .../boot/dts/amlogic/meson-gx-p23x-q20x.dtsi  |  2 --
 arch/arm64/boot/dts/amlogic/meson-gx.dtsi     |  8 ++---
 .../boot/dts/amlogic/meson-gxbb-nanopi-k2.dts |  2 --
 .../dts/amlogic/meson-gxbb-nexbox-a95x.dts    |  2 --
 .../boot/dts/amlogic/meson-gxbb-p20x.dtsi     |  2 --
 .../boot/dts/amlogic/meson-gxbb-vega-s95.dtsi |  2 --
 .../boot/dts/amlogic/meson-gxbb-wetek.dtsi    |  2 --
 arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi   | 25 ++++++++++++++
 .../boot/dts/amlogic/meson-gxl-s805x-p241.dts |  2 --
 .../meson-gxl-s905w-jethome-jethub-j80.dts    |  2 --
 .../meson-gxl-s905x-hwacom-amazetv.dts        |  2 --
 .../amlogic/meson-gxl-s905x-khadas-vim.dts    |  2 --
 .../amlogic/meson-gxl-s905x-nexbox-a95x.dts   |  2 --
 .../dts/amlogic/meson-gxl-s905x-p212.dtsi     |  2 --
 arch/arm64/boot/dts/amlogic/meson-gxl.dtsi    | 25 ++++++++++++++
 .../dts/amlogic/meson-gxm-khadas-vim2.dts     |  4 ---
 .../boot/dts/amlogic/meson-gxm-rbox-pro.dts   |  2 --
 .../amlogic/meson-libretech-cottonwood.dtsi   |  6 ----
 .../boot/dts/amlogic/meson-sm1-ac2xx.dtsi     |  6 ----
 .../boot/dts/amlogic/meson-sm1-bananapi.dtsi  |  2 --
 .../dts/amlogic/meson-sm1-khadas-vim3l.dts    |  2 --
 .../boot/dts/amlogic/meson-sm1-odroid.dtsi    |  2 --
 .../boot/dts/amlogic/meson-sm1-sei610.dts     |  6 ----
 43 files changed, 132 insertions(+), 135 deletions(-)

-- 
2.47.1

On 27/12/2024 22:25, Martin Blumenstingl wrote:
> This series switches all Amlogic SoCs to use the new PWM controller
> binding. The main benefits of the new binding are:
> - the pwm controller driver now picks the best possible clock to
>    achieve the most accurate pwm output
> - board.dts don't have to know about the pwm clock inputs anymore (as
>    the driver picks the best one automatically)
> - new SoCs only need a new compatible string but no pwm-meson driver
>    changes, assuming only the clock inputs differ from older IP
>    revisions
> 
> This silences the following warning(s) at boot (for each pwm
> controller instance):
>    using obsolete compatible, please consider updating dt
> 
> I have tested this on two devices:
> - meson8b: odroidc1 (boots fine and cycling through all CPU
>    frequencies and thus voltages works fine)
> - meson-sm1: x96-air-gbit (boots and the rtw8822cs SDIO card is
>    detected, so the 32kHz clock for the SDIO card works)
> 
> Since I cannot test all devices I'm asking for this series to be
> applied so the Kernel CI board farm can help verify it works on all
> boards available there.

Ack I'll appply them for the next release so it stays in -next for a while.

For the serie:
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>

Thanks!
Neil

> 
> 
> Martin Blumenstingl (5):
>    ARM: dts: amlogic: meson8: switch to the new PWM controller binding
>    ARM: dts: amlogic: meson8b: switch to the new PWM controller binding
>    arm64: dts: amlogic: gx: switch to the new PWM controller binding
>    arm64: dts: amlogic: axg: switch to the new PWM controller binding
>    arm64: dts: amlogic: g12: switch to the new PWM controller binding
> 
>   arch/arm/boot/dts/amlogic/meson8.dtsi         | 18 ++++++++--
>   arch/arm/boot/dts/amlogic/meson8b-ec100.dts   |  2 --
>   arch/arm/boot/dts/amlogic/meson8b-mxq.dts     |  2 --
>   .../arm/boot/dts/amlogic/meson8b-odroidc1.dts |  2 --
>   arch/arm/boot/dts/amlogic/meson8b.dtsi        | 18 ++++++++--
>   arch/arm64/boot/dts/amlogic/meson-axg.dtsi    | 24 +++++++++++---
>   .../boot/dts/amlogic/meson-g12-common.dtsi    | 33 ++++++++++++++++---
>   .../boot/dts/amlogic/meson-g12a-fbx8am.dts    |  4 ---
>   .../dts/amlogic/meson-g12a-radxa-zero.dts     |  4 ---
>   .../boot/dts/amlogic/meson-g12a-sei510.dts    |  4 ---
>   .../boot/dts/amlogic/meson-g12a-u200.dts      |  2 --
>   .../boot/dts/amlogic/meson-g12a-x96-max.dts   |  4 ---
>   .../amlogic/meson-g12b-a311d-libretech-cc.dts |  2 --
>   .../dts/amlogic/meson-g12b-bananapi-cm4.dtsi  |  4 ---
>   .../boot/dts/amlogic/meson-g12b-bananapi.dtsi |  4 ---
>   .../dts/amlogic/meson-g12b-khadas-vim3.dtsi   |  4 ---
>   .../boot/dts/amlogic/meson-g12b-odroid.dtsi   |  4 ---
>   .../dts/amlogic/meson-g12b-radxa-zero2.dts    |  8 -----
>   .../boot/dts/amlogic/meson-g12b-w400.dtsi     |  6 ----
>   .../dts/amlogic/meson-gx-libretech-pc.dtsi    |  6 ----
>   .../boot/dts/amlogic/meson-gx-p23x-q20x.dtsi  |  2 --
>   arch/arm64/boot/dts/amlogic/meson-gx.dtsi     |  8 ++---
>   .../boot/dts/amlogic/meson-gxbb-nanopi-k2.dts |  2 --
>   .../dts/amlogic/meson-gxbb-nexbox-a95x.dts    |  2 --
>   .../boot/dts/amlogic/meson-gxbb-p20x.dtsi     |  2 --
>   .../boot/dts/amlogic/meson-gxbb-vega-s95.dtsi |  2 --
>   .../boot/dts/amlogic/meson-gxbb-wetek.dtsi    |  2 --
>   arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi   | 25 ++++++++++++++
>   .../boot/dts/amlogic/meson-gxl-s805x-p241.dts |  2 --
>   .../meson-gxl-s905w-jethome-jethub-j80.dts    |  2 --
>   .../meson-gxl-s905x-hwacom-amazetv.dts        |  2 --
>   .../amlogic/meson-gxl-s905x-khadas-vim.dts    |  2 --
>   .../amlogic/meson-gxl-s905x-nexbox-a95x.dts   |  2 --
>   .../dts/amlogic/meson-gxl-s905x-p212.dtsi     |  2 --
>   arch/arm64/boot/dts/amlogic/meson-gxl.dtsi    | 25 ++++++++++++++
>   .../dts/amlogic/meson-gxm-khadas-vim2.dts     |  4 ---
>   .../boot/dts/amlogic/meson-gxm-rbox-pro.dts   |  2 --
>   .../amlogic/meson-libretech-cottonwood.dtsi   |  6 ----
>   .../boot/dts/amlogic/meson-sm1-ac2xx.dtsi     |  6 ----
>   .../boot/dts/amlogic/meson-sm1-bananapi.dtsi  |  2 --
>   .../dts/amlogic/meson-sm1-khadas-vim3l.dts    |  2 --
>   .../boot/dts/amlogic/meson-sm1-odroid.dtsi    |  2 --
>   .../boot/dts/amlogic/meson-sm1-sei610.dts     |  6 ----
>   43 files changed, 132 insertions(+), 135 deletions(-)
>

> On 28 Dec 2024, at 1:25 am, Martin Blumenstingl <martin.blumenstingl@googlemail.com> wrote:
> 
> This series switches all Amlogic SoCs to use the new PWM controller
> binding. The main benefits of the new binding are:
> - the pwm controller driver now picks the best possible clock to
>  achieve the most accurate pwm output
> - board.dts don't have to know about the pwm clock inputs anymore (as
>  the driver picks the best one automatically)
> - new SoCs only need a new compatible string but no pwm-meson driver
>  changes, assuming only the clock inputs differ from older IP
>  revisions
> 
> This silences the following warning(s) at boot (for each pwm
> controller instance):
>  using obsolete compatible, please consider updating dt
> 
> I have tested this on two devices:
> - meson8b: odroidc1 (boots fine and cycling through all CPU
>  frequencies and thus voltages works fine)
> - meson-sm1: x96-air-gbit (boots and the rtw8822cs SDIO card is
>  detected, so the 32kHz clock for the SDIO card works)
> 
> Since I cannot test all devices I'm asking for this series to be
> applied so the Kernel CI board farm can help verify it works on all
> boards available there.

This series breaks Broadcom BT on the GXBB/GXM/G12B boards in my
current test rotation. I’m running Linux 6.14.2 with this series
backported for testing. This is generally what’s seen in dmesg:

VIM2:~ # dmesg | grep -i blue
[    8.659535] Bluetooth: Core ver 2.22
[    8.659681] NET: Registered PF_BLUETOOTH protocol family
[    8.659690] Bluetooth: HCI device and connection manager initialized
[    8.659712] Bluetooth: HCI socket layer initialized
[    8.659721] Bluetooth: L2CAP socket layer initialized
[    8.659742] Bluetooth: SCO socket layer initialized
[    8.724898] Bluetooth: HCI UART driver ver 2.3
[    8.724953] Bluetooth: HCI UART protocol H4 registered
[    8.725106] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    8.725434] Bluetooth: HCI UART protocol Broadcom registered
[    8.725502] Bluetooth: HCI UART protocol QCA registered
[    8.725559] Bluetooth: HCI UART protocol AML registered
[    8.966727] Bluetooth: hci0: Frame reassembly failed (-84)
[    8.966772] Bluetooth: hci0: Frame reassembly failed (-84)
[   11.148157] Bluetooth: hci0: command 0xfc18 tx timeout
[   11.148383] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
[   11.148446] Bluetooth: hci0: Failed to set baudrate
[   13.281510] Bluetooth: hci0: command 0xfc18 tx timeout
[   13.281576] Bluetooth: hci0: BCM: Reset failed (-110)

This is also visible on a VIM3 board in kernelci (Linux 6.15.-rc2):

https://dashboard.kernelci.org/test/maestro%3A67fd3cda3328e043e96da230?l=true

[ 3.954267] Bluetooth: hci0: Frame reassembly failed (-84)
[ 4.040555] Bluetooth: hci0: Frame reassembly failed (-84)

(linux-firmware and thus kernelci is lacking Broadcom BT firmwares so
later messages that result from trying to load fw aren’t seen)

With the series reverted:

VIM2:~ # dmesg | grep -i blue
[    8.452570] Bluetooth: Core ver 2.22
[    8.452695] NET: Registered PF_BLUETOOTH protocol family
[    8.452703] Bluetooth: HCI device and connection manager initialized
[    8.452724] Bluetooth: HCI socket layer initialized
[    8.452735] Bluetooth: L2CAP socket layer initialized
[    8.452752] Bluetooth: SCO socket layer initialized
[    8.530077] Bluetooth: HCI UART driver ver 2.3
[    8.530113] Bluetooth: HCI UART protocol H4 registered
[    8.530387] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    8.530902] Bluetooth: HCI UART protocol Broadcom registered
[    8.530983] Bluetooth: HCI UART protocol QCA registered
[    8.531037] Bluetooth: HCI UART protocol AML registered
[    8.917685] Bluetooth: hci0: BCM: chip id 101
[    8.918000] Bluetooth: hci0: BCM: features 0x2f
[    8.919526] Bluetooth: hci0: BCM4354A2
[    8.919560] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0000
[    8.941837] Bluetooth: hci0: BCM4356A2 'brcm/BCM4356A2.hcd' Patch
[    9.831321] Bluetooth: hci0: BCM: features 0x2f
[    9.832884] Bluetooth: hci0: BCM4356 37.4MHz AMPAK AP6356-0055
[    9.832902] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0266
[    9.856044] Bluetooth: MGMT ver 1.23

An SML544TW board (S905D) with a QCA9377 chip is not affected by the
changes so the scope appears to be limited to Broadcom BT.

I’ve also noticed that VIM3 and the SML5442TW have device-tree items
like max-speed, clocks, clock-names defined, but adding these to e.g.
a WeTek Play2 board or removing from VIM3 doesn’t change anything.

Christian

On Sun, Apr 20, 2025 at 9:45 AM Christian Hewitt
<christian@hewittfamily.org.uk> wrote:
>
> > On 28 Dec 2024, at 1:25 am, Martin Blumenstingl <martin.blumenstingl@googlemail.com> wrote:
> >
> > This series switches all Amlogic SoCs to use the new PWM controller
> > binding. The main benefits of the new binding are:
> > - the pwm controller driver now picks the best possible clock to
> >  achieve the most accurate pwm output
> > - board.dts don't have to know about the pwm clock inputs anymore (as
> >  the driver picks the best one automatically)
> > - new SoCs only need a new compatible string but no pwm-meson driver
> >  changes, assuming only the clock inputs differ from older IP
> >  revisions
> >
> > This silences the following warning(s) at boot (for each pwm
> > controller instance):
> >  using obsolete compatible, please consider updating dt
> >
> > I have tested this on two devices:
> > - meson8b: odroidc1 (boots fine and cycling through all CPU
> >  frequencies and thus voltages works fine)
> > - meson-sm1: x96-air-gbit (boots and the rtw8822cs SDIO card is
> >  detected, so the 32kHz clock for the SDIO card works)
> >
> > Since I cannot test all devices I'm asking for this series to be
> > applied so the Kernel CI board farm can help verify it works on all
> > boards available there.
>
> This series breaks Broadcom BT on the GXBB/GXM/G12B boards in my
> current test rotation. I’m running Linux 6.14.2 with this series
> backported for testing. This is generally what’s seen in dmesg:
>
> VIM2:~ # dmesg | grep -i blue
> [    8.659535] Bluetooth: Core ver 2.22
> [    8.659681] NET: Registered PF_BLUETOOTH protocol family
> [    8.659690] Bluetooth: HCI device and connection manager initialized
> [    8.659712] Bluetooth: HCI socket layer initialized
> [    8.659721] Bluetooth: L2CAP socket layer initialized
> [    8.659742] Bluetooth: SCO socket layer initialized
> [    8.724898] Bluetooth: HCI UART driver ver 2.3
> [    8.724953] Bluetooth: HCI UART protocol H4 registered
> [    8.725106] Bluetooth: HCI UART protocol Three-wire (H5) registered
> [    8.725434] Bluetooth: HCI UART protocol Broadcom registered
> [    8.725502] Bluetooth: HCI UART protocol QCA registered
> [    8.725559] Bluetooth: HCI UART protocol AML registered
> [    8.966727] Bluetooth: hci0: Frame reassembly failed (-84)
> [    8.966772] Bluetooth: hci0: Frame reassembly failed (-84)
> [   11.148157] Bluetooth: hci0: command 0xfc18 tx timeout
> [   11.148383] Bluetooth: hci0: BCM: failed to write update baudrate (-110)
> [   11.148446] Bluetooth: hci0: Failed to set baudrate
> [   13.281510] Bluetooth: hci0: command 0xfc18 tx timeout
> [   13.281576] Bluetooth: hci0: BCM: Reset failed (-110)
>
> This is also visible on a VIM3 board in kernelci (Linux 6.15.-rc2):
>
> https://dashboard.kernelci.org/test/maestro%3A67fd3cda3328e043e96da230?l=true
>
> [ 3.954267] Bluetooth: hci0: Frame reassembly failed (-84)
> [ 4.040555] Bluetooth: hci0: Frame reassembly failed (-84)
>
> (linux-firmware and thus kernelci is lacking Broadcom BT firmwares so
> later messages that result from trying to load fw aren’t seen)
>
> With the series reverted:
>
> VIM2:~ # dmesg | grep -i blue
> [    8.452570] Bluetooth: Core ver 2.22
> [    8.452695] NET: Registered PF_BLUETOOTH protocol family
> [    8.452703] Bluetooth: HCI device and connection manager initialized
> [    8.452724] Bluetooth: HCI socket layer initialized
> [    8.452735] Bluetooth: L2CAP socket layer initialized
> [    8.452752] Bluetooth: SCO socket layer initialized
> [    8.530077] Bluetooth: HCI UART driver ver 2.3
> [    8.530113] Bluetooth: HCI UART protocol H4 registered
> [    8.530387] Bluetooth: HCI UART protocol Three-wire (H5) registered
> [    8.530902] Bluetooth: HCI UART protocol Broadcom registered
> [    8.530983] Bluetooth: HCI UART protocol QCA registered
> [    8.531037] Bluetooth: HCI UART protocol AML registered
> [    8.917685] Bluetooth: hci0: BCM: chip id 101
> [    8.918000] Bluetooth: hci0: BCM: features 0x2f
> [    8.919526] Bluetooth: hci0: BCM4354A2
> [    8.919560] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0000
> [    8.941837] Bluetooth: hci0: BCM4356A2 'brcm/BCM4356A2.hcd' Patch
> [    9.831321] Bluetooth: hci0: BCM: features 0x2f
> [    9.832884] Bluetooth: hci0: BCM4356 37.4MHz AMPAK AP6356-0055
> [    9.832902] Bluetooth: hci0: BCM4356A2 (001.003.015) build 0266
> [    9.856044] Bluetooth: MGMT ver 1.23
>
> An SML544TW board (S905D) with a QCA9377 chip is not affected by the
> changes so the scope appears to be limited to Broadcom BT.
>
> I’ve also noticed that VIM3 and the SML5442TW have device-tree items
> like max-speed, clocks, clock-names defined, but adding these to e.g.
> a WeTek Play2 board or removing from VIM3 doesn’t change anything.
Thanks for reporting this - a fix has been submitted here: [0]


[0] https://lore.kernel.org/linux-amlogic/20250420164801.330505-1-martin.blumenstingl@googlemail.com/T/#t

Hi,

On Fri, 27 Dec 2024 22:25:09 +0100, Martin Blumenstingl wrote:
> This series switches all Amlogic SoCs to use the new PWM controller
> binding. The main benefits of the new binding are:
> - the pwm controller driver now picks the best possible clock to
>   achieve the most accurate pwm output
> - board.dts don't have to know about the pwm clock inputs anymore (as
>   the driver picks the best one automatically)
> - new SoCs only need a new compatible string but no pwm-meson driver
>   changes, assuming only the clock inputs differ from older IP
>   revisions
> 
> [...]

Thanks, Applied to https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git (v6.15/arm64-dt)

[3/5] arm64: dts: amlogic: gx: switch to the new PWM controller binding
      https://git.kernel.org/amlogic/c/12abaac5a70994490e565249dcffbb5c329b30bd
[4/5] arm64: dts: amlogic: axg: switch to the new PWM controller binding
      https://git.kernel.org/amlogic/c/77747dbb11466d5ac2ee11a260e8de0b65f3fd1c
[5/5] arm64: dts: amlogic: g12: switch to the new PWM controller binding
      https://git.kernel.org/amlogic/c/06c993691a2fdcabc43053a8fdd813cdeef516c4

These changes has been applied on the intermediate git tree [1].

The v6.15/arm64-dt branch will then be sent via a formal Pull Request to the Linux SoC maintainers
for inclusion in their intermediate git branches in order to be sent to Linus during
the next merge window, or sooner if it's a set of fixes.

In the cases of fixes, those will be merged in the current release candidate
kernel and as soon they appear on the Linux master branch they will be
backported to the previous Stable and Long-Stable kernels [2].

The intermediate git branches are merged daily in the linux-next tree [3],
people are encouraged testing these pre-release kernels and report issues on the
relevant mailing-lists.

If problems are discovered on those changes, please submit a signed-off-by revert
patch followed by a corrective changeset.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
[3] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

-- 
Neil

Hi,

On Fri, 27 Dec 2024 22:25:09 +0100, Martin Blumenstingl wrote:
> This series switches all Amlogic SoCs to use the new PWM controller
> binding. The main benefits of the new binding are:
> - the pwm controller driver now picks the best possible clock to
>   achieve the most accurate pwm output
> - board.dts don't have to know about the pwm clock inputs anymore (as
>   the driver picks the best one automatically)
> - new SoCs only need a new compatible string but no pwm-meson driver
>   changes, assuming only the clock inputs differ from older IP
>   revisions
> 
> [...]

Thanks, Applied to https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git (v6.15/arm-dt)

[1/5] ARM: dts: amlogic: meson8: switch to the new PWM controller binding
      https://git.kernel.org/amlogic/c/d352e8fc91526bdbb70468e8dea13581b905891f
[2/5] ARM: dts: amlogic: meson8b: switch to the new PWM controller binding
      https://git.kernel.org/amlogic/c/39786592bfdd92b64a68283fa896e108ca9822de

These changes has been applied on the intermediate git tree [1].

The v6.15/arm-dt branch will then be sent via a formal Pull Request to the Linux SoC maintainers
for inclusion in their intermediate git branches in order to be sent to Linus during
the next merge window, or sooner if it's a set of fixes.

In the cases of fixes, those will be merged in the current release candidate
kernel and as soon they appear on the Linux master branch they will be
backported to the previous Stable and Long-Stable kernels [2].

The intermediate git branches are merged daily in the linux-next tree [3],
people are encouraged testing these pre-release kernels and report issues on the
relevant mailing-lists.

If problems are discovered on those changes, please submit a signed-off-by revert
patch followed by a corrective changeset.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
[3] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

-- 
Neil