Re: [PATCH 1/3] PM / QoS: Make it possible to expose PM QoS latency constraints

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 8 Mar 2012, Kevin Hilman wrote:

> >> > The word "wakeup" may refer to many different things, as well as the word
> >> > "resume". :-)
> >> 
> >> Yes, but what's the confusion in this case?
> >> 
> >> IMO, The existing /sys/devices/.../power/wakeup* meaning is the same
> >> meaning as as for the wakeup latency in this patch,
> >
> > No, it is not.  They refer to system wakeup. :-)
> 
> OK, now I'm confused (again).  I thought those could be used for runtime
> PM wakeups also.  At least I was planning on using them for any kind of
> wakeup.
> 
> >> so I don't understand where the confusion would be.
> >
> > See above. ;-)
> 
> Sheesh, this is getting ugly.
> 
> So wakeup*  attributes refer to system resume and resume* attribues
> refer to runtime PM.
> 
> Yuck.

How about calling it "runtime latency"?  Or "runtime wakeup latency" in 
case people think there might be some other sort of latency associated 
with runtime power management.

Alan Stern

--
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


[Index of Archives]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux