From: antoine.tenart@free-electrons.com (Antoine Ténart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 6/7] Documentation: add the Marvell Berlin pinctrl documentation
Date: Fri, 16 May 2014 18:47:51 +0200 [thread overview]
Message-ID: <20140516164751.GA8406@kwain> (raw)
In-Reply-To: <CACRpkdaL9tzfUrY=wLjSR3dcD7JC1mUX3kdG+Wh5gDyxGY2Yqw@mail.gmail.com>
Linus,
On Fri, May 16, 2014 at 03:35:48PM +0200, Linus Walleij wrote:
> On Mon, May 5, 2014 at 7:27 AM, Antoine T?nart
> <antoine.tenart@free-electrons.com> wrote:
>
> > Add the documentation related to the Berlin pin-controller driver and
> > explain how to configure this group based controller.
> >
> > Signed-off-by: Antoine T?nart <antoine.tenart@free-electrons.com>
> > Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> (...)
>
> When I see this:
>
> > +Required subnode-properties:
> > +- marvell,groups: a list of strings describing the group names.
> > +- marvell,function: a string describing the function used to mux the groups.
> > +
> > +Example:
> > +
> > +sm_pinctrl: pin-controller at 0 {
> > + compatible = "marvell,berlin2q-sysmgr-pinctrl";
> > + reg = <0xfc0000 0x44>;
> > +
> > + uart0_pmux: uart0-pmux {
> > + marvell,groups = "GSM12", "GSM13";
> > + marvell,function = "uart0";
> > + };
> > +}
>
> I feel like ... can't we just standardize that and make it a common
> pinctrl binding, and name the properties "groups" and "function"
> for a family of pin controllers just mapping N groups to 1 function?
>
> I will merge the patches as are, but maybe we can make it generic
> on top of this before the merge window?
Do you mean just changing:
s/marvell,groups/groups/
s/marvell,function/function/
and updating the documentation ?
If so, I can definitely do that.
Antoine
--
Antoine T?nart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-16 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 5:27 [PATCH v3 0/7] ARM: berlin: add pinctrl support Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 1/7] pinctrl: berlin: add the core pinctrl driver for Marvell Berlin SoCs Antoine Ténart
2014-05-17 10:08 ` Sebastian Hesselbarth
2014-05-22 21:59 ` Linus Walleij
2014-05-22 23:02 ` Sebastian Hesselbarth
2014-05-05 5:27 ` [PATCH v3 2/7] pinctrl: berlin: add the BG2Q pinctrl driver Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 3/7] pinctrl: berlin: add the BG2 " Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 4/7] pinctrl: berlin: add the BG2CD " Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 5/7] ARM: berlin: add the pinctrl dependency for the Marvell Berlin SoCs Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 6/7] Documentation: add the Marvell Berlin pinctrl documentation Antoine Ténart
2014-05-16 13:35 ` Linus Walleij
2014-05-16 16:47 ` Antoine Ténart [this message]
2014-05-22 21:56 ` Linus Walleij
2014-05-05 5:27 ` [PATCH v3 7/7] ARM: dts: berlin: add the pinctrl node and muxing setup for uarts Antoine Ténart
2014-05-16 12:43 ` [PATCH v3 0/7] ARM: berlin: add pinctrl support Linus Walleij
2014-05-18 21:10 ` Sebastian Hesselbarth
2014-05-22 22:03 ` 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=20140516164751.GA8406@kwain \
--to=antoine.tenart@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).