From: Chris Ball <cjb@laptop.org>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 0/3] adding write_protect and card_detect for mx25/35
Date: Mon, 28 Feb 2011 15:55:40 -0500 [thread overview]
Message-ID: <m3r5ar281f.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <1298727881-12141-1-git-send-email-w.sang@pengutronix.de> (Wolfram Sang's message of "Sat, 26 Feb 2011 14:44:38 +0100")
Hi Wolfram,
On Sat, Feb 26 2011, Wolfram Sang wrote:
> Last tests showed some problems with MX51, especially with card_detect. While
> the approach in general will suffice for i.MX5x, it seems there are a few
> details missing right now. Because I do not have the resources (both time and
> hardware) to deal with these issues, I propose a step by step approach. Let's
> add the functionality for mx25/35 first and make sure there is no difference in
> behaviour for mx5x. (Note that the i.MX5x can route the pins directly to the
> controller, so a properly designed board should not need these gpio-additions.)
> That is what this patch series does: The main change is that mx5x won't notice
> any difference. For mx25/35, it is the same as it has been tested by Eric and
> Marc.
>
> Thanks to all involved in providing feedback, I hope it can go in now. If you
> want to add support for it to your board, please CC me.
Thanks, pushed to mmc-next for .39 now.
- Chris.
--
Chris Ball <cjb@laptop.org>
One Laptop Per Child
prev parent reply other threads:[~2011-02-28 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 13:44 [PATCH V4 0/3] adding write_protect and card_detect for mx25/35 Wolfram Sang
2011-02-26 13:44 ` [PATCH 1/3] mmc: sdhci-esdhc-imx: add support for write protect on custom GPIO on mx25/35 Wolfram Sang
2011-02-26 13:44 ` [PATCH 2/3] mmc: sdhci-esdhc: broken card detection is not a default quirk Wolfram Sang
2011-02-26 13:44 ` [PATCH 3/3] mmc: sdhci-esdhc-imx: add card detect on custom GPIO for mx25/35 Wolfram Sang
2011-02-28 20:55 ` Chris Ball [this message]
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=m3r5ar281f.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox