to, 2012-11-01 kello 23:49 +0100, Wolfram Sang kirjoitti:
> Hi,
>
> > Anyway new patch coming soon :)
>
> Was there one? I have skimmed a number of threads discussing spurious
> interrupts or interrupt floods but AFAICS all discussions ended up in
> trying another approach later or fixing the is
Hi,
> Anyway new patch coming soon :)
Was there one? I have skimmed a number of threads discussing spurious
interrupts or interrupt floods but AFAICS all discussions ended up in
trying another approach later or fixing the issue somewhere else than
I2C. Is this correct? Or is there a bugfix patch
Hi,
ma, 2012-10-15 kello 18:02 -0700, Tony Lindgren kirjoitti:
> * Kevin Hilman [121015 10:32]:
> > Kalle Jokiniemi writes:
> > >
> > > Does not work for me :(
> > >
> > > As I said, the issue occurs for me when I enter static suspend (echo mem
> > >> /sys/power/autosleep or /sys/power/state). I
* Kevin Hilman [121015 10:32]:
> Kalle Jokiniemi writes:
> >
> > Does not work for me :(
> >
> > As I said, the issue occurs for me when I enter static suspend (echo mem
> >> /sys/power/autosleep or /sys/power/state). I don't think doing this
> > just in runtime pm will fix my issue. Or do those
Kalle Jokiniemi writes:
> Hi,
>
> la, 2012-10-13 kello 01:00 +0530, Shubhrajyoti Datta kirjoitti:
>> On Sat, Oct 13, 2012 at 12:10 AM, Kevin Hilman
>> wrote:
>> > From: Kevin Hilman
>> >
>> > Currently, runtime PM is used to keep the device enabled only during
>> > active transfers and for a co
Hi,
la, 2012-10-13 kello 01:00 +0530, Shubhrajyoti Datta kirjoitti:
> On Sat, Oct 13, 2012 at 12:10 AM, Kevin Hilman
> wrote:
> > From: Kevin Hilman
> >
> > Currently, runtime PM is used to keep the device enabled only during
> > active transfers and for a configurable runtime PM autosuspend tim
On Sat, Oct 13, 2012 at 12:10 AM, Kevin Hilman
wrote:
> From: Kevin Hilman
>
> Currently, runtime PM is used to keep the device enabled only during
> active transfers and for a configurable runtime PM autosuspend timout
> after an xfer.
>
> In addition to idling the device, driver's ->runtime_sus
From: Kevin Hilman
Currently, runtime PM is used to keep the device enabled only during
active transfers and for a configurable runtime PM autosuspend timout
after an xfer.
In addition to idling the device, driver's ->runtime_suspend() method
currently disables device interrupts when idle. Howe