From: Kever Yang <kever.yang@rock-chips.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: heiko@sntech.de, linux-kernel@vger.kernel.org,
Jonas Karlman <jonas@kwiboo.se>,
Detlev Casanova <detlev.casanova@collabora.com>,
Dragan Simic <dsimic@manjaro.org>, Yao Zi <ziyao@disroot.org>,
Junhao Xie <bigfoot@classfun.cn>,
devicetree@vger.kernel.org,
Elaine Zhang <zhangqing@rock-chips.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
Jamie Iles <jamie@jamieiles.com>,
Guenter Roeck <linux@roeck-us.net>,
Frank Wang <frank.wang@rock-chips.com>,
linux-rockchip@lists.infradead.org,
linux-watchdog@vger.kernel.org, Jimmy Hon <honyuenkwun@gmail.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-arm-kernel@lists.infradead.org,
Finley Xiao <finley.xiao@rock-chips.com>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
FUKAUMI Naoki <naoki@radxa.com>,
Diederik de Haas <didi.debian@cknow.org>,
Shresth Prasad <shresthprasad7@gmail.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Johan Jonker <jbx6244@gmail.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v5 0/6] rockchip: Add rk3562 SoC and evb support
Date: Wed, 7 May 2025 10:02:12 +0800 [thread overview]
Message-ID: <a5da2a81-6944-4d4e-a582-a24f8340efc5@rock-chips.com> (raw)
In-Reply-To: <174655575165.2171034.16453137338500014976.robh@kernel.org>
On 2025/5/7 02:23, Rob Herring (Arm) wrote:
> On Tue, 06 May 2025 10:57:09 +0800, Kever Yang wrote:
>> Patch series V5 remove [v4 1/7] which had taken by Manivannan, and move
>> scmi-shmem from soc node to reserved memory.
>>
>> Patch series V4 remove patches already landed, and remove dts nodes for
>> modules still under review.
>>
>> This patch set adds rk3562 SoC and its evb support.
>>
>> I have split out patches need driver change for different subsystem.
>> And all the modules with dt-binding document update in this patch set
>> do not need any driver change. I put them together to make it clear we
>> have a new SoC and board to use the new compatible. Please pick up the
>> patch for your subsystem, or please let me know if the patch has to
>> send separate.
>>
>> Test with USB, PCIe, EMMC, SD Card.
>>
>> This patch set is base on the patch set for rk3576 evb1 support.
>>
>> V3:
>> https://lore.kernel.org/linux-rockchip/20250227111913.2344207-1-kever.yang@rock-chips.com/
>> V2:
>> https://lore.kernel.org/linux-rockchip/b4df8a73-58a2-4765-a9e4-3513cb2bc720@rock-chips.com/T/
>>
>>
>> Changes in v5:
>> - Collect review tag
>> - Update scmi-shmem from soc to reserved memory
>>
>> Changes in v4:
>> - Collect ack tag
>> - Collect ack tag
>> - Collect ack tag
>> - remove gmac and otp nodes
>> - remove gmac nodes
>>
>> Changes in v3:
>> - Collect reveiw tag
>> - Collect the Acked-by tag
>> - remove i2c/serial/spi alias
>> - add soc node
>>
>> Changes in v2:
>> - Update in sort order
>> - remove grf in cru
>> - Update some properties order
>>
>> Finley Xiao (2):
>> arm64: dts: rockchip: add core dtsi for RK3562 Soc
>> arm64: dts: rockchip: Add RK3562 evb2 devicetree
>>
>> Kever Yang (4):
>> dt-bindings: watchdog: Add rk3562 compatible
>> dt-bindings: rockchip: pmu: Add rk3562 compatible
>> dt-bindings: soc: rockchip: Add rk3562 syscon compatibles
>> dt-bindings: arm: rockchip: Add rk3562 evb2 board
>>
>> .../devicetree/bindings/arm/rockchip.yaml | 5 +
>> .../devicetree/bindings/arm/rockchip/pmu.yaml | 2 +
>> .../devicetree/bindings/soc/rockchip/grf.yaml | 7 +
>> .../bindings/watchdog/snps,dw-wdt.yaml | 1 +
>> arch/arm64/boot/dts/rockchip/Makefile | 1 +
>> .../boot/dts/rockchip/rk3562-evb2-v10.dts | 488 ++++
>> .../boot/dts/rockchip/rk3562-pinctrl.dtsi | 2352 +++++++++++++++++
>> arch/arm64/boot/dts/rockchip/rk3562.dtsi | 1270 +++++++++
>> 8 files changed, 4126 insertions(+)
>> create mode 100644 arch/arm64/boot/dts/rockchip/rk3562-evb2-v10.dts
>> create mode 100644 arch/arm64/boot/dts/rockchip/rk3562-pinctrl.dtsi
>> create mode 100644 arch/arm64/boot/dts/rockchip/rk3562.dtsi
>>
>> --
>> 2.25.1
>>
>>
>>
>
> My bot found new DTB warnings on the .dts files added or changed in this
> series.
>
> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
> are fixed by another series. Ultimately, it is up to the platform
> maintainer whether these warnings are acceptable or not. No need to reply
> unless the platform maintainer has comments.
>
> If you already ran DT checks and didn't see these error(s), then
> make sure dt-schema is up to date:
>
> pip3 install dtschema --upgrade
>
>
> This patch series was applied (using b4) to base:
> Base: attempting to guess base-commit...
> Base: tags/next-20250506 (exact match)
>
> If this is not the correct base, please add 'base-commit' tag
> (or use b4 which does this automatically)
>
> New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/rockchip/' for 20250506025715.33595-1-kever.yang@rock-chips.com:
>
> arch/arm64/boot/dts/rockchip/rk3562-evb2-v10.dtb: /soc/usb2-phy@ff740000: failed to match any schema with compatible: ['rockchip,rk3562-usb2phy']
The usb2-phy patch set[1] has send and got reviewed tag from Heiko for a
long time, what should I do for that patch?
Thanks,
- Kever
[1]
https://patchwork.kernel.org/project/linux-phy/patch/20250415050005.52773-2-kever.yang@rock-chips.com/
>
>
>
>
>
>
prev parent reply other threads:[~2025-05-07 2:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 2:57 Kever Yang
2025-05-06 2:57 ` [PATCH v5 1/6] dt-bindings: watchdog: Add rk3562 compatible Kever Yang
2025-05-06 2:57 ` [PATCH v5 2/6] dt-bindings: rockchip: pmu: " Kever Yang
2025-05-06 2:57 ` [PATCH v5 3/6] dt-bindings: soc: rockchip: Add rk3562 syscon compatibles Kever Yang
2025-05-06 2:57 ` [PATCH v5 4/6] dt-bindings: arm: rockchip: Add rk3562 evb2 board Kever Yang
2025-05-06 2:57 ` [PATCH v5 5/6] arm64: dts: rockchip: add core dtsi for RK3562 SoC Kever Yang
2025-05-06 2:57 ` [PATCH v5 6/6] arm64: dts: rockchip: Add RK3562 evb2 devicetree Kever Yang
2025-05-06 18:23 ` [PATCH v5 0/6] rockchip: Add rk3562 SoC and evb support Rob Herring (Arm)
2025-05-07 2:02 ` Kever Yang [this message]
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=a5da2a81-6944-4d4e-a582-a24f8340efc5@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=bigfoot@classfun.cn \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dsimic@manjaro.org \
--cc=finley.xiao@rock-chips.com \
--cc=frank.wang@rock-chips.com \
--cc=heiko@sntech.de \
--cc=honyuenkwun@gmail.com \
--cc=jamie@jamieiles.com \
--cc=jbx6244@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marcin.juszkiewicz@linaro.org \
--cc=naoki@radxa.com \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=shresthprasad7@gmail.com \
--cc=wim@linux-watchdog.org \
--cc=zhangqing@rock-chips.com \
--cc=ziyao@disroot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®