From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Michel Pollet <michel.pollet@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Phil Edworthy <phil.edworthy@renesas.com>,
Michel Pollet <buserror+upstream@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Magnus Damm <damm+renesas@opensource.se>
Subject: Re: [PATCH v1 0/5] Renesas R9A06G032 PINCTRL Driver
Date: Mon, 18 Jun 2018 10:57:18 +0200 [thread overview]
Message-ID: <CAMuHMdVL-00gb7ZfgNGr8-VawFUpg+iY5mpPF6UZPfjFqM1_jg@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdbX0R+ipasLfZi80yf2OBU0TuDT-0KoUJBvrQz3Zj6eFQ@mail.gmail.com>
Hi Linus,
On Mon, Jun 18, 2018 at 10:46 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> On Thu, Jun 14, 2018 at 1:00 PM, Michel Pollet
> <michel.pollet@bp.renesas.com> wrote:
>
> > *WARNING* -- this requires:
> > + R9A06G032 base patch v9
> > + R9A06G032 SMP patch v5
>
> Is that required for the pin controller itself (compile-time dependence)
> or is it required to boot the system (run-time dependence)?
Obviously the last 3 patches in the series touch the DTS, so they depend
on the base patch adding the DTS files.
> We can merge support for pin control ahead, that's fine.
The actual pinctrl driver can indeed be merged separately.
> > This implements the pinctrl driver for the R9A06G032.
>
> Geert Uytterhoeven and Laurent Pinchart maintains the Renesas pin
> controllers, and this one is for some reason a totally new one in
> drivers/pinctrl/pinctrl-r9a06g032.c
>
> Is it totally different from the other "great old ones" in the SuperH-PFC
> series or is there some other reason why it was done like this?
Yes it is, cfr. drivers/pinctrl/pinctrl-rza1.c, which lives outside sh-pfc, too.
Of course I can take it through my sh-pfc tree, once the rough edges have been
removed.
Thanks!
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
next prev parent reply other threads:[~2018-06-18 8:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 11:00 [PATCH v1 0/5] Renesas R9A06G032 PINCTRL Driver Michel Pollet
2018-06-14 11:00 ` [PATCH v1 1/5] dt-bindings: Add the r9a06g032-pinctrl.h file Michel Pollet
2018-06-25 20:47 ` Rob Herring
2018-06-14 11:00 ` [PATCH v1 2/5] dt-bindings: clock: renesas,r9a06g032-pinctrl: documentation Michel Pollet
2018-06-14 12:04 ` jacopo mondi
2018-06-14 12:10 ` Michel Pollet
2018-06-14 12:17 ` Chris Brandt
2018-06-15 8:40 ` jacopo mondi
2018-06-14 11:00 ` [PATCH v1 3/5] pinctrl: renesas: Renesas R9A06G032 pinctrl driver Michel Pollet
2018-06-15 10:59 ` jacopo mondi
2018-06-14 11:00 ` [PATCH v1 4/5] ARM: dts: Renesas R9A06G032 pinctrl node Michel Pollet
2018-06-14 11:42 ` Sergei Shtylyov
2018-06-14 11:00 ` [PATCH v1 5/5] ARM: dts: Renesas RZN1D-DB Board: Add UART0 pinmux node Michel Pollet
2018-06-18 8:46 ` [PATCH v1 0/5] Renesas R9A06G032 PINCTRL Driver Linus Walleij
2018-06-18 8:57 ` Geert Uytterhoeven [this message]
2018-06-28 14:10 ` Linus Walleij
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=CAMuHMdVL-00gb7ZfgNGr8-VawFUpg+iY5mpPF6UZPfjFqM1_jg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=buserror+upstream@gmail.com \
--cc=damm+renesas@opensource.se \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michel.pollet@bp.renesas.com \
--cc=phil.edworthy@renesas.com \
--cc=robh+dt@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).