linux-hardening - Re: [PATCH v16 1/5] dt-bindings: mmc: sdhci-pxa: restrict pinctrl to pxav1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <95ef2f67-146d-4f31-a07a-4d1f82bc60c3@kernel.org>
Date: Tue, 15 Jul 2025 08:32:08 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Duje Mihanović <duje@...emihanovic.xyz>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Lubomir Rintel <lkundrak@...sk>,
 Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>,
 Andrew Lunn <andrew@...n.ch>, Gregory Clement <gregory.clement@...tlin.com>,
 Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
 Kees Cook <kees@...nel.org>, Tony Luck <tony.luck@...el.com>,
 "Guilherme G. Piccoli" <gpiccoli@...lia.com>,
 Ulf Hansson <ulf.hansson@...aro.org>, David Wronek <david@...nlining.org>,
 Karel Balej <balejk@...fyz.cz>, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-hardening@...r.kernel.org, phone-devel@...r.kernel.org,
 ~postmarketos/upstreaming@...ts.sr.ht, soc@...ts.linux.dev,
 linux-mmc@...r.kernel.org
Subject: Re: [PATCH v16 1/5] dt-bindings: mmc: sdhci-pxa: restrict pinctrl to
 pxav1

On 15/07/2025 00:23, Duje Mihanović wrote:
> On Friday, 11 July 2025 09:31:55 Central European Summer Time Krzysztof 
> Kozlowski wrote:
>> On Wed, Jul 09, 2025 at 07:33:01PM +0200, Duje Mihanović wrote:
>>> 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?
>>
>> just min/maxItems should be enough in each allOf:if:then: sections.
> 
> I guess for now. Later however I might need to add a state_uhs setting to the 
> pxav3 driver; is the method I described right for this or is there something 
> better?
Then please define it now which would make entire discussion obsolete, I
think.

Best regards,
Krzysztof