From: <Dharma.B@microchip.com>
To: <conor@kernel.org>
Cc: <ulf.hansson@linaro.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <neil.armstrong@linaro.org>,
<khilman@baylibre.com>, <jbrunet@baylibre.com>,
<martin.blumenstingl@googlemail.com>, <linux-mmc@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: mmc: move compatible property to its specific binding
Date: Tue, 7 Jan 2025 03:34:33 +0000 [thread overview]
Message-ID: <91dfdd42-6ddb-490f-acda-41ce55782959@microchip.com> (raw)
In-Reply-To: <20241219-scenic-revision-17da9231d61a@spud>
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@microchip.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@microchip.com>
--
With Best Regards,
Dharma B.
next prev parent reply other threads:[~2025-01-07 3:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 4:10 [PATCH] dt-bindings: mmc: move compatible property to its specific binding Dharma Balasubiramani
2024-12-19 20:11 ` Conor Dooley
2025-01-07 3:34 ` Dharma.B [this message]
2025-01-07 20:34 ` Martin Blumenstingl
2025-01-08 3:11 ` Dharma.B
2025-01-08 20:56 ` Martin Blumenstingl
2025-01-20 4:30 ` Dharma.B
2025-02-04 4:24 ` Dharma.B
2025-02-04 8:14 ` neil.armstrong
2025-02-05 3:49 ` Dharma.B
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=91dfdd42-6ddb-490f-acda-41ce55782959@microchip.com \
--to=dharma.b@microchip.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.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