From: Chris Ball <cjb@laptop.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Shawn Guo <shawn.guo@linaro.org>,
linux-samsung-soc@vger.kernel.org, patches@linaro.org,
devicetree-discuss@lists.ozlabs.org, linux-mmc@vger.kernel.org,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH] mmc: dt: Add 'broken-cd' DT binding
Date: Wed, 22 Aug 2012 10:58:51 -0400 [thread overview]
Message-ID: <87d32j2ct0.fsf@octavius.laptop.org> (raw)
In-Reply-To: <5034F2AD.7060801@wwwdotorg.org> (Stephen Warren's message of "Wed, 22 Aug 2012 08:54:37 -0600")
Hi Stephen,
On Wed, Aug 22 2012, Stephen Warren wrote:
> On 08/22/2012 04:17 AM, Chris Ball wrote:
>> Hi,
>>
>> On Wed, Aug 22 2012, Shawn Guo wrote:
>>> The following is what I have on my mind.
>>>
>>> broken-cd cd-gpios implication
>>> -------------------------------------------
>>> no no SDHCI CD
>>> no yes GPIO CD
>>> yes no NO CD / Broken CD
>>> yes yes Invalid
>>>
>>> yes: property presents
>>> no: property does not present
>>
>> This matches Mitch's last suggestion exactly -- I think we're all agreed
>> on these properties now. The only remaining question is how to handle
>> the pinctrl for CD in Thomas's case.
>
> Sorry if this has already been mentioned, but I assume the standard
> non-removable property overrides any of those, or is invalid in
> combination with any of those?
Yes, absolutely. I'll make sure to explain that in the new version of
the document. (I think the reason it hasn't been mentioned much in this
thread is that it's already part of the core bindings.)
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-08-22 14:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 11:09 [PATCH] mmc: dt: Add 'broken-cd' DT binding Thomas Abraham
2012-08-21 11:01 ` Arnd Bergmann
2012-08-21 11:14 ` Chris Ball
2012-08-21 11:14 ` Thomas Abraham
2012-08-21 11:56 ` Chris Ball
2012-08-21 12:08 ` Arnd Bergmann
2012-08-21 14:21 ` Rob Herring
2012-08-21 14:48 ` Chris Ball
2012-08-21 15:03 ` Rob Herring
2012-08-21 15:18 ` Chris Ball
2012-08-21 16:01 ` Rob Herring
2012-08-21 17:33 ` Thomas Abraham
[not found] ` <CAJuYYwR+oCQUcgoy6ZuHp0XAa+EAj9d-FvLtwsQcP3muFMrKLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-21 18:32 ` Mitch Bradley
2012-08-22 5:51 ` Shawn Guo
2012-08-22 10:17 ` Chris Ball
2012-08-22 10:51 ` Thomas Abraham
2012-08-22 11:08 ` Chris Ball
2012-08-22 12:04 ` Thomas Abraham
2012-08-22 14:54 ` Chris Ball
2012-08-22 14:59 ` Thomas Abraham
2012-08-22 18:05 ` [PATCH] mmc: dt: Add card-detection properties to core binding Chris Ball
2012-08-24 5:44 ` Shawn Guo
[not found] ` <CAJuYYwQLUs5qb8NqtPf3=ytNHJ_VdnN8Z4yWwyk2+OTftdWFXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-08-22 17:09 ` [PATCH] mmc: dt: Add 'broken-cd' DT binding Mitch Bradley
2012-08-23 6:59 ` Thomas Abraham
2012-08-22 14:54 ` Stephen Warren
2012-08-22 14:58 ` Chris Ball [this message]
2012-08-21 15:21 ` Thomas Abraham
2012-08-22 6:00 ` Shawn Guo
2012-08-22 12:26 ` Shawn Guo
2012-08-22 13:54 ` Chris Ball
2012-08-21 12:30 ` Thomas Abraham
2012-08-21 11:09 ` Thomas Abraham
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=87d32j2ct0.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.org \
--cc=w.sang@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.