On Tue, Nov 20, 2018 at 10:00 AM Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx> wrote:
If you use one timer as a clock event device and the other as a clocksource, there are no timers left to run the existing timer_interrupt() handler. So this arrangement would require GENERIC_CLOCKEVENTS=y, right?
I think so, yes.
Then, wouldn't all relevant platforms have to support GENERIC_CLOCKEVENTS=y, if a single binary was to support all of those platforms?
Good point. I wonder of there is a path forward where we could have peaceful GENERIC_CLOCKEVENTS and !GENERIC_CLOCKEVENTS co-existence. Yours, Linus Walleij
