From: Rob Emanuele <poorarm@shoreis.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
Andrew Victor <avictor.za@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org, drzeus-mmc@drzeus.cx
Subject: Re: [PATCH 5/6] Unified AVR32/AT91 MCI Driver Support for a VCC Pin
Date: Mon, 15 Jun 2009 11:17:36 -0700 [thread overview]
Message-ID: <c8284b5b0906151117j14c0ced0oe7530d9cce33d5bd@mail.gmail.com> (raw)
In-Reply-To: <4A3674B0.8050004@atmel.com>
Nicolas,
On Mon, Jun 15, 2009 at 9:20 AM, Nicolas Ferre<nicolas.ferre@atmel.com> wrote:
> Rob Emanuele :
>> Add support to the atmel-mci driver for a VCC pin in order to conserve
>> power if the MMC interface is powered down.
>
> Can you elaborate a bit more. In particular, I do not understand the
> concept of "vcc_pin_act_low".
>
Like the original at91_mci driver, this patch adds the ability to use
a pin to toggle 3.3V power going to the SD Card. In my case the pin
is tied to a International Rectifier 6420 P-type MOSFET since a port
pin alone cannot drive the SD Card. When I pull the vcc_pin low, 3.3V
can reach the SD Card to power it. The "vcc_pin_act_low" (pin active
low) determines which way the pin should be pulled to enable power to
the SD Card. If vcc_pin_act_low is true, when the card needs to get
powered up, it sets the vcc_pin low. Other board designs may need a
pin driven high to power the SD Card.
Thanks,
Rob
next prev parent reply other threads:[~2009-06-15 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 1:02 Rob Emanuele
2009-06-15 16:20 ` Nicolas Ferre
2009-06-15 18:17 ` Rob Emanuele [this message]
2009-06-15 21:35 ` Michael Roth
2009-06-15 22:16 ` Rob Emanuele
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=c8284b5b0906151117j14c0ced0oe7530d9cce33d5bd@mail.gmail.com \
--to=poorarm@shoreis.com \
--cc=avictor.za@gmail.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.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
all inboxes | Powered by JetHome®