On 04/08/2011 02:57 AM, Johan wrote: > 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 Johan, the device and tree you're referring to are owned by Google. This mailing list is for the MSM architecture in the mainline kernel. We don't have NexusOne support yet so this ML may not be able to help. That being said, I do know some developers who are familiar with this driver on other MSM targets. I'll ask around and see if I can find an answer for you. - Bryan -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
