Pierre Ossman wrote:
> Mark Lord wrote:
>> But.. in the middle of all of this, we now see the SHDCI code
>> trying to talk to its as-yet-not-restored device, and being rather
>> noisy about it all:
>>
>
> Not quite. I'd say it's the kernel calling the interrupt handler of a
> currently sleeping device. Since we're seeing this problem I assume the
> kernel's interrupt code isn't aware of PM states?
>
Hmm... I guess it can't be as the interrupt handler isn't associated with a
device, just a random pointer.
So either release the interrupt (which seems a bit unsafe as then we might not
get it back), or handle states at the start of the isr.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
