From: Antonio Ospite <ospite@studenti.unina.it>
To: linux-mmc@vger.kernel.org
Cc: Antonio Ospite <ospite@studenti.unina.it>,
Daniel Ribeiro <drwyrm@gmail.com>,
David Brownell <dbrownell@users.sourceforge.net>,
Chris Ball <cjb@laptop.org>,
Grant Likely <grant.likely@secretlab.ca>,
Ernst Schwab <eschwab@online.de>,
Sonic Zhang <sonic.zhang@analog.com>,
Linus Walleij <linus.walleij@stericsson.com>,
openezx-devel@lists.openezx.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] mmc_spi: Add support for regulator framework
Date: Mon, 4 Apr 2011 11:56:31 +0200 [thread overview]
Message-ID: <20110404115631.67b1f317.ospite@studenti.unina.it> (raw)
In-Reply-To: <1300733202-27316-1-git-send-email-ospite@studenti.unina.it>
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
On Mon, 21 Mar 2011 19:46:38 +0100
Antonio Ospite <ospite@studenti.unina.it> wrote:
> Hi,
>
> this patchset has the purpose of adding support for the regulator framework to
> the mmc_spi driver. The first three patches are preparatory cleanups to make
> the fourth one more straightforward.
>
> Maybe the fourth patch can be improved, I am open to any suggestions about it.
>
Ping. I forgot to Cc spi-devel-general on this series, should I resend
it?
> These changes take strong inspiration from the pxamci driver; they have been
> tested on a Motorola A910, which uses a regulator to powerup the MMC card
> connected to the SPI bus, a test from a current user of the mmc_spi driver
> would not hurt just to be sure no regressions have been introduced.
>
> Thanks,
> Antonio
>
> Antonio Ospite (4):
> mmc_spi.c: factor out the check for power capability
> mmc_spi.c: factor out the SD card shutdown sequence
> mmc_spi.c: factor out a mmc_spi_setpower() function
> mmc_spi.c: add support for the regulator framework
>
> drivers/mmc/host/mmc_spi.c | 194 +++++++++++++++++++++++++++++---------------
> 1 files changed, 129 insertions(+), 65 deletions(-)
>
--
Antonio Ospite
http://ao2.it
PGP public key ID: 0x4553B001
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-04 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 18:46 [PATCH 0/4] mmc_spi: Add support for regulator framework Antonio Ospite
2011-03-21 18:46 ` [PATCH 1/4] mmc_spi.c: factor out the check for power capability Antonio Ospite
2011-03-21 18:46 ` [PATCH 2/4] mmc_spi.c: factor out the SD card shutdown sequence Antonio Ospite
2011-03-21 18:46 ` [PATCH 3/4] mmc_spi.c: factor out a mmc_spi_setpower() function Antonio Ospite
2011-03-21 18:46 ` [PATCH 4/4] mmc_spi.c: add support for the regulator framework Antonio Ospite
2011-04-04 9:56 ` Antonio Ospite [this message]
2011-04-05 3:05 ` [PATCH 0/4] mmc_spi: Add support for " Grant Likely
2011-04-05 8:43 ` Antonio Ospite
2011-04-05 13:46 ` Grant Likely
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=20110404115631.67b1f317.ospite@studenti.unina.it \
--to=ospite@studenti.unina.it \
--cc=cjb@laptop.org \
--cc=dbrownell@users.sourceforge.net \
--cc=drwyrm@gmail.com \
--cc=eschwab@online.de \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=openezx-devel@lists.openezx.org \
--cc=sonic.zhang@analog.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).