From: antoine.tenart@free-electrons.com (Antoine Ténart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/7] Documentation: add the Marvell Berlin pinctrl documentation
Date: Mon, 28 Apr 2014 19:05:24 +0200 [thread overview]
Message-ID: <20140428170524.GB4211@kwain> (raw)
In-Reply-To: <535B7FFC.3000109@gmail.com>
Sebastian,
On Sat, Apr 26, 2014 at 11:44:28AM +0200, Sebastian Hesselbarth wrote:
> On 04/23/2014 05:51 PM, Antoine T?nart wrote:
[?]
> > +A pin-controller node should contain subnodes representing the pin group
> > +configurations, one per group. Each subnode has the group name and the muxing
>
> ",one per group" isn't correct, is it? You can have one subnode with
> more than one group, like in your example below.
Sure, I forgot to update this one after adding the ability to configure
multiple groups in the same subnode.
Antoine
--
Antoine T?nart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-28 17:05 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 15:51 [PATCH v2 0/7] ARM: berlin: add pinctrl support Antoine Ténart
2014-04-23 15:51 ` Antoine Ténart
2014-04-23 15:51 ` [PATCH v2 1/7] pinctrl: berlin: add the core pinctrl driver for Marvell Berlin SoCs Antoine Ténart
2014-04-23 15:51 ` Antoine Ténart
2014-04-26 9:17 ` Sebastian Hesselbarth
2014-04-26 9:17 ` Sebastian Hesselbarth
2014-04-28 17:06 ` Antoine Ténart
2014-04-23 15:51 ` [PATCH v2 2/7] pinctrl: berlin: add the BG2Q pinctrl driver Antoine Ténart
2014-04-23 15:51 ` Antoine Ténart
2014-04-26 9:29 ` Sebastian Hesselbarth
2014-04-26 9:29 ` Sebastian Hesselbarth
2014-04-28 17:03 ` Antoine Ténart
2014-04-23 15:51 ` [PATCH v2 3/7] pinctrl: berlin: add the BG2 " Antoine Ténart
2014-04-23 15:51 ` Antoine Ténart
2014-04-26 9:33 ` Sebastian Hesselbarth
2014-04-26 9:33 ` Sebastian Hesselbarth
2014-04-23 15:51 ` [PATCH v2 4/7] pinctrl: berlin: add the BG2CD " Antoine Ténart
2014-04-23 15:51 ` Antoine Ténart
2014-04-26 9:40 ` Sebastian Hesselbarth
2014-04-26 9:40 ` Sebastian Hesselbarth
2014-04-23 15:51 ` [PATCH v2 5/7] ARM: berlin: add the pinctrl dependency for the Marvell Berlin SoCs Antoine Ténart
2014-04-23 15:51 ` Antoine Ténart
2014-04-23 15:51 ` [PATCH v2 6/7] Documentation: add the Marvell Berlin pinctrl documentation Antoine Ténart
2014-04-23 15:51 ` Antoine Ténart
2014-04-26 9:44 ` Sebastian Hesselbarth
2014-04-26 9:44 ` Sebastian Hesselbarth
2014-04-28 17:05 ` Antoine Ténart [this message]
2014-04-23 15:51 ` [PATCH v2 7/7] ARM: dts: berlin: add the pinctrl node and muxing setup for uarts Antoine Ténart
2014-04-23 15:51 ` Antoine Ténart
2014-04-23 15:51 ` Antoine Ténart
2014-04-26 9:51 ` Sebastian Hesselbarth
2014-04-26 9:51 ` Sebastian Hesselbarth
2014-04-26 9:51 ` Sebastian Hesselbarth
2014-04-24 12:52 ` [PATCH v2 0/7] ARM: berlin: add pinctrl support Linus Walleij
2014-04-24 12:52 ` Linus Walleij
2014-04-24 13:08 ` Russell King - ARM Linux
2014-04-24 13:08 ` Russell King - ARM Linux
2014-04-24 13:23 ` Sebastian Hesselbarth
2014-04-24 13:23 ` Sebastian Hesselbarth
2014-04-24 13:26 ` Thomas Petazzoni
2014-04-24 13:26 ` Thomas Petazzoni
2014-04-25 9:13 ` Linus Walleij
2014-04-25 9:13 ` Linus Walleij
2014-04-26 9:53 ` Sebastian Hesselbarth
2014-04-26 9:53 ` Sebastian Hesselbarth
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=20140428170524.GB4211@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.