On Mon, Jul 9, 2018 at 8:24 PM Kevin Hilman <[email protected]> wrote: > > On Mon, Jul 9, 2018 at 8:45 AM Sudeep Holla <[email protected]> wrote: > > > > This reverts commit 1332a90558013ae4242e3dd7934bdcdeafb06c0d. > > > > The original issue was not because of incorrect checking of cpumask for > > both new and old tick device. It was incorrectly analysed was due to the > > misunderstanding of the comment and misinterpretation of the return > > value from tick_check_preferred. The main issue is with the clockevent > > driver that sets the cpumask to cpu_all_mask instead of cpu_possible_mask. > > > > Cc: Thomas Gleixner <[email protected]> > > Signed-off-by: Sudeep Holla <[email protected]> > > Tested-by: Kevin Hilman <[email protected]> Tested-by: Martin Blumenstingl <[email protected]>
> And verified to fix a regression on the 32-bit ARM platform mesion8b-odroidc1. I also tested it on Meson8b as well as Meson8m2 Regards Martin
