From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart
<laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
Cc: "Laurent Pinchart"
<laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>,
"Sascha Hauer" <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Niklas Söderlund" <niso-UNjuZkX4dYU@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Magnus Damm"
<magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Linus Walleij"
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [RFC/PATCH] pinctrl: sh-pfc: Accept standard function, pins and groups properties
Date: Tue, 09 Jun 2015 14:35:07 +0000 [thread overview]
Message-ID: <CAMuHMdWp4iBGtR2EiYMa03hwJrSOpq9dB==yDgt+OwjCebuFMg@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdbepTKxMFVpTo7ZmjYE1beF5XOMOQarszaDGojerNQqMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Laurent,
On Fri, Mar 6, 2015 at 11:39 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Wed, Feb 4, 2015 at 10:53 AM, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> wrote:
>> On Wednesday 04 February 2015 09:40:48 Linus Walleij wrote:
>>> On Tue, Jan 27, 2015 at 9:31 PM, Laurent Pinchart wrote:
>>> > The "function", "pins" and "groups" pinmux and pinctrl properties have
>>> > been standardized. Support them in addition to the custom "renesas,*"
>>> > properties. New-style and old-style properties can't be mixed in DT.
>>> >
>>> > Signed-off-by: Laurent Pinchart
>>> > <laurent.pinchart+renesas@ideasonboard.com>
>>>
>>> (...)
>>>
>>> >> Would be nice if the PFC driver could be augmented to also accept the
>>> >> now standard bindings "groups" and "function" simply :) we're adding
>>> >> parse functions for those to the core.
>>> >
>>> > Something like this ?
>>>
>>> Yes :)
>>>
>>> > Please note two differences between the Renesas PFC bindings and the
>>> > standard bindings:
>>> >
>>> > - The standard bindings state that a pinctrl node must contain either a
>>> > "pins" property or a "groups" property, while the Renesas bindings
>>> > allows for both to coexist in the same node.
>>>
>>> Sascha also says this makes sense for him so I guess I'm getting a bit
>>> soft on the issue.
>>>
>>> > - The standard bindings don't allow a pinmux node to contain a "pins"
>>> > property, while the Renesas bindings do.
>>>
>>> Does that mean "pins" affect the muxing or that "pins" is about some per-pin
>>> config shoveled into the same node?
>>>
>>> The former is not OK, the latter is.
>>
>> It means "pins" affect the muxing. The sh-pfc driver supports both muxing
>> groups and muxing individual pins.
>
> OK.
>
>>> > mmcif_pins: mmcif {
>>> >
>>> > mux {
>>> > - renesas,groups = "mmc0_data8_0",
>>> > "mmc0_ctrl_0";
>>> > - renesas,function = "mmc0";
>>> > + groups = "mmc0_data8_0", "mmc0_ctrl_0";
>>> > + function = "mmc0";
>>> > };
>>>
>>> So that looks just very nice.
>>>
>>> > cfg {
>>> > - renesas,groups = "mmc0_data8_0";
>>> > - renesas,pins = "PORT279";
>>> > + groups = "mmc0_data8_0";
>>> > + pins = "PORT279";
>>> > bias-pull-up;
>>>
>>> And here I can't see the use of "groups" in this node since it
>>> doesn't match a function. It's a bit ambiguous what "groups"
>>> mean when you run into it like this.
>>
>> It means that the bias-pull-up configuration is applied to all pins of the
>> "mmc0_data8_0" group, as well as to pin 279.
>
> OK.
>
> This looks good to me, is the patch applicable as it is, or will you rebase
> it and send out a non-RFC version?
This seems to have fallen through the (ELC?) cracks...
What's the status?
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:[~2015-06-09 14:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 12:20 [PATCH v2 0/4] Add emev2 pinmux support Niklas Söderlund
2015-01-18 12:20 ` [PATCH v2 2/4] sh-pfc: " Niklas Söderlund
2015-01-22 22:37 ` Laurent Pinchart
2015-01-25 13:48 ` Niklas Söderlund
[not found] ` <20150125134823.GA26657-ofJ5d6taAgLV0csKaCxRng@public.gmane.org>
2015-01-25 15:55 ` Laurent Pinchart
2015-01-25 13:49 ` [PATCH v3] " Niklas Söderlund
2015-01-25 16:05 ` Laurent Pinchart
2015-01-27 7:52 ` Linus Walleij
2015-01-18 12:20 ` [PATCH v2 3/4] ARM: shmobile: emev2: Add PFC information to emev2.dtsi Niklas Söderlund
2015-01-22 21:50 ` Laurent Pinchart
2015-01-27 7:53 ` Linus Walleij
[not found] ` <1421583604-27256-1-git-send-email-niso-UNjuZkX4dYU@public.gmane.org>
2015-01-18 12:20 ` [PATCH v2 1/4] sh-pfc: add macro to define pinmux without function Niklas Söderlund
[not found] ` <1421583604-27256-2-git-send-email-niso-UNjuZkX4dYU@public.gmane.org>
2015-01-22 21:50 ` Laurent Pinchart
2015-01-27 7:48 ` Linus Walleij
2015-01-18 12:20 ` [PATCH v2 4/4] ARM: shmobile: emev2-kzm9d: Add PFC information for uart1 Niklas Söderlund
2015-01-27 7:55 ` Linus Walleij
2015-01-27 20:31 ` [RFC/PATCH] pinctrl: sh-pfc: Accept standard function, pins and groups properties Laurent Pinchart
2015-01-27 20:40 ` Geert Uytterhoeven
2015-02-04 8:40 ` Linus Walleij
[not found] ` <CACRpkda6H7hbgXhmSbgtwOC_8PbHnES5syp-YEp1+V6s5Ym6Cw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-04 9:53 ` Laurent Pinchart
2015-03-01 12:19 ` Laurent Pinchart
2015-03-06 10:39 ` Linus Walleij
[not found] ` <CACRpkdbepTKxMFVpTo7ZmjYE1beF5XOMOQarszaDGojerNQqMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-09 14:35 ` Geert Uytterhoeven [this message]
[not found] ` <CAMuHMdWp4iBGtR2EiYMa03hwJrSOpq9dB==yDgt+OwjCebuFMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-10 8:46 ` Linus Walleij
2015-01-27 20:35 ` [PATCH v2 4/4] ARM: shmobile: emev2-kzm9d: Add PFC information for uart1 Laurent Pinchart
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='CAMuHMdWp4iBGtR2EiYMa03hwJrSOpq9dB==yDgt+OwjCebuFMg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=laurent.pinchart+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=niso-UNjuZkX4dYU@public.gmane.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).