From: Wolfram Sang <wsa@the-dreams.de>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-mmc@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Mathieu Malaterre <malat@debian.org>, Pavel Machek <pavel@ucw.cz>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [PATCH 1/3] dt-bindings: mmc: Add 'fixed-emmc-driver-type-hs{200,400}'
Date: Tue, 5 Nov 2019 07:22:23 +0100 [thread overview]
Message-ID: <20191105062223.GB1048@kunai> (raw)
In-Reply-To: <20191105055015.23656-1-erosca@de.adit-jv.com>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
Hi Eugeniu,
thanks for this work!
> A certain eMMC manufacturer provided below requirement:
> ---snip---
> Use "drive strength" value of 4 or 1 for HS400 or 0 for HS200.
> ---snip---
I see.
> The existing "fixed-emmc-driver-type" property [1] is the closest one
> to implement the above, but it falls short due to being unable to define
> two values to differentiate between HS200 and HS400 (both modes may be
> supported by the same non-removable MMC device).
>
> To allow users to set a preferred HS200/HS400 "drive strength", provide
> two more bindings inspired from [1]:
> - fixed-emmc-driver-type-hs200
> - fixed-emmc-driver-type-hs400
Main question before looking at the code: Can't we just extend the
existing binding with an optional second parameter?
minItems: 1
maxItems: 2
I tend to favour this approach...
> For more details about eMMC I/O driver strength types, see Jedec spec.
> Keep "fixed-emmc-driver-type" in place for backward compatibility.
If we decide for the path proposed here, should the old binding be
deprecated then?
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-11-05 6:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 5:50 [PATCH 1/3] dt-bindings: mmc: Add 'fixed-emmc-driver-type-hs{200,400}' Eugeniu Rosca
2019-11-05 5:50 ` [PATCH 2/3] mmc: host: Compress 'fixed-emmc-driver-type' handling Eugeniu Rosca
2019-11-05 5:50 ` [PATCH 3/3] mmc: core: Add 'fixed-emmc-driver-type-hs{200,400}' Eugeniu Rosca
2019-11-05 6:22 ` Wolfram Sang [this message]
2019-11-05 8:32 ` [PATCH 1/3] dt-bindings: mmc: " Eugeniu Rosca
2019-11-07 0:39 ` Rob Herring
2019-11-12 21:19 ` Wolfram Sang
2019-11-12 23:11 ` Linus Walleij
2019-11-14 10:46 ` Ulf Hansson
2019-11-06 11:07 ` Linus Walleij
2019-11-11 22:25 ` Eugeniu Rosca
2019-11-12 23:08 ` Linus Walleij
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=20191105062223.GB1048@kunai \
--to=wsa@the-dreams.de \
--cc=adrian.hunter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=erosca@de.adit-jv.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=malat@debian.org \
--cc=pavel@ucw.cz \
--cc=roscaeugeniu@gmail.com \
--cc=ulf.hansson@linaro.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).