mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: "Wappler Marcel" <Marcel.Wappler@bridgeco.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MMC: Card detection through pin CD/DAT3 issue
Date: Tue, 18 Mar 2008 13:47:59 +0100	[thread overview]
Message-ID: <20080318134759.04450604@mjolnir.drzeus.cx> (raw)
In-Reply-To: <83116F0A4FF67A4F97BA0B6E408C48E301DAB4DF@zuerich.BC-Int.NET>

On Tue, 18 Mar 2008 13:24:33 +0100
"Wappler Marcel" <Marcel.Wappler@bridgeco.net> wrote:

> 
> I have found this requirement in the SD host controller spec:
> "The card detect is active regardless of the SD Bus Power."
> 
> I wonder how the card should be able to pull up the CD/DAT3 Pad to VCC
> if its only VCC pad is not connected to VCC due to the fact that the host
> controller has switched off the cards power - any idea how this could be
> managed?

It could provide a very low voltage and current, just enough to probe the resistor but not enough to actually power anything on the card.

> 
> There is a SD card spec section somewhere which statet that:
> "If one of the supply pins (VDD or VSS) is not connected properly, then
> the current is drawn through a data line to supply the card."
> 
> Maybe this is the key in understanding ho the pull up without VCC connected
> works?
> 

I think that's just a warning that the supply pins need to be grounded when power is disabled. I have a controller where they are left floating, and some cards do indeed power up using power from the data line pull-ups. The end results is a heavily malfunctioning card due to insufficient power supply.

Most of this card detection using DAT3 business is unknown to me. The spec that describes how it is supposed to work is not publicly available, so I can only speculate.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

  reply	other threads:[~2008-03-18 12:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 10:59 Wappler Marcel
2008-03-18 11:20 ` Pierre Ossman
2008-03-18 12:24   ` Wappler Marcel
2008-03-18 12:47     ` Pierre Ossman [this message]
     [not found] <a8HRS-1KI-17@gated-at.bofh.it>
     [not found] ` <a8Ibj-2w0-17@gated-at.bofh.it>
     [not found]   ` <a8J7c-4QO-1@gated-at.bofh.it>
2008-03-18 23:08     ` Bodo Eggert
2008-03-19  8:41       ` Wappler Marcel
2008-03-20  7:27         ` Bodo Eggert

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=20080318134759.04450604@mjolnir.drzeus.cx \
    --to=drzeus-mmc@drzeus.cx \
    --cc=Marcel.Wappler@bridgeco.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®