From: antoine.tenart@free-electrons.com (Antoine Ténart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/7] pinctrl: berlin: add the BG2Q pinctrl driver
Date: Mon, 28 Apr 2014 19:03:29 +0200 [thread overview]
Message-ID: <20140428170329.GA4211@kwain> (raw)
In-Reply-To: <535B7C8A.6000003@gmail.com>
Sebastian,
On Sat, Apr 26, 2014 at 11:29:46AM +0200, Sebastian Hesselbarth wrote:
> On 04/23/2014 05:51 PM, Antoine T?nart wrote:
[?]
> > + BERLIN_PINCTRL_GROUP("G2", 0x18, 0x3, 0x06,
> > + BERLIN_PINCTRL_FUNCTION(0x0, "gpio"),
> > + BERLIN_PINCTRL_FUNCTION(0x2, "arc"),
> > + BERLIN_PINCTRL_FUNCTION(0x3, "lvds_vsync")),
>
> Shouldn't the above be:
>
> BERLIN_PINCTRL_FUNCTION(0x3, "lvds"))), /* vsync */
Sure.
[?]
> > + BERLIN_PINCTRL_GROUP("G6", 0x18, 0x3, 0x12,
> > + BERLIN_PINCTRL_FUNCTION(0x0, "soc"),
>
> Uhm, any idea what "soc" is for? If not, just leave it.
That should be 'jtag', I'll update.
[?]
> > + BERLIN_PINCTRL_GROUP("G13", 0x1c, 0x3, 0x09,
> > + BERLIN_PINCTRL_FUNCTION(0x0, "gpio"),
> > + BERLIN_PINCTRL_FUNCTION(0x1, "sts1"),
>
> Any idea what "sts" means, maybe "ts" is for Transport Stream?
> No need to change it, I am just curious.
STS stands for Serial Transport Stream. There may be a more common name
for this, any idea ?
> > + BERLIN_PINCTRL_GROUP("GAV11", 0x28, 0x3, 0x0c,
> > + BERLIN_PINCTRL_FUNCTION(0x0, "avio"),
> > + BERLIN_PINCTRL_FUNCTION(0x1, "dv0"),
> > + BERLIN_PINCTRL_FUNCTION(0x2, "fp"),
> > + BERLIN_PINCTRL_FUNCTION(0x3, "i2s0"),
> > + BERLIN_PINCTRL_FUNCTION(0x4, "avio_pwm"),
>
> Is it the same "pwm" as for GAV8? If so, remove the "avio_"
> prefix?
Not the same, but 'pwm' makes sense here.
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:03 UTC|newest]
Thread overview: 23+ 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 ` [PATCH v2 1/7] pinctrl: berlin: add the core pinctrl driver for Marvell Berlin SoCs Antoine Ténart
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-26 9:29 ` Sebastian Hesselbarth
2014-04-28 17:03 ` Antoine Ténart [this message]
2014-04-23 15:51 ` [PATCH v2 3/7] pinctrl: berlin: add the BG2 " Antoine Ténart
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-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 ` [PATCH v2 6/7] Documentation: add the Marvell Berlin pinctrl documentation Antoine Ténart
2014-04-26 9:44 ` Sebastian Hesselbarth
2014-04-28 17:05 ` Antoine Ténart
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-26 9:51 ` Sebastian Hesselbarth
2014-04-24 12:52 ` [PATCH v2 0/7] ARM: berlin: add pinctrl support Linus Walleij
2014-04-24 13:08 ` Russell King - ARM Linux
2014-04-24 13:23 ` Sebastian Hesselbarth
2014-04-24 13:26 ` Thomas Petazzoni
2014-04-25 9:13 ` Linus Walleij
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=20140428170329.GA4211@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).