public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: New wake ups from sky2
       [not found] ` <20070720225038.7635da3f@oldman>
@ 2007-07-21  9:00   ` Thomas Meyer
  2007-07-22 20:06     ` Stephen Hemminger
  0 siblings, 1 reply; 2+ messages in thread
From: Thomas Meyer @ 2007-07-21  9:00 UTC (permalink / raw)
  To: Stephen Hemminger, Linux Kernel Mailing List

Stephen Hemminger schrieb:
> Thomas Meyer <thomas@m3y3r.de> wrote:
>
>   
>> Today i did a git pull to be up to date again and i noticed in the
>> powertop tool that i'll get this new entry
>>
>>   14,2% (  9,1)     <kernel core> : sky2_probe (sky2_idle)
>>
>> with around 10 interrupts per second.
>>
>> i think (i.e. i don't know and just guessing!) this commit is
>> responsible for these wake ups:
>>
>> git show eb35cf60e462491249166182e3e755d3d5d91a28
>>
>> Author: Stephen Hemminger <shemminger@osdl.org>
>> Date:   Tue Jun 13 17:17:31 2006 +0900
>>
>>     [PATCH] sky2: stop/start hardware idle timer on suspend/resume
>>
>>     The resume bug was caused not by an early interrupt but because the idle
>>     timeout was not being stopped on suspend.  Also disable hardware IRQ's
>>     on suspend.  Will need to revisit this with hotplug?
>>
>>     Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
>>     Signed-off-by: Linus Torvalds <torvalds@osdl.org>
>>
>> Any ideas?
>>
>>     
>
> Last version has idle timer enabled.
> It is a tradeoff between device hanging due to lost interrupt or wasting power.
> You can make the timeout longer by setting idle_timeout module parameter larger,
> (or zero which will disable it).
>   
Ok. But do you need to start the timer when no cable is plugged in, like
in the case above?

mfg
thomas


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: New wake ups from sky2
  2007-07-21  9:00   ` New wake ups from sky2 Thomas Meyer
@ 2007-07-22 20:06     ` Stephen Hemminger
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2007-07-22 20:06 UTC (permalink / raw)
  To: Thomas Meyer; +Cc: Linux Kernel Mailing List

On Sat, 21 Jul 2007 11:00:38 +0200
Thomas Meyer <thomas@m3y3r.de> wrote:

> Stephen Hemminger schrieb:
> > Thomas Meyer <thomas@m3y3r.de> wrote:
> >
> >   
> >> Today i did a git pull to be up to date again and i noticed in the
> >> powertop tool that i'll get this new entry
> >>
> >>   14,2% (  9,1)     <kernel core> : sky2_probe (sky2_idle)
> >>
> >> with around 10 interrupts per second.
> >>
> >> i think (i.e. i don't know and just guessing!) this commit is
> >> responsible for these wake ups:
> >>
> >> git show eb35cf60e462491249166182e3e755d3d5d91a28
> >>
> >> Author: Stephen Hemminger <shemminger@osdl.org>
> >> Date:   Tue Jun 13 17:17:31 2006 +0900
> >>
> >>     [PATCH] sky2: stop/start hardware idle timer on suspend/resume
> >>
> >>     The resume bug was caused not by an early interrupt but because the idle
> >>     timeout was not being stopped on suspend.  Also disable hardware IRQ's
> >>     on suspend.  Will need to revisit this with hotplug?
> >>
> >>     Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
> >>     Signed-off-by: Linus Torvalds <torvalds@osdl.org>
> >>
> >> Any ideas?
> >>
> >>     
> >
> > Last version has idle timer enabled.
> > It is a tradeoff between device hanging due to lost interrupt or wasting power.
> > You can make the timeout longer by setting idle_timeout module parameter larger,
> > (or zero which will disable it).
> >   
> Ok. But do you need to start the timer when no cable is plugged in, like
> in the case above?

Probably not, because risk of missed PHY interrupt is miniscule.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-07-22 20:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <46A10CC3.6050909@m3y3r.de>
     [not found] ` <20070720225038.7635da3f@oldman>
2007-07-21  9:00   ` New wake ups from sky2 Thomas Meyer
2007-07-22 20:06     ` Stephen Hemminger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox