linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, quentin.schulz@cherry.de,
	krzk+dt@kernel.org, devicetree@vger.kernel.org,
	conor+dt@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Add two board-families from Theobroma-Systems
Date: Tue, 13 May 2025 17:05:56 +0200	[thread overview]
Message-ID: <3311886.aV6nBDHxoP@diego> (raw)
In-Reply-To: <174679984943.3368422.9645324507043955723.robh@kernel.org>

Am Freitag, 9. Mai 2025, 16:16:58 Mitteleuropäische Sommerzeit schrieb Rob Herring (Arm):
> 
> On Thu, 08 May 2025 17:09:49 +0200, Heiko Stuebner wrote:
> > Both the Cobra and PP1516 boards are based around the PX30 SoC and can be
> > found with a variety of display options.
> > 
> > As new boards should not use the deprecated snps,reset-* properties
> > in the gmac node, I also added a core mdio-node for the gmac and
> > converted the Theobroma Ringneck board over.
> > 
> > Testing with the new node both before and after converting Ringneck
> > showed the board finding its network both when booting locally and
> > from the tftp/nfs.
> > 
> > 
> > Heiko Stuebner (6):
> >   arm64: dts: rockchip: add basic mdio node to px30
> >   arm64: dts: rockchip: move reset to dedicated eth-phy node on ringneck
> >   dt-bindings: arm: rockchip: add PX30-Cobra boards from Theobroma
> >     Systems
> >   arm64: dts: rockchip: add px30-cobra base dtsi and board variants
> >   dt-bindings: arm: rockchip: add PX30-PP1516 boards from Theobroma
> >     Systems
> >   arm64: dts: rockchip: add px30-pp1516 base dtsi and board variants
> > 
> >  .../devicetree/bindings/arm/rockchip.yaml     |  18 +
> >  arch/arm64/boot/dts/rockchip/Makefile         |   6 +
> >  .../rockchip/px30-cobra-ltk050h3146w-a2.dts   |  39 ++
> >  .../dts/rockchip/px30-cobra-ltk050h3146w.dts  |  39 ++
> >  .../dts/rockchip/px30-cobra-ltk050h3148w.dts  |  39 ++
> >  .../dts/rockchip/px30-cobra-ltk500hd1829.dts  |  58 ++
> >  arch/arm64/boot/dts/rockchip/px30-cobra.dtsi  | 570 +++++++++++++++++
> >  .../rockchip/px30-pp1516-ltk050h3146w-a2.dts  |  39 ++
> >  .../dts/rockchip/px30-pp1516-ltk050h3148w.dts |  39 ++
> >  arch/arm64/boot/dts/rockchip/px30-pp1516.dtsi | 601 ++++++++++++++++++
> >  .../boot/dts/rockchip/px30-ringneck.dtsi      |  22 +-
> >  arch/arm64/boot/dts/rockchip/px30.dtsi        |   6 +
> >  12 files changed, 1473 insertions(+), 3 deletions(-)
> >  create mode 100644 arch/arm64/boot/dts/rockchip/px30-cobra-ltk050h3146w-a2.dts
> >  create mode 100644 arch/arm64/boot/dts/rockchip/px30-cobra-ltk050h3146w.dts
> >  create mode 100644 arch/arm64/boot/dts/rockchip/px30-cobra-ltk050h3148w.dts
> >  create mode 100644 arch/arm64/boot/dts/rockchip/px30-cobra-ltk500hd1829.dts
> >  create mode 100644 arch/arm64/boot/dts/rockchip/px30-cobra.dtsi
> >  create mode 100644 arch/arm64/boot/dts/rockchip/px30-pp1516-ltk050h3146w-a2.dts
> >  create mode 100644 arch/arm64/boot/dts/rockchip/px30-pp1516-ltk050h3148w.dts
> >  create mode 100644 arch/arm64/boot/dts/rockchip/px30-pp1516.dtsi
> > 
> > --
> > 2.47.2
> > 
> > 
> > 
> 
> 
> 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.15-rc1-1-g59529bbe642d (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 20250508150955.1897702-1-heiko@sntech.de:
> 
> arch/arm64/boot/dts/rockchip/px30-cobra-ltk500hd1829.dtb: panel@0 (leadtek,ltk500hd1829): 'port' does not match any of the regexes: '^pinctrl-[0-9]+$'
> 	from schema $id: http://devicetree.org/schemas/display/panel/leadtek,ltk500hd1829.yaml#
> arch/arm64/boot/dts/rockchip/px30-cobra-ltk050h3148w.dtb: panel@0 (leadtek,ltk050h3148w): 'port' does not match any of the regexes: '^pinctrl-[0-9]+$'
> 	from schema $id: http://devicetree.org/schemas/display/panel/leadtek,ltk050h3146w.yaml#
> arch/arm64/boot/dts/rockchip/px30-pp1516-ltk050h3148w.dtb: panel@0 (leadtek,ltk050h3148w): 'port' does not match any of the regexes: '^pinctrl-[0-9]+$'
> 	from schema $id: http://devicetree.org/schemas/display/panel/leadtek,ltk050h3146w.yaml#
> arch/arm64/boot/dts/rockchip/px30-cobra-ltk050h3146w.dtb: panel@0 (leadtek,ltk050h3146w): 'port' does not match any of the regexes: '^pinctrl-[0-9]+$'
> 	from schema $id: http://devicetree.org/schemas/display/panel/leadtek,ltk050h3146w.yaml#
> arch/arm64/boot/dts/rockchip/px30-pp1516-ltk050h3146w-a2.dtb: panel@0 (leadtek,ltk050h3146w-a2): 'port' does not match any of the regexes: '^pinctrl-[0-9]+$'
> 	from schema $id: http://devicetree.org/schemas/display/panel/leadtek,ltk050h3146w.yaml#
> arch/arm64/boot/dts/rockchip/px30-cobra-ltk050h3146w-a2.dtb: panel@0 (leadtek,ltk050h3146w-a2): 'port' does not match any of the regexes: '^pinctrl-[0-9]+$'
> 	from schema $id: http://devicetree.org/schemas/display/panel/leadtek,ltk050h3146w.yaml#
> 

this is handled by the already applied changes to the panel bindings:
dt-bindings: display: ltk500hd1829: add port property [0]
dt-bindings: display: ltk050h3146w: add port property [1]


[0] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e782ac936941cff4c5580bb5cc2ec0e91468068c
[1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=bf0636f4348e098e2338eebbe42d7780c58a1195





      reply	other threads:[~2025-05-13 15:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 15:09 [PATCH 0/6] Add two board-families from Theobroma-Systems Heiko Stuebner
2025-05-08 15:09 ` [PATCH 1/6] arm64: dts: rockchip: add basic mdio node to px30 Heiko Stuebner
2025-05-12 10:04   ` Quentin Schulz
2025-05-08 15:09 ` [PATCH 2/6] arm64: dts: rockchip: move reset to dedicated eth-phy node on ringneck Heiko Stuebner
2025-05-12 18:30   ` Quentin Schulz
2025-05-08 15:09 ` [PATCH 3/6] dt-bindings: arm: rockchip: add PX30-Cobra boards from Theobroma Systems Heiko Stuebner
2025-05-08 15:12   ` Conor Dooley
2025-05-12 18:39   ` Quentin Schulz
2025-05-08 15:09 ` [PATCH 4/6] arm64: dts: rockchip: add px30-cobra base dtsi and board variants Heiko Stuebner
2025-05-09 11:21   ` Diederik de Haas
2025-05-12 19:48   ` Quentin Schulz
2025-05-08 15:09 ` [PATCH 5/6] dt-bindings: arm: rockchip: add PX30-PP1516 boards from Theobroma Systems Heiko Stuebner
2025-05-08 15:13   ` Conor Dooley
2025-05-13  8:08   ` Quentin Schulz
2025-05-08 15:09 ` [PATCH 6/6] arm64: dts: rockchip: add px30-pp1516 base dtsi and board variants Heiko Stuebner
2025-05-13  9:58   ` Quentin Schulz
2025-05-09 14:16 ` [PATCH 0/6] Add two board-families from Theobroma-Systems Rob Herring (Arm)
2025-05-13 15:05   ` Heiko Stübner [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=3311886.aV6nBDHxoP@diego \
    --to=heiko@sntech.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=quentin.schulz@cherry.de \
    --cc=robh@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 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).