linux-kernel - Re: [PATCH] dt-bindings: mmc: move compatible property to its specific binding

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 for Android: free password hash cracker in your pocket

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

Message-ID: <91dfdd42-6ddb-490f-acda-41ce55782959@microchip.com>
Date: Tue, 7 Jan 2025 03:34:33 +0000
From: <Dharma.B@...rochip.com>
To: <conor@...nel.org>
CC: <ulf.hansson@...aro.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
	<conor+dt@...nel.org>, <neil.armstrong@...aro.org>, <khilman@...libre.com>,
	<jbrunet@...libre.com>, <martin.blumenstingl@...glemail.com>,
	<linux-mmc@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>, <linux-amlogic@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dt-bindings: mmc: move compatible property to its
 specific binding

On 20/12/24 1:41 am, Conor Dooley wrote:
> On Thu, Dec 19, 2024 at 09:40:41AM +0530, Dharma Balasubiramani wrote:
>> Move the `compatible` property into its specific binding to make the MMC
>> slot more generic and modular.
> This makes no sense, as presented. What's the real reason for this
> change? You want to ref mmc-slot.yaml but the compatible is causing a
> driver to probe?

We don’t have the configuration for that driver enabled. Wouldn’t 
including the compatible in the DTS files without the actual driver be 
redundant?

Is it the correct approach to add the compatible just to fix the dt 
binding errors?

related discussion: 
https://lore.kernel.org/lkml/63473475-f29e-4a65-a0aa-1f1e4112b57d@microchip.com/

> Otherwise, if this is just to avoid having to fix up some devicetree
> source files, I don't think we should do this.
> 
> Thanks,
> Conor.
> 
>> Signed-off-by: Dharma Balasubiramani<dharma.b@...rochip.com>
>> ---
>>   Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml | 4 ++++
>>   Documentation/devicetree/bindings/mmc/mmc-slot.yaml              | 7 +------
>>   2 files changed, 5 insertions(+), 6 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml b/Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml
>> index 022682a977c6..7600a4988eca 100644
>> --- a/Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml
>> +++ b/Documentation/devicetree/bindings/mmc/amlogic,meson-mx-sdio.yaml
>> @@ -54,6 +54,10 @@ patternProperties:
>>         A node for each slot provided by the MMC controller
>>   
>>       properties:
>> +      compatible:
>> +        items:
>> +          - const: mmc-slot
>> +
>>         reg:
>>           enum: [0, 1, 2]
>>   
>> diff --git a/Documentation/devicetree/bindings/mmc/mmc-slot.yaml b/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
>> index 1f0667828063..84c4605658e0 100644
>> --- a/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
>> +++ b/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
>> @@ -20,19 +20,15 @@ properties:
>>     $nodename:
>>       pattern:"^slot(@.*)?$"
>>   
>> -  compatible:
>> -    const: mmc-slot
>> -
>>     reg:
>>       description:
>>         the slot (or "port") ID
>>       maxItems: 1
>>   
>>   required:
>> -  - compatible
>>     - reg
>>   
>> -unevaluatedProperties: false
>> +additionalProperties: true
>>   
>>   examples:
>>     - |
>> @@ -40,7 +36,6 @@ examples:
>>         #address-cells = <1>;
>>         #size-cells = <0>;
>>         slot@0 {
>> -        compatible = "mmc-slot";
>>           reg = <0>;
>>           bus-width = <4>;
>>         };
>>
>> ---
>> base-commit: 7fa366f1b6e376c38966faa42da7f0f2e013fdab
>> change-id: 20241219-mmc-slot-0574889daea3
>>
>> Best regards,
>> -- 
>> Dharma Balasubiramani<dharma.b@...rochip.com>


-- 
With Best Regards,
Dharma B.