Hi, Currently single-function pins are described using the raw PINMUX_DATA() macro.
Morimoto-san doesn't like that. He proposed to use the existing PINMUX_IPSR_NOGP() macro instead (cfr. "[RFC] pinctrl: sh-pfc: r8a7795: Add pinmux data for single-function pins", http://www.spinics.net/lists/linux-sh/msg44823.html). However, that macro is intended to describe a pinmux configuration without GPIO function, which feels wrong to me. This patch series proposes an alternative, introducing a new macro PINMUX_SINGLE() to describe a pinmux configuration for a single-function pin. It also converts the existing single-function pin descriptions. Thanks for your comments! Geert Uytterhoeven (4): pinctrl: sh-pfc: Add PINMUX_SINGLE() pinctrl: sh-pfc: r8a7790: Use PINMUX_SINGLE() instead of raw PINMUX_DATA() pinctrl: sh-pfc: r8a7791: Use PINMUX_SINGLE() instead of raw PINMUX_DATA() pinctrl: sh-pfc: r8a7794: Use PINMUX_SINGLE() instead of raw PINMUX_DATA() drivers/pinctrl/sh-pfc/pfc-r8a7790.c | 18 +++++++-------- drivers/pinctrl/sh-pfc/pfc-r8a7791.c | 34 ++++++++++++++-------------- drivers/pinctrl/sh-pfc/pfc-r8a7794.c | 44 ++++++++++++++++++------------------ drivers/pinctrl/sh-pfc/sh_pfc.h | 7 ++++++ 4 files changed, 55 insertions(+), 48 deletions(-) -- 1.9.1 Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@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 -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
