linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: libertas-dev@lists.infradead.org
Cc: linux-mmc@vger.kernel.org
Subject: libertas: DAT1 signal IRQ in 1-bit SDIO mode
Date: Mon, 29 Mar 2010 20:24:14 +0200	[thread overview]
Message-ID: <20100329182414.GJ30801@buzzloop.caiaq.de> (raw)

Hi,

I'm still fighting with a MX31 SDHC controller connected to a 8686
module via SDIO. As the libertas firmware uses multiblock transfers,
this can't work in 4bit SDIO mode due to a bug in the SDHC controller
of the MX31 silicon. This is now finally also confirmed by Freescale.

So the only way around this is to use 1-bit transfers. This appears to
work stable now as long as I don't let the host controller announce the
capability of serving SDIO IRQs (MMC_CAP_SDIO_IRQ). The IRQ flag is then
polled by the MMC core which is a performance drawback of course, but at
least it finally works.

However, I also implemented code for proper SDIO IRQ hardware handling
for this controller, but the hardware condition is never triggered. I
measured with an oscilloscope and found out the 8686 does not actually
drive the DAT1 line (which is used as IRQ in 1-bit SDIO mode) low when
it is supposed to do.

My question is - did anyone ever use the chip in this mode? Is that a
firmware bug?

Any pointers appreciated - I would like to post my pending patches for
that issue asap, but need to clear that last issue first.

Thanks,
Daniel


             reply	other threads:[~2010-03-29 18:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 18:24 Daniel Mack [this message]
     [not found] ` <4BB0FE7A.6090709@embwise.com>
2010-03-30  9:05   ` libertas: DAT1 signal IRQ in 1-bit SDIO mode Daniel Mack
2010-03-30 17:50   ` Daniel Mack

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=20100329182414.GJ30801@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-mmc@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;
as well as URLs for NNTP newsgroup(s).