Message ID | 1534511968-19634-1-git-send-email-uli+renesas@fpond.eu (mailing list archive) |
---|---|
Headers | show |
Series | H3/M3-W cpuidle support | expand |
Hi Uli, On Fri, Aug 17, 2018 at 3:19 PM Ulrich Hecht <uli+renesas@fpond.eu> wrote: > This series adds CPU idle support for H3 and M3-W. It's a straight > up-port from the BSP. Thanks for your series! > The part that disables cpuidle for the CA53 cores on M3ULCB is a bit > dodgy. Is it a valid assumption that all M3ULCB boards have an ES1.0 > SoC? Alternatively, is this something that can be handled in the kernel using soc_device_match()? Gr{oetje,eeting}s, Geert
Hi Uli, (with Khiem's address fixed (hopefully)) On Thu, Aug 23, 2018 at 10:22 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote: > On Fri, Aug 17, 2018 at 3:19 PM Ulrich Hecht <uli+renesas@fpond.eu> wrote: > > This series adds CPU idle support for H3 and M3-W. It's a straight > > up-port from the BSP. > > Thanks for your series! > > > The part that disables cpuidle for the CA53 cores on M3ULCB is a bit > > dodgy. Is it a valid assumption that all M3ULCB boards have an ES1.0 > > SoC? > > Alternatively, is this something that can be handled in the kernel using > soc_device_match()? Given many Salvator-X boards (incl. mine) also have M3-W ES1.0, and PSCI is involved, I have to ask: is this a hardware (M3-W ES1.0) or firmware (PSCI) issue? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds