linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 09/10] ARM: mvebu: add Device Tree files for Armada 39x SoC and board
Date: Fri, 20 Feb 2015 15:45:47 +0100	[thread overview]
Message-ID: <20150220144547.GB13797@lunn.ch> (raw)
In-Reply-To: <20150220151455.461b97bb@free-electrons.com>

> > > +			pinctrl at 18000 {
> > > +				uart0_pins: uart0-pins {
> > > +					marvell,pins = "mpp0", "mpp1";
> > > +					marvell,function = "ua0";
> > > +				};
> > > +
> > > +				uart1_pins: uart1-pins {
> > > +					marvell,pins = "mpp19", "mpp20";
> > > +					marvell,function = "ua1";
> > > +				};
> > 
> > Does it make sense to put there in the .dtsi file? I know there are
> > other choices, but generally board manufacturers tend to follow the
> > reference design.
> 
> I am not really convinced here: there are really many possible pin
> muxing possibilities. Various pins for UART0 and UART1, whether you use
> CTS/RTS or not, etc. I believe this is really the sort of pin mux
> configuration that is best left at the board level.

Hi Thomas

Lets look at this from the perspective of lies, damn lies, and
statistics:

Kirkwood has a default pinmux configuration in kirkwood.dtsi. Two of
the sixty six .dts files overwrite the defaults.

Dove has a default pinmux of uart1, but none for uart0.  None of the
.dts files define a pinmux for uart0 and none overwrite the defaults
for uart1.

Armanda XP has a default pinmux for uart2 and uart2 in armada-xp.dtsi,
but none for uart0 or uart1. None of the .dts files define a pinmux
for uart0 or uart1, and none overwrite the defaults for uart2 or
uart3.

Armada 370 has default pinmux for uart0 and uart1. None of the .dts
files overwrite the defaults.

I'm too lazy to look at 375, 380, and 385.

We have over 80 dts files here with defaults from a .dtsi file, and
only two need anything other than defaults.

	 Andrew

  reply	other threads:[~2015-02-20 14:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 15:57 [PATCH 00/10] ARM: mvebu: add basic support for Armada 39x Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 01/10] devicetree: bindings: add DT binding for the Marvell Armada 39x SoC family Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 02/10] devicetree: bindings: update DT bindings for Marvell EBU clock support Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 03/10] devicetree: bindings: add Device Tree bindings for Armada 39x pin-muxing controller Thomas Petazzoni
2015-02-06 17:05   ` Andrew Lunn
2015-02-20 11:11     ` Thomas Petazzoni
2015-02-20 14:18       ` Andrew Lunn
2015-02-06 15:57 ` [PATCH 04/10] devicetree: bindings: add new SMP enable method for Marvell Armada 39x Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 05/10] clk: mvebu: extend common code to allow an optional refclk Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 06/10] clk: mvebu: add Marvell Armada 39x driver Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 07/10] pinctrl: mvebu: add pinctrl driver for Marvell Armada 39x Thomas Petazzoni
2015-03-04 12:54   ` Linus Walleij
2015-03-04 13:05     ` Thomas Petazzoni
2015-02-06 15:57 ` [PATCH 08/10] ARM: mvebu: add core support for " Thomas Petazzoni
2015-02-06 19:57   ` Stephen Boyd
2015-02-20 13:05     ` Thomas Petazzoni
2015-02-06 20:31   ` Maxime Ripard
2015-02-06 15:57 ` [PATCH 09/10] ARM: mvebu: add Device Tree files for Armada 39x SoC and board Thomas Petazzoni
2015-02-06 17:21   ` Andrew Lunn
2015-02-20 14:14     ` Thomas Petazzoni
2015-02-20 14:45       ` Andrew Lunn [this message]
2015-02-20 15:46         ` Thomas Petazzoni
2015-02-06 20:39   ` Maxime Ripard
2015-02-06 15:57 ` [PATCH 10/10] Documentation: arm: update supported Marvell EBU processors Thomas Petazzoni

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=20150220144547.GB13797@lunn.ch \
    --to=andrew@lunn.ch \
    --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).