From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [v2, 1/5] mmc: dt: add compatible into eSDHC required properties
Date: Fri, 5 May 2017 11:18:02 +0800 [thread overview]
Message-ID: <20170505031801.GA852@dragon> (raw)
In-Reply-To: <DB6PR0401MB2536CB3661070921AEA0C5B6F8EB0@DB6PR0401MB2536.eurprd04.prod.outlook.com>
On Fri, May 05, 2017 at 03:01:04AM +0000, Y.B. Lu wrote:
> > > diff --git a/Documentation/devicetree/bindings/mmc/fsl-esdhc.txt
> > > b/Documentation/devicetree/bindings/mmc/fsl-esdhc.txt
> > > index dedfb02..b04b248 100644
> > > --- a/Documentation/devicetree/bindings/mmc/fsl-esdhc.txt
> > > +++ b/Documentation/devicetree/bindings/mmc/fsl-esdhc.txt
> > > @@ -7,6 +7,7 @@ This file documents differences between the core
> > > properties described by mmc.txt and the properties used by the sdhci-
> > esdhc driver.
> > >
> > > Required properties:
> > > + - compatible : should be "fsl,esdhc", or "fsl,<chip>-esdhc".
> >
> > I think either supported <chip> or the compatible should be listed
> > explicitly.
> >
>
> [Lu Yangbo-B47093] I think the reason we use <chip> is to avoid listing too much chips, and to avoid doc updating if new chips are added.
> The checkpatch script also had considered that.
>
> Currently there're about 20 platforms with "fsl,<chip>-esdhc" compatible in kernel dts.
> And the doc also provide an example.
> Example:
>
> sdhci at 2e000 {
> compatible = "fsl,mpc8378-esdhc", "fsl,esdhc";
>
> Should we still need to list all ?
I anyway need an ACK from Rob on this patch. Let's see what he would
say.
Shawn
next prev parent reply other threads:[~2017-05-05 3:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 10:48 [v2, 0/5] Add eSDHC UHS-I/HS200 mode support for ls1012a/ls1046a/ls208xa Yangbo Lu
2017-05-04 10:48 ` [v2, 1/5] mmc: dt: add compatible into eSDHC required properties Yangbo Lu
2017-05-05 2:36 ` Shawn Guo
2017-05-05 3:01 ` Y.B. Lu
2017-05-05 3:18 ` Shawn Guo [this message]
2017-05-08 16:36 ` Rob Herring
2017-05-09 2:51 ` Y.B. Lu
2017-05-04 10:48 ` [v2, 2/5] arm64: dts: ls1046a: support SD UHS-I and eMMC HS200 on RDB Yangbo Lu
2017-05-04 10:48 ` [v2, 3/5] arm64: dts: ls208xa: support SD UHS-I on RDB and eMMC HS200 on QDS Yangbo Lu
2017-05-04 10:48 ` [v2, 4/5] arm64: dts: ls1012a: add eSDHC nodes Yangbo Lu
2017-05-04 10:49 ` [v2, 5/5] arm64: dts: ls1088a: add esdhc node Yangbo Lu
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=20170505031801.GA852@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).