linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: linux-sh@vger.kernel.org, linux-gpio@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH/RFC 0/4] pinctrl: sh-pfc: Add PINMUX_SINGLE()
Date: Tue, 20 Oct 2015 21:26:31 +0200	[thread overview]
Message-ID: <1445369195-25117-1-git-send-email-geert+renesas@glider.be> (raw)

	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 -- 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

             reply	other threads:[~2015-10-20 19:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 19:26 Geert Uytterhoeven [this message]
2015-10-20 19:26 ` [PATCH/RFC 1/4] pinctrl: sh-pfc: Add PINMUX_SINGLE() Geert Uytterhoeven
2015-11-25  0:49   ` Laurent Pinchart
2015-11-30 10:44     ` Geert Uytterhoeven
2015-10-20 19:26 ` [PATCH/RFC 2/4] pinctrl: sh-pfc: r8a7790: Use PINMUX_SINGLE() instead of raw PINMUX_DATA() Geert Uytterhoeven
2015-10-20 19:26 ` [PATCH/RFC 3/4] pinctrl: sh-pfc: r8a7791: " Geert Uytterhoeven
2015-10-20 19:26 ` [PATCH/RFC 4/4] pinctrl: sh-pfc: r8a7794: " Geert Uytterhoeven
2015-10-21  1:18 ` [PATCH/RFC 0/4] pinctrl: sh-pfc: Add PINMUX_SINGLE() Kuninori Morimoto
2015-10-27 10:20 ` Linus Walleij
2015-11-25  0:48 ` Laurent Pinchart
2015-11-25 10:14   ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1445369195-25117-1-git-send-email-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).