From: Doug Anderson <dianders@chromium.org>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps
Date: Wed, 22 Jun 2016 08:06:20 -0700 [thread overview]
Message-ID: <CAD=FV=WNaTEDyVNyteLq3O-BL9KxR49W=44jbXogKXd2dkDWDQ@mail.gmail.com> (raw)
In-Reply-To: <1465374021-2526-1-git-send-email-shawn.lin@rock-chips.com>
Hi,
On Wed, Jun 8, 2016 at 1:20 AM, Shawn Lin <shawn.lin@rock-chips.com> wrote:
> Let's add some basic description for cap-no-sdio,
> cap-no-sd and cap-no-mmc.
>
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
>
> ---
>
> Documentation/devicetree/bindings/mmc/mmc.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt b/Documentation/devicetree/bindings/mmc/mmc.txt
> index ecc007a..e16d42b 100644
> --- a/Documentation/devicetree/bindings/mmc/mmc.txt
> +++ b/Documentation/devicetree/bindings/mmc/mmc.txt
> @@ -39,6 +39,9 @@ Optional properties:
> - cap-power-off-card: powering off the card is safe
> - cap-mmc-hw-reset: eMMC hardware reset is supported
> - cap-sdio-irq: enable SDIO IRQ signalling on this interface
> +- cap-no-sdio: skip sending sdio cmd during initialization
> +- cap-no-sd: skip sending sd cmd during initialization
> +- cap-no-mmc: skip sending mmc cmd during initialization
In the past it has been determined that the "cap-" prefix is
unnecessary. Some properties still have "cap-" because of backward
compatibility reasons, but as I understand it new properties shouldn't
start with "cap-".
See <https://lists.ozlabs.org/pipermail/devicetree-discuss/2013-June/034664.html>
for reference.
-Doug
next prev parent reply other threads:[~2016-06-22 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 8:19 [RFC PATCH 0/4] Introduce new caps to improve the card's init sequence Shawn Lin
2016-06-08 8:20 ` [RFC PATCH 1/4] Documentation: mmc: add description for new caps Shawn Lin
2016-06-08 20:48 ` Rob Herring
2016-06-22 12:30 ` Ulf Hansson
2016-06-22 15:06 ` Doug Anderson [this message]
2016-06-23 1:29 ` Shawn Lin
2016-06-23 4:33 ` Doug Anderson
2016-06-08 8:20 ` [RFC PATCH 2/4] mmc: core: expose MMC_CAP2_NO_SDIO to dt-binding Shawn Lin
2016-06-08 8:20 ` [RFC PATCH 3/4] mmc: core: add cap-no-sd and cap-no-mmc properties Shawn Lin
2016-06-08 8:22 ` [RFC PATCH 4/4] mmc: core: improve initialization flow Shawn Lin
2016-06-22 12:37 ` [RFC PATCH 0/4] Introduce new caps to improve the card's init sequence Ulf Hansson
2016-06-23 1:35 ` Shawn Lin
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='CAD=FV=WNaTEDyVNyteLq3O-BL9KxR49W=44jbXogKXd2dkDWDQ@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=shawn.lin@rock-chips.com \
--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).