From: sashiko-bot@kernel.org
To: "Cunhao Lu" <1579567540@qq.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
mfd@lists.linux.dev, linux-gpio@vger.kernel.org,
linux-serial@vger.kernel.org, linux-phy@lists.infradead.org,
linux-usb@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com,
lee@kernel.org
Subject: Re: [PATCH 26/27] arm64: dts: rockchip: Add RK3572 SoC
Date: Thu, 22 Oct 2026 16:13:24 +0000 [thread overview]
Message-ID: <sashiko-outbox-181790@kernel.org> (raw)
In-Reply-To: <20261022-add-board-ok3572-c-v1-26-0b0fd85a31ee@qq.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] arm64: dts: rockchip: duplicate pdmm1-clk*-idle node names in rk3572-pinctrl
- [Medium] arm64: dts: rockchip: missing pixel clock pin in rk3572 rgb3x8_pins_m1
--
commit 187a63c766133c9d7856a97e9575a5f3703cf119
Author: Cunhao Lu <1579567540@qq.com>
arm64: dts: rockchip: Add RK3572 SoC
This commit adds the base device tree files for the Rockchip rk3572,
including the operating points, pinctrl definitions, and peripheral nodes.
> diff --git a/arch/arm64/boot/dts/rockchip/rk3572-pinctrl.dtsi b/arch/arm64/boot/dts/rockchip/rk3572-pinctrl.dtsi
> new file mode 100644
> index 0000000000000..8440feea419b9
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3572-pinctrl.dtsi
> @@ -0,0 +1,3935 @@
[ ... ]
> + pdm {
> + /omit-if-no-ref/
> + pdmm0_clk0_idle: pdmm0-clk0-idle {
> + rockchip,pins =
> + <0 RK_PC4 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm0_clk1_idle: pdmm0-clk1-idle {
> + rockchip,pins =
> + <0 RK_PC3 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm1_clk0_idle: pdmm1-clk0-idle {
> + rockchip,pins =
> + <2 RK_PB2 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm1_clk1_idle: pdmm1-clk1-idle {
> + rockchip,pins =
> + <2 RK_PB4 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm2_clk0_idle: pdmm1-clk0-idle {
> + rockchip,pins =
> + <1 RK_PC1 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm2_clk1_idle: pdmm1-clk1-idle {
> + rockchip,pins =
> + <1 RK_PD5 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm3_clk0_idle: pdmm1-clk0-idle {
> + rockchip,pins =
> + <2 RK_PC5 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm3_clk1_idle: pdmm1-clk1-idle {
> + rockchip,pins =
> + <2 RK_PC7 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm4_clk0_idle: pdmm1-clk0-idle {
> + rockchip,pins =
> + <3 RK_PB1 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm4_clk1_idle: pdmm1-clk1-idle {
> + rockchip,pins =
> + <3 RK_PA7 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> + };
[Severity: Medium]
Should the node names for pdmm2_clk0_idle, pdmm3_clk0_idle, and
pdmm4_clk0_idle under the pdm node in rk3572-pinctrl.dtsi be
pdmm2-clk0-idle, pdmm3-clk0-idle, and pdmm4-clk0-idle (and likewise for the
clk1-idle nodes), rather than repeating pdmm1-clk0-idle and pdmm1-clk1-idle?
Because these sibling nodes share the same node names under the pdm parent,
dtc merges them into a single pdmm1-clk0-idle node and a single
pdmm1-clk1-idle node, overwriting rockchip,pins with the values from
pdmm4_clk0_idle and pdmm4_clk1_idle when any of the pdmm1, pdmm2, or pdmm3
idle clock pinctrl phandles are referenced.
[ ... ]
> + vo {
[ ... ]
> + /omit-if-no-ref/
> + rgb3x8_pins_m0: rgb3x8-pins-m0 {
> + rockchip,pins =
> + <3 RK_PD7 3 &pcfg_pull_none>,
> + <3 RK_PD0 3 &pcfg_pull_none>,
> + <3 RK_PC7 3 &pcfg_pull_none>,
> + <3 RK_PC6 3 &pcfg_pull_none>,
> + <3 RK_PC5 3 &pcfg_pull_none>,
> + <3 RK_PC4 3 &pcfg_pull_none>,
> + <3 RK_PC1 3 &pcfg_pull_none>,
> + <3 RK_PC0 3 &pcfg_pull_none>,
> + <3 RK_PB7 3 &pcfg_pull_none>,
> + <3 RK_PD4 3 &pcfg_pull_none>,
> + <3 RK_PD5 3 &pcfg_pull_none>,
> + <3 RK_PD6 3 &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + rgb3x8_pins_m1: rgb3x8-pins-m1 {
> + rockchip,pins =
> + <3 RK_PB6 3 &pcfg_pull_none>,
> + <3 RK_PB5 3 &pcfg_pull_none>,
> + <3 RK_PB4 3 &pcfg_pull_none>,
> + <3 RK_PB0 3 &pcfg_pull_none>,
> + <3 RK_PA7 3 &pcfg_pull_none>,
> + <3 RK_PA6 3 &pcfg_pull_none>,
> + <3 RK_PA5 3 &pcfg_pull_none>,
> + <3 RK_PA4 3 &pcfg_pull_none>,
> + <3 RK_PD4 3 &pcfg_pull_none>,
> + <3 RK_PD5 3 &pcfg_pull_none>,
> + <3 RK_PD6 3 &pcfg_pull_none>;
> + };
[Severity: Medium]
Is rgb3x8_pins_m1 under the vo node in rk3572-pinctrl.dtsi missing the
<3 RK_PD7 3 &pcfg_pull_none> pixel clock pin?
rgb3x8_pins_m0 and the other display pin groups (vo_lcdc_pins, bt1120_pins,
bt656_pins, rgb565_pins, rgb666_pins, and rgb888_pins) all include this pin
alongside their data and sync pins, whereas rgb3x8_pins_m1 only lists the 8
data pins and 3 sync pins.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261022-add-board-ok3572-c-v1-0-0b0fd85a31ee@qq.com?part=26
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Cunhao Lu" <1579567540@qq.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
mfd@lists.linux.dev, linux-gpio@vger.kernel.org,
linux-serial@vger.kernel.org, linux-phy@lists.infradead.org,
linux-usb@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com,
lee@kernel.org
Subject: Re: [PATCH 26/27] arm64: dts: rockchip: Add RK3572 SoC
Date: Thu, 22 Oct 2026 16:13:24 +0000 [thread overview]
Message-ID: <sashiko-outbox-181790@kernel.org> (raw)
In-Reply-To: <20261022-add-board-ok3572-c-v1-26-0b0fd85a31ee@qq.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] arm64: dts: rockchip: duplicate pdmm1-clk*-idle node names in rk3572-pinctrl
- [Medium] arm64: dts: rockchip: missing pixel clock pin in rk3572 rgb3x8_pins_m1
--
commit 187a63c766133c9d7856a97e9575a5f3703cf119
Author: Cunhao Lu <1579567540@qq.com>
arm64: dts: rockchip: Add RK3572 SoC
This commit adds the base device tree files for the Rockchip rk3572,
including the operating points, pinctrl definitions, and peripheral nodes.
> diff --git a/arch/arm64/boot/dts/rockchip/rk3572-pinctrl.dtsi b/arch/arm64/boot/dts/rockchip/rk3572-pinctrl.dtsi
> new file mode 100644
> index 0000000000000..8440feea419b9
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3572-pinctrl.dtsi
> @@ -0,0 +1,3935 @@
[ ... ]
> + pdm {
> + /omit-if-no-ref/
> + pdmm0_clk0_idle: pdmm0-clk0-idle {
> + rockchip,pins =
> + <0 RK_PC4 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm0_clk1_idle: pdmm0-clk1-idle {
> + rockchip,pins =
> + <0 RK_PC3 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm1_clk0_idle: pdmm1-clk0-idle {
> + rockchip,pins =
> + <2 RK_PB2 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm1_clk1_idle: pdmm1-clk1-idle {
> + rockchip,pins =
> + <2 RK_PB4 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm2_clk0_idle: pdmm1-clk0-idle {
> + rockchip,pins =
> + <1 RK_PC1 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm2_clk1_idle: pdmm1-clk1-idle {
> + rockchip,pins =
> + <1 RK_PD5 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm3_clk0_idle: pdmm1-clk0-idle {
> + rockchip,pins =
> + <2 RK_PC5 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm3_clk1_idle: pdmm1-clk1-idle {
> + rockchip,pins =
> + <2 RK_PC7 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm4_clk0_idle: pdmm1-clk0-idle {
> + rockchip,pins =
> + <3 RK_PB1 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + pdmm4_clk1_idle: pdmm1-clk1-idle {
> + rockchip,pins =
> + <3 RK_PA7 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> + };
[Severity: Medium]
Should the node names for pdmm2_clk0_idle, pdmm3_clk0_idle, and
pdmm4_clk0_idle under the pdm node in rk3572-pinctrl.dtsi be
pdmm2-clk0-idle, pdmm3-clk0-idle, and pdmm4-clk0-idle (and likewise for the
clk1-idle nodes), rather than repeating pdmm1-clk0-idle and pdmm1-clk1-idle?
Because these sibling nodes share the same node names under the pdm parent,
dtc merges them into a single pdmm1-clk0-idle node and a single
pdmm1-clk1-idle node, overwriting rockchip,pins with the values from
pdmm4_clk0_idle and pdmm4_clk1_idle when any of the pdmm1, pdmm2, or pdmm3
idle clock pinctrl phandles are referenced.
[ ... ]
> + vo {
[ ... ]
> + /omit-if-no-ref/
> + rgb3x8_pins_m0: rgb3x8-pins-m0 {
> + rockchip,pins =
> + <3 RK_PD7 3 &pcfg_pull_none>,
> + <3 RK_PD0 3 &pcfg_pull_none>,
> + <3 RK_PC7 3 &pcfg_pull_none>,
> + <3 RK_PC6 3 &pcfg_pull_none>,
> + <3 RK_PC5 3 &pcfg_pull_none>,
> + <3 RK_PC4 3 &pcfg_pull_none>,
> + <3 RK_PC1 3 &pcfg_pull_none>,
> + <3 RK_PC0 3 &pcfg_pull_none>,
> + <3 RK_PB7 3 &pcfg_pull_none>,
> + <3 RK_PD4 3 &pcfg_pull_none>,
> + <3 RK_PD5 3 &pcfg_pull_none>,
> + <3 RK_PD6 3 &pcfg_pull_none>;
> + };
> +
> + /omit-if-no-ref/
> + rgb3x8_pins_m1: rgb3x8-pins-m1 {
> + rockchip,pins =
> + <3 RK_PB6 3 &pcfg_pull_none>,
> + <3 RK_PB5 3 &pcfg_pull_none>,
> + <3 RK_PB4 3 &pcfg_pull_none>,
> + <3 RK_PB0 3 &pcfg_pull_none>,
> + <3 RK_PA7 3 &pcfg_pull_none>,
> + <3 RK_PA6 3 &pcfg_pull_none>,
> + <3 RK_PA5 3 &pcfg_pull_none>,
> + <3 RK_PA4 3 &pcfg_pull_none>,
> + <3 RK_PD4 3 &pcfg_pull_none>,
> + <3 RK_PD5 3 &pcfg_pull_none>,
> + <3 RK_PD6 3 &pcfg_pull_none>;
> + };
[Severity: Medium]
Is rgb3x8_pins_m1 under the vo node in rk3572-pinctrl.dtsi missing the
<3 RK_PD7 3 &pcfg_pull_none> pixel clock pin?
rgb3x8_pins_m0 and the other display pin groups (vo_lcdc_pins, bt1120_pins,
bt656_pins, rgb565_pins, rgb666_pins, and rgb888_pins) all include this pin
alongside their data and sync pins, whereas rgb3x8_pins_m1 only lists the 8
data pins and 3 sync pins.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261022-add-board-ok3572-c-v1-0-0b0fd85a31ee@qq.com?part=26
next prev parent reply other threads:[~2026-10-22 16:13 UTC|newest]
Thread overview: 188+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 16:10 [PATCH 00/27] rockchip: Add RK3572 and Forlinx OK3572-C support Cunhao Lu via B4 Relay
2026-10-21 16:10 ` Cunhao Lu
2026-10-21 16:10 ` Cunhao Lu via B4 Relay
2026-10-21 16:10 ` Cunhao Lu via B4 Relay
2026-10-21 16:10 ` [PATCH 01/27] dt-bindings: clock: rockchip: Add RK3572 CRU Cunhao Lu via B4 Relay
2026-10-21 16:10 ` Cunhao Lu
2026-10-21 16:10 ` Cunhao Lu via B4 Relay
2026-10-21 16:10 ` Cunhao Lu via B4 Relay
2026-10-22 16:12 ` sashiko-bot
2026-10-21 16:10 ` [PATCH 02/27] dt-bindings: power: rockchip: Add RK3572 power domains Cunhao Lu via B4 Relay
2026-10-21 16:10 ` Cunhao Lu
2026-10-21 16:10 ` Cunhao Lu via B4 Relay
2026-10-21 16:10 ` Cunhao Lu via B4 Relay
2026-10-22 16:12 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 03/27] dt-bindings: soc: rockchip: Add RK3572 PMU and GRF Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:12 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 04/27] dt-bindings: mfd: syscon: Add RK3572 QoS register compatible Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 05/27] dt-bindings: pinctrl: rockchip: Add RK3572 Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 06/27] dt-bindings: gpio: rockchip: Add RK3572 GPIO banks Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 07/27] clk: rockchip: Add RK3572 clock and reset support Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 22:26 ` Heiko Stübner
2026-10-21 22:26 ` Heiko Stübner
2026-10-21 22:26 ` Heiko Stübner
2026-10-22 6:09 ` Cunhao Lu
2026-10-22 6:09 ` Cunhao Lu
2026-10-22 6:09 ` Cunhao Lu
2026-10-22 7:38 ` Heiko Stübner
2026-10-22 7:38 ` Heiko Stübner
2026-10-22 7:38 ` Heiko Stübner
2026-10-22 8:31 ` Cunhao Lu
2026-10-22 8:31 ` Cunhao Lu
2026-10-22 8:31 ` Cunhao Lu
2026-10-22 6:01 ` kernel test robot
2026-10-22 16:13 ` sashiko-bot
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 08/27] pinctrl: rockchip: Add RK3572 support Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 09/27] gpio: rockchip: Add RK3572 GPIO support Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-22 16:13 ` sashiko-bot
2026-10-28 10:16 ` Bartosz Golaszewski
2026-10-28 10:16 ` Bartosz Golaszewski
2026-10-28 10:16 ` Bartosz Golaszewski
2026-10-21 16:11 ` [PATCH 10/27] pmdomain: rockchip: Add RK3572 boot peripheral domains Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 11/27] dt-bindings: i2c: rk3x: Add RK3572 Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-26 22:34 ` Andi Shyti
2026-10-26 22:34 ` Andi Shyti
2026-10-26 22:34 ` Andi Shyti
2026-10-21 16:11 ` [PATCH 12/27] dt-bindings: serial: snps-dw-apb-uart: " Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 13/27] dt-bindings: mmc: rockchip: Add RK3572 controllers Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 14/27] dt-bindings: net: rockchip-dwmac: Add RK3572 Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 17:14 ` Andrew Lunn
2026-10-21 17:14 ` Andrew Lunn
2026-10-21 17:14 ` Andrew Lunn
2026-10-22 6:03 ` Cunhao Lu
2026-10-22 6:03 ` Cunhao Lu
2026-10-22 6:03 ` Cunhao Lu
2026-10-22 16:13 ` sashiko-bot
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 15/27] dt-bindings: thermal: rockchip: " Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 16/27] net: stmmac: dwmac-rk: Add RK3572 support Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 17:09 ` Andrew Lunn
2026-10-21 17:09 ` Andrew Lunn
2026-10-21 17:09 ` Andrew Lunn
2026-10-22 5:33 ` Cunhao Lu
2026-10-22 5:33 ` Cunhao Lu
2026-10-22 5:33 ` Cunhao Lu
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 17/27] thermal: rockchip: " Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 18/27] dt-bindings: phy: rockchip-inno-usb2: Add RK3572 Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 19/27] dt-bindings: phy: rockchip-naneng-combphy: " Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 20/27] dt-bindings: usb: rockchip: Add RK3572 DWC3 controller Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 21/27] phy: rockchip-inno-usb2: Add RK3572 support Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 22/27] phy: rockchip-naneng-combphy: " Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 23/27] usb: dwc3: Configure RK3572 PIPE port before discovery Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 24/27] mmc: dw_mmc-rockchip: Keep RK3572 NVM domain powered Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-27 0:53 ` Shawn Lin
2026-10-27 0:53 ` Shawn Lin
2026-10-27 0:53 ` Shawn Lin
2026-10-27 8:14 ` Cunhao Lu
2026-10-27 8:14 ` Cunhao Lu
2026-10-27 8:14 ` Cunhao Lu
2026-10-21 16:11 ` [PATCH 25/27] dt-bindings: arm: rockchip: Add Forlinx OK3572-C Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 26/27] arm64: dts: rockchip: Add RK3572 SoC Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot [this message]
2026-10-22 16:13 ` sashiko-bot
2026-10-21 16:11 ` [PATCH 27/27] arm64: dts: rockchip: Add initial support for Forlinx OK3572-C Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-21 16:11 ` Cunhao Lu via B4 Relay
2026-10-22 16:13 ` sashiko-bot
2026-10-21 23:00 ` [PATCH 00/27] rockchip: Add RK3572 and Forlinx OK3572-C support Shawn Lin
2026-10-21 23:00 ` Shawn Lin
2026-10-21 23:00 ` Shawn Lin
2026-10-22 6:37 ` Cunhao Lu
2026-10-22 6:37 ` Cunhao Lu
2026-10-22 6:37 ` Cunhao Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sashiko-outbox-181790@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=1579567540@qq.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.