From: Frank Li <Frank.li@nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"open list:MULTIMEDIA CARD (MMC),
SECURE DIGITAL (SD) AND..." <linux-mmc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: mmc: Convert fsl-esdhc.txt to yaml
Date: Mon, 3 Jun 2024 11:00:28 -0400 [thread overview]
Message-ID: <Zl3ajFd05VKULEyO@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <b78b14c7-e71c-4403-a606-80564a31e107@kernel.org>
On Sat, Jun 01, 2024 at 05:25:46PM +0200, Krzysztof Kozlowski wrote:
> On 31/05/2024 21:37, Frank Li wrote:
> > Convert layerscape fsl-esdhc binding doc from txt to yaml format.
> >
> > Addtional change during convert:
> > - deprecate "sdhci,wp-inverted", "sdhci,1-bit-only".
> > - Add "reg" and "interrupts" property.
> > - change example "sdhci@2e000" to "mmc@2e000".
> > - compatible string require fsl,<chip>-esdhc followed by fsl,esdhc to match
> > most existed dts file.
> >
>
>
> > -};
> > diff --git a/Documentation/devicetree/bindings/mmc/fsl-ls-esdhc.yaml b/Documentation/devicetree/bindings/mmc/fsl-ls-esdhc.yaml
> > new file mode 100644
> > index 0000000000000..cafc09c4f1234
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mmc/fsl-ls-esdhc.yaml
>
> Filename: fsl,esdhc.yaml
There is fsl-imx-esdhc.yaml for freescale imx esdhc. If use "fsl,esdhc.yam",
it may confuse user, which will cover imx chips also, actually it is only
used for layerscape chips.
Frank
>
> > @@ -0,0 +1,98 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
>
> ...
>
> > + clock-frequency:
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + description: specifies eSDHC base clock frequency.
> > +
> > + sdhci,wp-inverted:
> > + $ref: /schemas/types.yaml#/definitions/flag
> > + deprecated: true
> > + description:
> > + specifies that eSDHC controller reports
> > + inverted write-protect state; New devices should use the generic
> > + "wp-inverted" property.
> > +
> > + sdhci,1-bit-only:
> > + $ref: /schemas/types.yaml#/definitions/flag
> > + deprecated: true
> > + description:
> > + specifies that a controller can only handle
> > + 1-bit data transfers. New devices should use the generic
> > + "bus-width = <1>" property.
> > +
> > + sdhci,auto-cmd12:
> > + $ref: /schemas/types.yaml#/definitions/flag
> > + description:
> > + specifies that a controller can only handle auto CMD12.
> > +
> > + voltage-ranges:
> > + $ref: /schemas/types.yaml#/definitions/uint32-matrix
> > + items:
> > + items:
> > + - description: specifies minimum slot voltage (mV).
> > + - description: specifies maximum slot voltage (mV).
> > +
> > + little-endian:
> > + $ref: /schemas/types.yaml#/definitions/flag
> > + description:
> > + If the host controller is little-endian mode, specify
> > + this property. The default endian mode is big-endian.
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - interrupts
>
> clock-frequency was required. Isn't it required now?
>
> > +
> > +allOf:
> > + - $ref: sdhci-common.yaml#
> > +
> > +unevaluatedProperties: false
> > +
> > +examples:
> > + - |
> > + mmc@2e000 {
> > + compatible = "fsl,mpc8378-esdhc", "fsl,esdhc";
> > + reg = <0x2e000 0x1000>;
> > + interrupts = <42 0x8>;
> > + interrupt-parent = <&ipic>;
> > + /* Filled in by U-Boot */
> > + clock-frequency = <0>;
>
> Please provide complete (final) example.
>
> > + voltage-ranges = <3300 3300>;
> > + };
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-06-03 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 19:37 [PATCH 1/1] dt-bindings: mmc: Convert fsl-esdhc.txt to yaml Frank Li
2024-06-01 15:25 ` Krzysztof Kozlowski
2024-06-03 15:00 ` Frank Li [this message]
2024-06-04 6:25 ` Krzysztof Kozlowski
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=Zl3ajFd05VKULEyO@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.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