> -----Original Message----- > From: Paul Walmsley [mailto:paul@xxxxxxxxx] > Sent: Thursday, February 18, 2010 11:44 AM > To: David Vrabel > Cc: Madhusudhan; linux-mmc@xxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 3/3] mmc: omap_hsmmc: enable SDIO card interrupts > > On Thu, 18 Feb 2010, David Vrabel wrote: > > > Paul Walmsley wrote: > > > > > > Perhaps I'm misunderstanding what you're referring to, but it seems > there > > > is some confusion as to what target smart-idle mode does. > > > > The TI OMAP 34xx TRM is the one of the most obtuse document I've had to > > read. An even after multiple reads of relevant sections it still > > doesn't make sense. Parts are contradictory, parts are poorly explained > > and some bit are just plain incorrect. > > Yes. TI needs to also release the functional specifications for each IP > block; the information in the current TRM is generally insufficient to > write high-quality drivers. > > TI should also host a process, open to the public, to submit TRM revision > and clarification requests, and to track their disposition. > Paul, David, Not to add further confusion but as far as I understand SDIO should be able to asynchronously wakeup OMAP regardless of MMC clocks being OFF . As per the SDIO spec DAT1 line is used for signaling the card interrupt to the host. The TRM clearly shows a GPIO connected to DAT1 line for wakeup through the SDIO interrupt. Wouldn't this help? > > I don't have time to sort out any of this properly -- it works well > > enough for me. > > Thanks very much for the SDIO patches. They are appreciated. Definitely these are good features that are being added. Just that there are confusions around and not everyone has a setup to validate these features. If I look in the mainline kernel today there is only one SDIO card driver " sdio_uart.c". And at least I don't see a way I can test any of these features myself. Regards, Madhu > > > - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
