From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 1/3] DT: bindings: mmc: Add property for 3.3V only support
Date: Wed, 10 Aug 2016 22:27:04 +0200 (CEST) [thread overview]
Message-ID: <853617027.179290.63a6f478-ad48-40c8-82ca-760dd1afc040.open-xchange@email.1und1.de> (raw)
In-Reply-To: <20160810184451.GA13473@rob-hp-laptop>
Hi,
> Rob Herring <robh@kernel.org> hat am 10. August 2016 um 20:44 geschrieben:
>
>
> 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?
i want to quote Ulf Hansson here [1]:
The problem with the "no-1-8-v" binding is that it's describing what
the hardware *can't* do. It thus becomes easy to abuse it.
I suggest we stop using it, we should mark it deprecated.
[1] - http://www.spinics.net/lists/linux-mmc/msg34604.html
> How would I override a controller saying 1.8V is
> supported and it is not?
Sorry, i'm not sure that i understand your question. In case a board or a MMC
controller doesn't support 1.8V, it usually supports only 3.3V which is the
intension of this patch.
>
> Rob
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2016-08-10 20:27 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
2016-08-10 20:27 ` Stefan Wahren [this message]
2016-08-10 21:39 ` Rob Herring
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
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
2016-08-07 2:07 ` Shawn Lin
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
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=853617027.179290.63a6f478-ad48-40c8-82ca-760dd1afc040.open-xchange@email.1und1.de \
--to=stefan.wahren@i2se.com \
--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).