On Mon, Jul 23, 2012 at 2:19 AM, Will Newton wrote:
>> Very good question. In my current setup I don't see setup_bus()
>> called during normal operation. If it were, my kernel messages would
>> be constantly spammed with messages like:
>> Bus speed (slot %d) = %dHz (slot req %dHz, actual %dH
On Mon, Jul 23, 2012 at 3:48 AM, Doug Anderson wrote:
> On Sat, Jul 21, 2012 at 3:40 AM, Will Newton wrote:
>>> static void dw_mci_enable_sdio_irq(struct mmc_host *mmc, int enb)
>>> {
>>> struct dw_mci_slot *slot = mmc_priv(mmc);
>>> @@ -871,6 +896,14 @@ static void dw_mci_enable_sdio_i
On Sat, Jul 21, 2012 at 3:40 AM, Will Newton wrote:
>> static void dw_mci_enable_sdio_irq(struct mmc_host *mmc, int enb)
>> {
>> struct dw_mci_slot *slot = mmc_priv(mmc);
>> @@ -871,6 +896,14 @@ static void dw_mci_enable_sdio_irq(struct mmc_host
>> *mmc, int enb)
>> /* Enable/di
On Fri, Jul 20, 2012 at 7:13 PM, Doug Anderson wrote:
> The documentation for the dw_mmc part says that the low power
> mode should normally only be set for MMC and SD memory and should
> be turned off for SDIO cards that need interrupts detected.
>
> The best place I could find to do this is when
The documentation for the dw_mmc part says that the low power
mode should normally only be set for MMC and SD memory and should
be turned off for SDIO cards that need interrupts detected.
The best place I could find to do this is when the SDIO interrupt
was first enabled. I rely on the fact that
5 matches
Mail list logo
