devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Hsun Lai <i@chainsx.cn>, "Rob Herring (Arm)" <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	Conor Dooley <conor+dt@kernel.org>,
	Fred Bloggs <f.blogs@napier.co.nz>,
	linux-arm-kernel@lists.infradead.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v2 0/2] Add support for 100ASK DShanPi A1
Date: Tue, 26 Aug 2025 16:57:37 +0200	[thread overview]
Message-ID: <12479023.CDJkKcVGEf@phil> (raw)
In-Reply-To: <175621649670.159455.15557432322730951360.robh@kernel.org>

Am Dienstag, 26. August 2025, 15:56:43 Mitteleuropäische Sommerzeit schrieb Rob Herring (Arm):
> 
> On Tue, 26 Aug 2025 11:08:15 +0800, Hsun Lai wrote:
> > This series add support for 100ASK DShanPi A1.
> > 
> > Info of device can be found at:
> > https://wiki.dshanpi.org/en/docs/DshanPi-A1/intro/
> > 
> > Changes in v2:
> > - Delete the pwm include file (Chukun Pan, v1)
> > - Fix vcc3v3_pcie gpios (Chukun Pan, v1)
> > - Adjust the order of some nodes (Chukun Pan, v1)
> > - Fix sdmmc (Chukun Pan, v1)
> > - Add phy-supply for u2phy0_otg (Chukun Pan, v1)
> > 
> > Changes in v1:
> > - Add support for 100ASK DShanPi A1
> > 
> > Hsun Lai (2):
> >   dt-bindings: arm: rockchip: Add 100ASK DShanPi A1
> >   arm64: dts: rockchip: add DTs for 100ASK DShanPi A1
> > 
> >  .../devicetree/bindings/arm/rockchip.yaml     |   5 +
> >  arch/arm64/boot/dts/rockchip/Makefile         |   1 +
> >  .../dts/rockchip/rk3576-100ask-dshanpi-a1.dts | 838 ++++++++++++++++++
> >  3 files changed, 844 insertions(+)
> >  create mode 100644 arch/arm64/boot/dts/rockchip/rk3576-100ask-dshanpi-a1.dts
> > 
> > --
> > 2.34.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/v6.17-rc1-22-g7d11b8c260ea (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 20250826030818.3485927-1-i@chainsx.cn:

both warnings are not the fault of this board addition, but instead
come from "unrelated" sources in the main rk3576 dtsi:


> arch/arm64/boot/dts/rockchip/rk3576-100ask-dshanpi-a1.dtb: syscon@26034000 (rockchip,rk3576-dcphy-grf): clocks: False schema does not allow [[21, 492]]
> 	from schema $id: http://devicetree.org/schemas/soc/rockchip/grf.yaml#

I messed up and forgot to add the new syscon to the clocks-required list.
Will fix that shortly.


> arch/arm64/boot/dts/rockchip/rk3576-100ask-dshanpi-a1.dtb: /soc/dsi@27d80000: failed to match any schema with compatible: ['rockchip,rk3576-mipi-dsi2']

the rk3576 dsi compatible is in drm-misc-next [0], so should
hit linux-next shortly.


[0] https://gitlab.freedesktop.org/drm/misc/kernel/-/commit/f05530bdaf42aa0e6bb4cde76ba6a081cf473d44



      reply	other threads:[~2025-08-26 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26  3:08 [PATCH v2 0/2] Add support for 100ASK DShanPi A1 Hsun Lai
2025-08-26  3:08 ` [PATCH v2 1/2] dt-bindings: arm: rockchip: Add " Hsun Lai
2025-08-26  3:08 ` [PATCH v2 2/2] arm64: dts: rockchip: add DTs for " Hsun Lai
2025-08-27 14:30   ` Chukun Pan
2025-08-26 13:56 ` [PATCH v2 0/2] Add support " Rob Herring (Arm)
2025-08-26 14:57   ` Heiko Stuebner [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=12479023.CDJkKcVGEf@phil \
    --to=heiko@sntech.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=f.blogs@napier.co.nz \
    --cc=i@chainsx.cn \
    --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=robh@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).