linux-kernel - Re: [PATCH] dt-bindings: mmc: xenon: Convert to JSON schema

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <fd8cb680-5ae0-6b47-3f35-a497c51a47b9@alliedtelesis.co.nz>
Date:   Mon, 21 Mar 2022 00:12:24 +0000
From:   Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To:     Krzysztof Kozlowski <krzk@...nel.org>,
        "huziji@...vell.com" <huziji@...vell.com>,
        "ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "andrew@...n.ch" <andrew@...n.ch>,
        "gregory.clement@...tlin.com" <gregory.clement@...tlin.com>,
        "sebastian.hesselbarth@...il.com" <sebastian.hesselbarth@...il.com>
CC:     "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] dt-bindings: mmc: xenon: Convert to JSON schema

(adding some ARM people, resending hopefully without the html)

On 19/03/22 03:20, Krzysztof Kozlowski wrote:
>> +          - const: marvell,sdhci-xenon
> This did not exist before. Separate patches please for additions (with
> explanation why). Maybe some DTS lists this, but then it should be
> individually judged whether the DTS is correct.
>
On this specifically. I was all ready to add an additional patch to 
document this but then I noticed nothing actually uses the 
"marvell,sdhci-xenon" compatible and it appears nothing ever did. I then 
figured I'd delete the unused compatible string from armada-37xx.dtsi 
but then I remembered that sometimes we add compatible strings to have 
them "just in case" we need them for some SoC specific workaround.

So there's a few things I can do

0. Nothing (easy) although the binding I just submitted will complain 
about the unexpected value
1. Document "marvell,sdhci-xenon" as a valid compatible
1.a. Add "marvell,sdhci-xenon" to the sdhci-xenon.c driver
2. Remove "marvell,sdhci-xenon" from armada-37xx.dtsi