From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Chris Brandt <Chris.Brandt@renesas.com>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
"geert+renesas@glider.be" <geert+renesas@glider.be>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [RFC 2/5] pinctrl: rz-pfc: Add Renesas RZ/A1 pinctrl driver
Date: Tue, 31 Jan 2017 12:39:56 +0200 [thread overview]
Message-ID: <5091561.JdaHPde81y@avalon> (raw)
In-Reply-To: <SG2PR06MB1165C49393EAA4027B020B448A4B0@SG2PR06MB1165.apcprd06.prod.outlook.com>
Hi Chris,
On Monday 30 Jan 2017 19:19:18 Chris Brandt wrote:
> On Wednesday, January 25, 2017, Jacopo Mondi wrote:
> > + /* Port 5 */
> > + RZ_PIN_NAME(5, 0), RZ_PIN_NAME(5, 1), RZ_PIN_NAME(5, 2),
> > + RZ_PIN_NAME(5, 3), RZ_PIN_NAME(5, 4), RZ_PIN_NAME(5, 5),
> > + RZ_PIN_NAME(5, 6), RZ_PIN_NAME(5, 7), RZ_PIN_NAME(5, 8),
> > + RZ_PIN_NAME(5, 9), RZ_PIN_NAME(5, 10),
>
> The RZ/A1L (basically a subset of RZ/A1H to reduce cost) uses
> all 16 port pins on "port 5" so I'd like to include them as well.
>
> > +static const struct of_device_id rza1_pinctrl_of_match[] = {
> > + { .compatible = "renesas,rza1-pinctrl", },
> > + { }
> > +};
>
> Since this PFC driver file is specifically for RZ/A1, I think a
> better compatible string would be:
>
> .compatible = "renesas,r7s72100-renesas-pinctrl",
Do we need to repeat "renesas" in the name ? And given that the datasheet
names the hardware "ports", how about "renesas,r7s72100-ports" ? The IP core
handles both pinctrl and GPIO, so "pinctrl" is a bit restrictive.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-01-31 10:39 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 18:09 [RFC 0/5] Renesas RZ series pinctrl driver Jacopo Mondi
2017-01-25 18:09 ` [RFC 1/5] pinctrl: rz-pfc: Add Renesas RZ pinctrl core module Jacopo Mondi
2017-01-26 2:58 ` Chris Brandt
2017-01-26 9:08 ` jacopo mondi
2017-01-26 14:19 ` Chris Brandt
2017-01-26 19:43 ` Geert Uytterhoeven
2017-01-30 19:19 ` Chris Brandt
2017-01-31 9:00 ` jacopo mondi
2017-01-31 13:48 ` Chris Brandt
2017-02-01 12:47 ` Laurent Pinchart
2017-02-01 15:21 ` Laurent Pinchart
2017-02-06 18:15 ` jacopo mondi
2017-02-06 18:28 ` Tony Lindgren
2017-02-07 10:27 ` jacopo mondi
2017-01-25 18:09 ` [RFC 2/5] pinctrl: rz-pfc: Add Renesas RZ/A1 pinctrl driver Jacopo Mondi
2017-01-26 19:49 ` Geert Uytterhoeven
2017-01-30 19:19 ` Chris Brandt
2017-01-31 10:39 ` Laurent Pinchart [this message]
2017-01-31 14:11 ` Chris Brandt
2017-02-01 15:25 ` Laurent Pinchart
2017-01-25 18:09 ` [RFC 3/5] arm: dts: dt-bindings: Add Renesas RZ pinctrl header Jacopo Mondi
2017-01-26 19:52 ` Geert Uytterhoeven
2017-01-30 18:30 ` Laurent Pinchart
2017-01-31 9:12 ` jacopo mondi
2017-01-31 9:31 ` Geert Uytterhoeven
2017-01-31 14:00 ` Chris Brandt
2017-01-25 18:09 ` [RFC 4/5] arm: dts: r7s1000: Add pincontroller node Jacopo Mondi
2017-01-26 9:49 ` Sergei Shtylyov
2017-01-26 19:54 ` Geert Uytterhoeven
2017-01-31 10:24 ` jacopo mondi
2017-01-31 10:34 ` Geert Uytterhoeven
2017-01-30 18:29 ` Laurent Pinchart
2017-01-30 19:39 ` Chris Brandt
2017-01-31 10:35 ` Laurent Pinchart
2017-01-31 14:08 ` Chris Brandt
2017-01-25 18:09 ` [RFC 5/5] arm: dts: genmai: Add SCIF2 pin group Jacopo Mondi
2017-01-26 9:51 ` Sergei Shtylyov
2017-01-30 18:17 ` Laurent Pinchart
2017-01-30 18:55 ` Geert Uytterhoeven
2017-01-26 2:57 ` [RFC 0/5] Renesas RZ series pinctrl driver Chris Brandt
2017-01-26 19:56 ` Geert Uytterhoeven
2017-01-27 16:47 ` [RFC fixes 0/2] FIX: " Jacopo Mondi
2017-01-27 16:47 ` [RFC fixes 1/2] arm: dts: genmai: Configure RIIC2 pins Jacopo Mondi
2017-01-30 18:49 ` Laurent Pinchart
2017-01-27 16:47 ` [RFC fixes 2/2] pinctrl: rz-pfc: Fix RZ/A1 pin function configuration Jacopo Mondi
2017-01-27 21:09 ` [RFC fixes 0/2] FIX: Renesas RZ series pinctrl driver Chris Brandt
2017-01-30 15:47 ` jacopo mondi
2017-01-30 16:29 ` Chris Brandt
2017-01-30 13:51 ` [RFC 0/5] " Linus Walleij
2017-01-30 15:53 ` Tony Lindgren
2017-01-30 16:18 ` jacopo mondi
2017-01-30 16:08 ` Geert Uytterhoeven
2017-01-30 18:59 ` Laurent Pinchart
2017-01-30 19:49 ` Chris Brandt
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=5091561.JdaHPde81y@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Chris.Brandt@renesas.com \
--cc=geert+renesas@glider.be \
--cc=jacopo+renesas@jmondi.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@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).