From: Rob Herring <robh@kernel.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
Ulf Hansson <ulf.hansson@linaro.org>, Marek Vasut <marex@denx.de>,
Otavio Salvador <otavio@ossystems.com.br>,
devicetree@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
linux-mmc@vger.kernel.org, Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Holger Schurig <holgerschurig@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC 1/3] DT: bindings: mmc: Add property for 3.3V only support
Date: Wed, 10 Aug 2016 13:44:51 -0500 [thread overview]
Message-ID: <20160810184451.GA13473@rob-hp-laptop> (raw)
In-Reply-To: <1470488140-10104-2-git-send-email-stefan.wahren@i2se.com>
On Sat, Aug 06, 2016 at 12:55:38PM +0000, Stefan Wahren wrote:
> Currently there is no proper way to define that a MMC host supports
> only 3.3V. The property no-1-8-v is broken and has different meanings
> for different sdhci variants. So add a new property for 3.3V only
> support and mark no-1-8-v as deprecated.
Why is it broken? How would I override a controller saying 1.8V is
supported and it is not?
Rob
next prev parent reply other threads:[~2016-08-10 18:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 12:55 [PATCH RFC 0/3] mmc: mxs-mmc: Implement DDR support Stefan Wahren
2016-08-06 12:55 ` [PATCH RFC 1/3] DT: bindings: mmc: Add property for 3.3V only support Stefan Wahren
2016-08-10 18:44 ` Rob Herring [this message]
2016-08-10 20:27 ` Stefan Wahren
[not found] ` <853617027.179290.63a6f478-ad48-40c8-82ca-760dd1afc040.open-xchange-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2016-08-10 21:39 ` Rob Herring
[not found] ` <CAL_JsqJ09hXYrp_pgAw9FXrBv+=grkm_zip6qB9XefujPECTxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-08-11 0:48 ` Shawn Lin
2016-08-18 12:25 ` Adrian Hunter
2016-08-30 9:26 ` Ulf Hansson
2016-09-02 18:50 ` Stefan Wahren
[not found] ` <1736517218.106027.c3e46c0d-6759-48dd-92a9-ce98ef74d48a.open-xchange-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2016-09-08 16:44 ` Rob Herring
2016-08-06 12:55 ` [PATCH RFC 2/3] mmc: core: add new cap for 3.3V only DDR MMCs Stefan Wahren
2016-08-06 13:14 ` Marek Vasut
2016-08-06 14:18 ` Stefan Wahren
2016-08-06 14:42 ` Marek Vasut
[not found] ` <16443443.114784.752d0f22-93a7-46e8-bb14-c884787aaea3.open-xchange-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2016-08-07 2:07 ` Shawn Lin
[not found] ` <7284d9a4-164d-dd2d-b9a0-dd1de6c76274-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-08-07 8:09 ` Stefan Wahren
2016-08-11 11:12 ` Jaehoon Chung
2016-08-11 11:57 ` Stefan Wahren
2016-08-06 12:55 ` [PATCH RFC 3/3] mmc: mxs-mmc: Implement DDR support Stefan Wahren
2016-08-06 13:13 ` Marek Vasut
2016-08-06 14:08 ` Stefan Wahren
2016-08-06 13:10 ` [PATCH RFC 0/3] " Marek Vasut
2016-08-06 13:48 ` Stefan Wahren
2016-08-07 11:37 ` Stefan Wahren
[not found] ` <1470488140-10104-1-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2016-08-27 19:15 ` Stefan Wahren
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=20160810184451.GA13473@rob-hp-laptop \
--to=robh@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=holgerschurig@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=otavio@ossystems.com.br \
--cc=shawnguo@kernel.org \
--cc=stefan.wahren@i2se.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