From: "Duje Mihanović" <duje@dujemihanovic.xyz>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lubomir Rintel <lkundrak@v3.sk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
David Wronek <david@mainlining.org>,
Karel Balej <balejk@matfyz.cz>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-hardening@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht, soc@lists.linux.dev,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH v16 1/5] dt-bindings: mmc: sdhci-pxa: restrict pinctrl to pxav1
Date: Wed, 09 Jul 2025 19:33:01 +0200 [thread overview]
Message-ID: <3379810.44csPzL39Z@radijator> (raw)
In-Reply-To: <20250709-spectacular-goat-of-tenacity-ced55a@krzk-bin>
On Wednesday, 9 July 2025 09:32:06 Central European Summer Time Krzysztof
Kozlowski wrote:
> On Tue, Jul 08, 2025 at 07:09:46PM +0200, Duje Mihanović wrote:
> > The current pinctrl properties apply only to the pxav1 controller.
>
> Why they are not applicable for pxav3?
state_cmd_gpio is used for working around a PXA168 SDIO erratum. That SoC uses
the pxav1 controller and no such erratum exists on any of the other PXA SoCs.
> > Adding one default pinctrl node to a pxav3 controller therefore causes
> > a schema warning.
> >
> > Check the existing properties only on pxav1. pxav2 and pxav3 may add
> > their own set of pinctrl properties if and when needed.
>
> This should be rather made complete here, because properties should be
> defined in top-level, not in allOf: block. Strictly speaking pinctrl-xxx
> are defined in core schema, but still the binding should follow same
> rule - define them in top.
Would it then be acceptable to declare the pinctrl properties in the top level
and define each controller's respective description: and items: in the allOf:
block?
Regards,
--
Duje
next prev parent reply other threads:[~2025-07-09 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 17:09 [PATCH v16 0/5] Initial Marvell PXA1908 support Duje Mihanović
2025-07-08 17:09 ` [PATCH v16 1/5] dt-bindings: mmc: sdhci-pxa: restrict pinctrl to pxav1 Duje Mihanović
2025-07-09 7:32 ` Krzysztof Kozlowski
2025-07-09 17:33 ` Duje Mihanović [this message]
2025-07-11 7:31 ` Krzysztof Kozlowski
2025-07-14 22:23 ` Duje Mihanović
2025-07-15 6:32 ` Krzysztof Kozlowski
2025-07-10 21:47 ` Rob Herring
2025-07-08 17:09 ` [PATCH v16 2/5] dt-bindings: marvell: Document PXA1908 SoC and samsung,coreprimevelte Duje Mihanović
2025-07-08 17:09 ` [PATCH v16 3/5] arm64: Kconfig.platforms: Add config for Marvell PXA1908 platform Duje Mihanović
2025-07-09 10:22 ` kernel test robot
2025-07-08 17:09 ` [PATCH v16 4/5] arm64: dts: Add DTS for Marvell PXA1908 and samsung,coreprimevelte Duje Mihanović
2025-07-08 17:09 ` [PATCH v16 5/5] MAINTAINERS: add myself as Marvell PXA1908 maintainer Duje Mihanović
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=3379810.44csPzL39Z@radijator \
--to=duje@dujemihanovic.xyz \
--cc=andrew@lunn.ch \
--cc=balejk@matfyz.cz \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=david@mainlining.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=gregory.clement@bootlin.com \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=soc@lists.linux.dev \
--cc=tony.luck@intel.com \
--cc=ulf.hansson@linaro.org \
--cc=will@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).