From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] ARM: berlin: add pinctrl support
Date: Thu, 24 Apr 2014 15:26:20 +0200 [thread overview]
Message-ID: <20140424152620.39eae472@skate> (raw)
In-Reply-To: <CACRpkdbT94HqVroM_0gSJJ8Q2+YaKXLwjFGMn+4SCa_PYiF19Q@mail.gmail.com>
Dear Linus Walleij,
On Thu, 24 Apr 2014 14:52:20 +0200, Linus Walleij wrote:
> > Tested on the Berlin BG2Q.
>
> So now I need some advice from the mvebu pinctrl maintainers
> (Thomas, Sebastian etc):
>
> - Is this a totally different pin controller so that drivers/pinctrl/mvebu
> can not be used?
It is. The CPU families are completely different, made from completely
separate divisions of Marvell. Just think that they come from different
companies :-)
On the mvebu side, each pin can be independently configured to a
different function: there is a 4-bits field for each pin to configure
the function.
On the berlin side, pins are only configured in groups. You can't
independently set the functions of each pin: you can set a function to
a pre-defined set of pins.
> - Really?
Yes.
> - OK can you help me review this thing?
Sure. I believe Sebastian already had a very detailed look so he can
provide his review.
> - Should the base folder really be named "berlin" or is this going to
> be part of a bigger family of pin controllers so a more neutral name
> should be sought?
berlin is the name of the mach-<foo> directory in arch/arm, and that's
really the code name for this SoC family.
> - Why do hardware engineers seek to reinvent wheels like pin
> controllers, GPIO and DMA engines all the time :-/
I guess Russell already gave you a good answer to this question :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Antoine Ténart" <antoine.tenart@free-electrons.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Alexandre Belloni" <alexandre.belloni@free-electrons.com>,
"zhiming Xu" <zmxu@marvell.com>,
"Jisheng Zhang" <jszhang@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/7] ARM: berlin: add pinctrl support
Date: Thu, 24 Apr 2014 15:26:20 +0200 [thread overview]
Message-ID: <20140424152620.39eae472@skate> (raw)
In-Reply-To: <CACRpkdbT94HqVroM_0gSJJ8Q2+YaKXLwjFGMn+4SCa_PYiF19Q@mail.gmail.com>
Dear Linus Walleij,
On Thu, 24 Apr 2014 14:52:20 +0200, Linus Walleij wrote:
> > Tested on the Berlin BG2Q.
>
> So now I need some advice from the mvebu pinctrl maintainers
> (Thomas, Sebastian etc):
>
> - Is this a totally different pin controller so that drivers/pinctrl/mvebu
> can not be used?
It is. The CPU families are completely different, made from completely
separate divisions of Marvell. Just think that they come from different
companies :-)
On the mvebu side, each pin can be independently configured to a
different function: there is a 4-bits field for each pin to configure
the function.
On the berlin side, pins are only configured in groups. You can't
independently set the functions of each pin: you can set a function to
a pre-defined set of pins.
> - Really?
Yes.
> - OK can you help me review this thing?
Sure. I believe Sebastian already had a very detailed look so he can
provide his review.
> - Should the base folder really be named "berlin" or is this going to
> be part of a bigger family of pin controllers so a more neutral name
> should be sought?
berlin is the name of the mach-<foo> directory in arch/arm, and that's
really the code name for this SoC family.
> - Why do hardware engineers seek to reinvent wheels like pin
> controllers, GPIO and DMA engines all the time :-/
I guess Russell already gave you a good answer to this question :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-24 13:26 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
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 [this message]
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=20140424152620.39eae472@skate \
--to=thomas.petazzoni@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.