From: Ulf Hansson <ulf.hansson@linaro.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Simon Horman <horms@verge.net.au>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v3 1/3] dt-bindings: mmc: describe new eMMC binding for fixed driver type
Date: Fri, 20 Oct 2017 12:03:04 +0200 [thread overview]
Message-ID: <CAPDyKFoAwbki4LEy3UmNqFi9dNSBHeT4oRELw28+LSdaHW4_Bg@mail.gmail.com> (raw)
In-Reply-To: <20171015124615.31391-2-wsa+renesas@sang-engineering.com>
On 15 October 2017 at 14:46, Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> Some boards may have to use a certain driver type (or drive strength) to
> achieve stable eMMC communication. Describe a binding to set this up via
> DT.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Acked-by: Rob Herring <robh@kernel.org>
Thanks, applied for next!
Kind regards
Uffe
> ---
>
> no changes since v2
>
> 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 b32ade645ad97c..94a90b49a6925d 100644
> --- a/Documentation/devicetree/bindings/mmc/mmc.txt
> +++ b/Documentation/devicetree/bindings/mmc/mmc.txt
> @@ -53,6 +53,9 @@ Optional properties:
> - no-sdio: controller is limited to send sdio cmd during initialization
> - no-sd: controller is limited to send sd cmd during initialization
> - no-mmc: controller is limited to send mmc cmd during initialization
> +- fixed-emmc-driver-type: for non-removable eMMC, enforce this driver type.
> + The value <n> is the driver type as specified in the eMMC specification
> + (table 206 in spec version 5.1).
>
> *NOTE* on CD and WP polarity. To use common for all SD/MMC host controllers line
> polarity properties, we have to fix the meaning of the "normal" and "inverted"
> --
> 2.11.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-10-20 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 12:46 [PATCH v3 0/3] mmc: support eMMC driver type selection with DT Wolfram Sang
2017-10-15 12:46 ` [PATCH v3 1/3] dt-bindings: mmc: describe new eMMC binding for fixed driver type Wolfram Sang
2017-10-16 7:45 ` Simon Horman
2017-10-20 10:03 ` Ulf Hansson [this message]
2017-10-15 12:46 ` [PATCH v3 2/3] mmc: parse new binding for eMMC " Wolfram Sang
2017-10-16 7:45 ` Simon Horman
2017-10-20 10:03 ` Ulf Hansson
2017-10-15 12:46 ` [PATCH v3 3/3] arm64: renesas: salvator: set driver type for eMMC Wolfram Sang
2017-10-16 7:46 ` Simon Horman
2017-10-20 10:03 ` Ulf Hansson
2017-10-21 8:34 ` Wolfram Sang
2017-10-29 15:16 ` Simon Horman
2017-10-29 15:23 ` Wolfram Sang
2017-10-29 15:25 ` Simon Horman
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=CAPDyKFoAwbki4LEy3UmNqFi9dNSBHeT4oRELw28+LSdaHW4_Bg@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=horms@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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).