From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Ram <vshrirama@gmail.com>
Cc: linux-kernel@vger.kernel.org, Pierre Ossman <drzeus-list@drzeus.cx>
Subject: Re: sd cards : OCR busy?
Date: Tue, 25 Apr 2006 16:00:50 +0100 [thread overview]
Message-ID: <20060425150050.GB18113@flint.arm.linux.org.uk> (raw)
In-Reply-To: <8bf247760604250741l5ee1267cg7745ef5934f48497@mail.gmail.com>
On Tue, Apr 25, 2006 at 07:41:04AM -0700, Ram wrote:
> I am using Linux 2.6.15.
>
> I am getting OCR busy Error. The driver works on some sd cards and
> does not work
> on some other cards. i really cant figure out what the problem is.
It seems that your kernel is doing something different from the code I
have in front of me.
> mmc_detect_change:
> mmc_rescan:
> __mmc_claim_host:
> mmc_setup:
> mmc_power_up:
> MMC1: set_ios: clock 400000Hz busmode 1 powermode 1 Vdd 0.21
> mmc_delay:
> MMC1: set_ios: clock 400000Hz busmode 1 powermode 2 Vdd 0.21
> mmc_delay:
> mmc_idle_cards:
> MMC1: set_ios: clock 400000Hz busmode 1 powermode 2 Vdd 0.21
Card inserted - okay.
> mmc_delay:
> mmc_wait_for_cmd:
> mmc_wait_for_req:
> mmc_omap_start_command:MMC1: CMD0, argument 0x00000000
> mmc_omap_irq:MMC IRQ 0001 (CMD 0): EOC
> MMC1: End request, err 0
Card told to go to idle state - okay.
> mmc_delay:
> MMC1: set_ios: clock 400000Hz busmode 1 powermode 2 Vdd 0.21
> mmc_delay:
> mmc_send_app_op_cond:
> mmc_wait_for_app_cmd:
> mmc_wait_for_req:
> mmc_omap_start_command:MMC1: CMD55, argument 0x00000000, 32-bit response,
> CRC
> mmc_omap_irq:MMC IRQ 1001 (CMD 55): EOC OCRB
> MMC1: OCR busy error, CMD55
> MMC1: Response 00000000
> MMC1: End request, err 0
Sent MMC_APP_CMD, got told "OCR busy" - this is bogus. APP_CMD does _not_
return an OCR. No idea why your OMAP host thinks it does.
Nevertheless, we have a zero response, but the card _did_ apparantly
respond. So we decide APP commands aren't supported.
> mmc_setup:No MMC cards found
> mmc_send_op_cond:
> mmc_wait_for_cmd:
> mmc_wait_for_req:
> mmc_omap_start_command:MMC1: CMD1, argument 0x00000000, 32-bit response
> mmc_omap_irq:MMC IRQ 1001 (CMD 1): EOC OCRB
> MMC1: Response 00000000
> MMC1: End request, err 0
We send a CMD1 to probe for the OCR. Get zero back. Zero back from a card
means "I don't support any voltage what so ever", so...
> mmc_select_voltage: ocr - 0
> mmc_release_host:
> mmc_power_off:
We power down.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2006-04-25 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 14:41 Ram
2006-04-25 15:00 ` Russell King [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=20060425150050.GB18113@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=vshrirama@gmail.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®