linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan <kungjohan@gmail.com>
To: linux-mmc@vger.kernel.org
Subject: Problem when using SDIO interrupts on Nexus One
Date: Thu, 7 Apr 2011 21:23:19 +0200	[thread overview]
Message-ID: <BANLkTin2cVt7236-Ds+3Wg0SsCuSSSZGsg@mail.gmail.com> (raw)

I have a Nexus One Android phone and I am trying to use a SDIO device
connected to the memory slot available on the phone. This device uses
SDIO interrupts on SD_D1 to signal interrupts to the host.

I am using a 2.6-32 kernel from the android-msm-2.6.32 branch
available fromgit://android.git.kernel.org/kernel/msm.git and has
built the kernel with the mahimahi_defconfig.

I have modified drivers/mmc/host/msm_sdcc.c so that SDIO interrupts is
used -> msmsdcc_sdioirq = 1;

My device is working quite well with SDIO interrupts but sometime I
can miss a interrupt and will get this interrupt when I try to send a
command to my device. I can see this behaviour if my device tries to
signal a interrupt 1 second of the last command sent to the device.
The SDIO interrupt line goes low and the host does not signal the
interrupt at once. My assumption is that this is due to some kind of
power management of the SDIO controller. I will get this interrupt
when I activate the SDIO controller by sending a command to my device.
 I have verified this with a logic analyzer attached to the bus and
can attach a screen shot if anyone wants to see this.

So my question is if anyone know how to get reliable SDIO interrupts
on this host, Qualcomm MSM? It seems like Qualcomm does not provide
documentation for this host.

Best Regards
Johan

             reply	other threads:[~2011-04-07 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 19:23 Johan [this message]
2011-04-11 12:08 ` Problem when using SDIO interrupts on Nexus One Subhash Jadavani
2011-04-13 10:07   ` Subhash Jadavani

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=BANLkTin2cVt7236-Ds+3Wg0SsCuSSSZGsg@mail.gmail.com \
    --to=kungjohan@gmail.com \
    --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).