linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH/RFC 0/4] pinctrl: sh-pfc: Add PINMUX_SINGLE()
Date: Wed, 25 Nov 2015 11:14:00 +0100	[thread overview]
Message-ID: <CAMuHMdWKcBbRwkgFxfatgPF2UFo2OTGAJ0wp3Q8sOGCXWB5SiA@mail.gmail.com> (raw)
In-Reply-To: <2326541.taAcxUkgxs@avalon>

Hi Laurent,

On Wed, Nov 25, 2015 at 1:48 AM, Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
> On Tuesday 20 October 2015 21:26:31 Geert Uytterhoeven wrote:
>> 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!
>
> For patches 2-4,
>
> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

Thanks!

> But why haven't you included the other SoCs ?

Because this was an RFC. Didn't want to look for more occurrences if my RFC
was rejected.

Seems like there are indeed more possible users on emev2, r8a778, r8a7779,
and sh7734.

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-11-25 10:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 19:26 [PATCH/RFC 0/4] pinctrl: sh-pfc: Add PINMUX_SINGLE() Geert Uytterhoeven
2015-10-20 19:26 ` [PATCH/RFC 1/4] " 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 [this message]

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=CAMuHMdWKcBbRwkgFxfatgPF2UFo2OTGAJ0wp3Q8sOGCXWB5SiA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=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).