From: "Rob Herring (Arm)" <robh@kernel.org>
To: Sergey Bostandzhyan <jin@mediatomb.cc>
Cc: linux-arm-kernel@lists.infradead.org, heiko@sntech.de,
devicetree@vger.kernel.org, conor+dt@kernel.org,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH V2 0/2 RESEND] Add DTS for NanoPi R2S Plus
Date: Mon, 05 Aug 2024 09:00:12 -0600 [thread overview]
Message-ID: <172286966609.2708545.4957056858125634326.robh@kernel.org> (raw)
In-Reply-To: <20240801175736.16591-1-jin@mediatomb.cc>
On Thu, 01 Aug 2024 17:57:34 +0000, Sergey Bostandzhyan wrote:
> Hi,
>
> as requested, I am resending the patch series, now with hopefully all
> relevant addresses on To/Cc.
>
> I noticed, that a DTS for the R2S Plus is not yet available, while the
> R2S is already there. The only difference is, that the Plus version has an
> eMMC, so we can reuse the R2S definitions and only add an eMMC block, which
> I copied from the DTS in the friendlyarm/uboot-rockchip repo.
>
> I applied the same DTS changes to u-boot and tested u-boot 2024.04 with
> kernel 6.6.35 on an R2S Plus which I have here and the eMMC became visible
> and usable.
>
> Kind regards,
> Sergey
>
>
> Sergey Bostandzhyan (2):
> arm64: dts: rockchip: Add DTS for FriendlyARM NanoPi R2S Plus
> dt-bindings: arm: rockchip: Add NanoPi R2S Plus
>
> .../devicetree/bindings/arm/rockchip.yaml | 1 +
> arch/arm64/boot/dts/rockchip/Makefile | 1 +
> .../dts/rockchip/rk3328-nanopi-r2s-plus.dts | 31 +++++++++++++++++++
> 3 files changed, 33 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dts
>
> --
> 2.20.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
New warnings running 'make CHECK_DTBS=y rockchip/rk3328-nanopi-r2s-plus.dtb' for 20240801175736.16591-1-jin@mediatomb.cc:
arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: hdmi@ff3c0000: interrupts: [[0, 35, 4], [0, 71, 4]] is too long
from schema $id: http://devicetree.org/schemas/display/rockchip/rockchip,dw-hdmi.yaml#
arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: /phy@ff430000: failed to match any schema with compatible: ['rockchip,rk3328-hdmi-phy']
arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: /clock-controller@ff440000: failed to match any schema with compatible: ['rockchip,rk3328-cru', 'rockchip,cru', 'syscon']
arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: /clock-controller@ff440000: failed to match any schema with compatible: ['rockchip,rk3328-cru', 'rockchip,cru', 'syscon']
arch/arm64/boot/dts/rockchip/rk3328-nanopi-r2s-plus.dtb: mmc@ff520000: Unevaluated properties are not allowed ('num-slots', 'supports-emmc' were unexpected)
from schema $id: http://devicetree.org/schemas/mmc/rockchip-dw-mshc.yaml#
next prev parent reply other threads:[~2024-08-05 15:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22bbec28-41c1-4f36-b776-6e091bf118d9@kernel.org>
2024-08-01 17:57 ` Sergey Bostandzhyan
2024-08-01 17:57 ` [PATCH V2 1/2 RESEND] arm64: dts: rockchip: Add DTS for FriendlyARM " Sergey Bostandzhyan
2024-08-04 0:27 ` Daniel Golle
2024-08-05 8:59 ` Sergey 'Jin' Bostandzhyan
2024-08-10 19:11 ` Heiko Stübner
2024-08-14 11:21 ` Sergey 'Jin' Bostandzhyan
2024-08-14 11:30 ` Diederik de Haas
2024-08-14 11:34 ` Diederik de Haas
2024-08-14 11:36 ` Heiko Stübner
2024-08-14 12:24 ` Sergey 'Jin' Bostandzhyan
2024-08-14 13:53 ` Heiko Stübner
2024-08-01 17:57 ` [PATCH V2 2/2 RESEND] dt-bindings: arm: rockchip: Add " Sergey Bostandzhyan
2024-08-06 17:24 ` Rob Herring (Arm)
2024-08-01 21:22 ` [PATCH V2 0/2 RESEND] Add DTS for " Heiko Stübner
2024-08-02 9:46 ` Bjoern A. Zeeb
2024-08-02 10:04 ` Sergey 'Jin' Bostandzhyan
2024-08-05 15:00 ` Rob Herring (Arm) [this message]
2024-08-02 13:57 Bjoern A. Zeeb
2024-08-02 14:19 ` Diederik de Haas
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=172286966609.2708545.4957056858125634326.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jin@mediatomb.cc \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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®