Messages in this thread | | | Subject | Re: keyboard and USB problems (Re: 2.6.2-rc1-mm2) | From | john stultz <> | Date | Fri, 23 Jan 2004 12:15:03 -0800 |
| |
On Fri, 2004-01-23 at 11:54, Vojtech Pavlik wrote: > On Fri, Jan 23, 2004 at 11:27:41AM -0800, john stultz wrote: > > Well, loops_per_jiffy is actually being measured correctly as we're > > using the acpi pm timesource to time udelay(). However there is a loss > > of resolution using the slower time source, so udelay(1) might take > > longer then 1 us. > > Longer udelay shouldn't cause trouble. Shorter one definitely would.
Hmm.
> > If that is going to cause problems, then we'll need to pull out the > > use-pmtmr-for-delay_pmtmr patch. I guess our only option is then to use > > the TSC for delay_pmtrm() (as a loop based delay fails in other cases). > > I'll write that up and send it your way, Andrew. > > I've seen the PM timer breaking the mouse operation rather badly in the > past, the lost-sync check was triggering for many people when the PM > timer was used. This implies time inacurracy in the range of 0.5 > seconds. Could that happen somehow?
Not in a way that I yet understand. Do you see similar problems with folks using clock=pit?
thanks -john
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |