Re: [PATCH] Remove ARCH_SHMOBILE
flat view
From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: 2016-03-02 16:08:52
Hi Magnus, On Wed, Mar 2, 2016 at 5:00 PM, Magnus Damm [off-list ref] wrote:
On Wed, Mar 2, 2016 at 6:30 PM, Geert Uytterhoeven [off-list ref] wrote:quoted
On Wed, Mar 2, 2016 at 2:55 AM, Simon Horman [off-list ref] wrote:quoted
--- a/drivers/input/keyboard/Kconfig +++ b/drivers/input/keyboard/Kconfig@@ -560,7 +560,7 @@ config KEYBOARD_SUNKBD config KEYBOARD_SH_KEYSC tristate "SuperH KEYSC keypad support" - depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST + depends on SUPERH || COMPILE_TESTI think dropping the SUPERH dependency is the right approach here, as all SuperH platforms using the driver select ARCH_SHMOBILE.Thanks, I agree!quoted
"sh_keysc" is used on SH_MIGOR, SH_ECOVEC, SH_KFR2R09, SH_7722_SOLUTION_ENGINE, and SH_7724_SOLUTION_ENGINE, which depend on either CPU_SUBTYPE_SH7722 or CPU_SUBTYPE_SH7724, and both select ARCH_SHMOBILE.quoted
help Say Y here if you want to use a keypad attached to the KEYSC block on SuperH processors such as sh7722 and sh7343.FWIW, this has never been enabled on sh7343. But CPU_SUBTYPE_SH7343 also selects ARCH_SHMOBILE, so we're safe.You are right that the SH architecture is the main consumer at this point. I do however vaguely recall ARM shmobile G3EVM and G4EVM including sh7367 and some other SoC also having a KEYSC hardware block included. Due to the iffy interrupt controller upstream support for those boards/socs were killed off quite some time ago while (not) migrating to DT. So I think this KEYSC driver is simply a left over from that time.
Note that sh73a0 also has keysc, but I don't think it's usable on kzm9g
(after a quick look at the schematics).
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