From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [Query] should pinmux setting be put into board specific dts or SoC specific dtsi?
Date: Wed, 21 Jan 2015 20:56:54 +0800 [thread overview]
Message-ID: <20150121205654.7055401d@xhacker> (raw)
In-Reply-To: <54BF81A3.4060500@gmail.com>
Dear Sebastian,
On Wed, 21 Jan 2015 02:38:27 -0800
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> On 01/21/2015 08:30 AM, Jisheng Zhang wrote:
> > IIUC, the pinmux setting is board specific. So my question is where to
> > put the pinmux settings? Board specific dts or SoC specific dtsi? Could
> > anyone kindly help me?
>
> Jisheng,
>
> it depends on the pinmux setting whether it should go in to SoC dtsi or
> board dts. For example, the pinmux setting for internal devices like
> UART - where there is only one or two possible settings - should go
> into SoC dtsi. Also, if there is only one possible setting or one
> default/common setting, the SoC dtsi node should already have the
> corresponding pinctrl properties. If a specific board uses another
> setting, it can always overwrite the default property with the
> one used at board level.
>
> A good example for board specific pinmux settings clearly is GPIO,
> e.g. you have a regulator for USB power that is controlled by GPIO
> then you'll have the regulator node on board level and also the
> corresponding pinmux settings for that very GPIO pin.
Thanks very much for the detailed explanation. The regulator is the case
I care ;)
>
> If you give a specific example of what pinmux setting bothers you,
> we can try to find a good place for it.
>
> Sebastian
prev parent reply other threads:[~2015-01-21 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 7:30 [Query] should pinmux setting be put into board specific dts or SoC specific dtsi? Jisheng Zhang
2015-01-21 10:38 ` Sebastian Hesselbarth
2015-01-21 12:56 ` Jisheng Zhang [this message]
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=20150121205654.7055401d@xhacker \
--to=jszhang@marvell.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).