From: Lars Povlsen <lars.povlsen@microchip.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Lars Povlsen <lars.povlsen@microchip.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"SoC Team" <soc@kernel.org>, Rob Herring <robh+dt@kernel.org>,
"Microchip Linux Driver Support" <UNGLinuxDriver@microchip.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] dt-bindings: mmc: Add Sparx5 SDHCI controller bindings
Date: Tue, 25 Aug 2020 11:35:14 +0200 [thread overview]
Message-ID: <87blizxe3x.fsf@soft-dev15.microsemi.net> (raw)
In-Reply-To: <20200825084752.GD2389103@piout.net>
Alexandre Belloni writes:
> On 25/08/2020 09:33:45+0200, Ulf Hansson wrote:
>> On Mon, 24 Aug 2020 at 17:10, Lars Povlsen <lars.povlsen@microchip.com> wrote:
>> >
>> > The Sparx5 SDHCI controller is based on the Designware controller IP.
>> >
>> > Signed-off-by: Lars Povlsen <lars.povlsen@microchip.com>
>> > ---
>> > .../mmc/microchip,dw-sparx5-sdhci.yaml | 65 +++++++++++++++++++
>> > 1 file changed, 65 insertions(+)
>> > create mode 100644 Documentation/devicetree/bindings/mmc/microchip,dw-sparx5-sdhci.yaml
>> >
>> > diff --git a/Documentation/devicetree/bindings/mmc/microchip,dw-sparx5-sdhci.yaml b/Documentation/devicetree/bindings/mmc/microchip,dw-sparx5-sdhci.yaml
>> > new file mode 100644
>> > index 0000000000000..55883290543b9
>> > --- /dev/null
>> > +++ b/Documentation/devicetree/bindings/mmc/microchip,dw-sparx5-sdhci.yaml
>> > @@ -0,0 +1,65 @@
>> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> > +%YAML 1.2
>> > +---
>> > +$id: http://devicetree.org/schemas/mmc/microchip,dw-sparx5-sdhci.yaml#
>> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> > +
>> > +title: Microchip Sparx5 Mobile Storage Host Controller Binding
>> > +
>> > +allOf:
>> > + - $ref: "mmc-controller.yaml"
>> > +
>> > +maintainers:
>> > + - Lars Povlsen <lars.povlsen@microchip.com>
>> > +
>> > +# Everything else is described in the common file
>> > +properties:
>> > + compatible:
>> > + const: microchip,dw-sparx5-sdhci
>> > +
>> > + reg:
>> > + maxItems: 1
>> > +
>> > + interrupts:
>> > + maxItems: 1
>> > +
>> > + clocks:
>> > + maxItems: 1
>> > + description:
>> > + Handle to "core" clock for the sdhci controller.
>> > +
>> > + clock-names:
>> > + items:
>> > + - const: core
>> > +
>> > + microchip,clock-delay:
>> > + description: Delay clock to card to meet setup time requirements.
>> > + Each step increase by 1.25ns.
>> > + $ref: "/schemas/types.yaml#/definitions/uint32"
>> > + minimum: 1
>> > + maximum: 15
>> > +
>> > +required:
>> > + - compatible
>> > + - reg
>> > + - interrupts
>> > + - clocks
>> > + - clock-names
>> > +
>> > +examples:
>> > + - |
>> > + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> > + #include <dt-bindings/clock/microchip,sparx5.h>
>> > + sdhci0: mmc@600800000 {
>>
>> Nitpick:
>>
>> I think we should use solely "mmc[n]" here. So:
>>
>> mmc0@600800000 {
>>
>> Please update patch3/3 accordingly as well.
>
> This is not what the devicetree specification says. 2.2.2 says that the
> generic name is mmc, not mmc[n]. Since there is a proper unit-address, I
> don't see the need for an index here.
>
Alex,
Yeah, I thought so as well - and the existing DTs have practically all
variations..
Nevertheless, I followed suit since I had to refresh the patch set
anyhow.
Cheers,
---Lars
--
Lars Povlsen,
Microchip
next prev parent reply other threads:[~2020-08-25 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 15:10 [PATCH v4 0/3] mmc: Adding support for Microchip Sparx5 SoC Lars Povlsen
2020-08-24 15:10 ` [PATCH v4 1/3] dt-bindings: mmc: Add Sparx5 SDHCI controller bindings Lars Povlsen
2020-08-25 7:33 ` Ulf Hansson
2020-08-25 8:47 ` Alexandre Belloni
2020-08-25 9:25 ` Ulf Hansson
2020-08-25 9:35 ` Lars Povlsen [this message]
2020-08-24 15:10 ` [PATCH v4 2/3] sdhci: sparx5: Add Sparx5 SoC eMMC driver Lars Povlsen
2020-08-24 15:50 ` Adrian Hunter
2020-08-24 20:03 ` kernel test robot
2020-08-24 15:10 ` [PATCH v4 3/3] arm64: dts: sparx5: Add Sparx5 eMMC support Lars Povlsen
-- strict thread matches above, loose matches on Subject: below --
2020-06-18 14:13 [PATCH v4 0/3] mmc: Adding support for Microchip Sparx5 SoC Lars Povlsen
2020-06-18 14:13 ` [PATCH v4 1/3] dt-bindings: mmc: Add Sparx5 SDHCI controller bindings Lars Povlsen
2020-06-29 21:54 ` Rob Herring
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=87blizxe3x.fsf@soft-dev15.microsemi.net \
--to=lars.povlsen@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=adrian.hunter@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).