Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: <Dharma.B@microchip.com>
To: <robh@kernel.org>
Cc: <ulf.hansson@linaro.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <Nicolas.Ferre@microchip.com>,
	<alexandre.belloni@bootlin.com>, <claudiu.beznea@tuxon.dev>,
	<Aubin.Constans@microchip.com>, <linux-mmc@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: mmc: atmel,hsmci: Convert to json schema
Date: Wed, 18 Dec 2024 04:11:50 +0000	[thread overview]
Message-ID: <63473475-f29e-4a65-a0aa-1f1e4112b57d@microchip.com> (raw)
In-Reply-To: <20241217124316.GA1136537-robh@kernel.org>

Hi Rob,

On 17/12/24 6:13 pm, Rob Herring wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Mon, Dec 09, 2024 at 10:02:30AM +0530, Dharma Balasubiramani wrote:
>> Convert atmel,hsmci documentation to yaml format. The new file will inherit
>> from mmc-controller.yaml.
>>
>> Signed-off-by: Dharma Balasubiramani <dharma.b@microchip.com>
>> ---
>> Changes in v2:
>> - Drop the duplicate properties in the slot node.
>> - Link to v1: https://lore.kernel.org/r/20241205-hsmci-v1-1-5a25e622dfed@microchip.com
>> ---
>>   .../devicetree/bindings/mmc/atmel,hsmci.yaml       | 110 +++++++++++++++++++++
>>   .../devicetree/bindings/mmc/atmel-hsmci.txt        |  73 --------------
>>   2 files changed, 110 insertions(+), 73 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/mmc/atmel,hsmci.yaml b/Documentation/devicetree/bindings/mmc/atmel,hsmci.yaml
>> new file mode 100644
>> index 000000000000..26686ada6288
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mmc/atmel,hsmci.yaml
>> @@ -0,0 +1,110 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/mmc/atmel,hsmci.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Atmel High-Speed MultiMedia Card Interface (HSMCI)
>> +
>> +description:
>> +  The Atmel HSMCI controller provides an interface for MMC, SD, and SDIO memory
>> +  cards.
>> +
>> +maintainers:
>> +  - Nicolas Ferre <nicolas.ferre@microchip.com>
>> +  - Aubin Constans <aubin.constans@microchip.com>
>> +
>> +allOf:
>> +  - $ref: mmc-controller.yaml
>> +
>> +properties:
>> +  compatible:
>> +    const: atmel,hsmci
>> +
>> +  reg:
>> +    maxItems: 1
>> +
>> +  interrupts:
>> +    maxItems: 1
>> +
>> +  dmas:
>> +    maxItems: 1
>> +
>> +  dma-names:
>> +    const: rxtx
>> +
>> +  clocks:
>> +    maxItems: 1
>> +
>> +  clock-names:
>> +    const: mci_clk
>> +
>> +  "#address-cells":
>> +    const: 1
>> +    description: Used for slot IDs.
>> +
>> +  "#size-cells":
>> +    const: 0
>> +
>> +patternProperties:
>> +  "^slot@[0-9]+$":
>> +    type: object
>> +    description: A slot node representing an MMC, SD, or SDIO slot.
> 
> There's a schema for slots now queued for 6.14[1]. You should use that.

Sure,
I will drop these and will just add the REF to mmc-slot

  patternProperties:
    "^slot@[0-9]+$":
-    type: object
-    description: A slot node representing an MMC, SD, or SDIO slot.
-
-    allOf:
-      - $ref: mmc-controller.yaml
-
-    properties:
-      reg:
-        description: Slot ID.
-        minimum: 0
+    $ref: mmc-slot.yaml

> One issue is 'compatible' is required. Either that would have to be
> dropped as required 
How to do that?

dt_binding_check complains that mmc@f0008000: slot@0: 'compatible' is a 
required property.

If the mmc-slot yaml is a generic binding then shall we move the 
compatible to its specific binding(amlogic,meson-mx-sdio.yaml)?

or you could just add it in your .dts files.

Won't it be redundant to have it?
> 
> Rob


-- 
With Best Regards,
Dharma B.

      reply	other threads:[~2024-12-18  4:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09  4:32 [PATCH v2] dt-bindings: mmc: atmel,hsmci: Convert to json schema Dharma Balasubiramani
2024-12-16  9:26 ` Charan.Pedumuru
2024-12-17 12:43 ` Rob Herring
2024-12-18  4:11   ` Dharma.B [this message]

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=63473475-f29e-4a65-a0aa-1f1e4112b57d@microchip.com \
    --to=dharma.b@microchip.com \
    --cc=Aubin.Constans@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.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