Messages in this thread | | | Subject | Re: [PATCH 01/10] -mm: clocksource: increase initcall priority | From | OGAWA Hirofumi <> | Date | Sun, 08 Oct 2006 04:19:52 +0900 |
| |
Daniel Walker <dwalker@mvista.com> writes:
> On Sun, 2006-10-08 at 03:41 +0900, OGAWA Hirofumi wrote: > >> >>> >> >>> We'll need to change it. >> >> >> >> We can add a call to clocksource_rating_change() inside >> >> acpi_pm_need_workaround(), are there deeper dependencies? >> > >> > There is no deeper dependencies. If it's meaning >> > clocksource_reselect() in current git, it sounds good to me. >> >> Ah, I was forgetting why I didn't before. If it's a buggy pmtmr, we'll >> get corrupted time until re-selecting the clocksource. >> >> If anybody doesn't care this will be good with it. If not, we would >> need to back to old one. IIRC, John did it. > > We could just reverse it, use the verified read function until we know > it's a good PM timer, then switch to the faster read function.
Yes, we did it in old timer code. -- OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> - 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/
| |