public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Emilio Lopez <emilio@elopez.com.ar>,
	linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
	sunny@allwinnertech.com, shuge@allwinnertech.com,
	kevin@allwinnertech.com
Subject: Re: [PATCH 4/6] ARM: sunxi: dt: Add Allwinner A10s DTSI
Date: Mon, 10 Jun 2013 12:34:35 +0200	[thread overview]
Message-ID: <20130610103435.GJ2748@lukather> (raw)
In-Reply-To: <3346364.JR9UrJYqP8@wuerfel>

Hi Arnd,

On Sun, Jun 09, 2013 at 11:36:24PM +0200, Arnd Bergmann wrote:
> On Sunday 09 June 2013 18:36:05 Maxime Ripard wrote:
> > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> > ---
> >  arch/arm/boot/dts/sun5i-a10s.dtsi | 286 ++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 286 insertions(+)
> >  create mode 100644 arch/arm/boot/dts/sun5i-a10s.dtsi
> 
> Would it make sense to split out the parts that are common with A13 into
> a separate sun5i.dtsi file?

I don't have the documentation at the moment, so I'm not exactly sure at
which extent it's similar to the A13. Yet for the moment, the two dtsi
are very different (different clock definitions, different muxings,
etc.), so , I'm not quite sure about wether it would make stuff smaller.

Of course, if we find they actually share a lot, we can definitely make
a common sun5i DTSI later.

But if you prefer to have it right now, I can always send a v2 :)

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-06-10 10:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 16:36 [PATCH 0/6] Add support for Allwinner A10s SoCs Maxime Ripard
2013-06-09 16:36 ` [PATCH 1/6] ARM: sunxi: Add Allwinner A10s machine compatible Maxime Ripard
2013-06-09 16:36 ` [PATCH 2/6] pinctrl: sunxi: Move the pins definitions to a separate header Maxime Ripard
2013-06-16 11:03   ` Linus Walleij
2013-06-17  8:41     ` Maxime Ripard
2013-06-17 16:11       ` Linus Walleij
2013-06-09 16:36 ` [PATCH 3/6] pinctrl: sunxi: Add Allwinner A10s pins Maxime Ripard
2013-06-16 11:04   ` Linus Walleij
2013-06-09 16:36 ` [PATCH 4/6] ARM: sunxi: dt: Add Allwinner A10s DTSI Maxime Ripard
2013-06-09 21:36   ` Arnd Bergmann
2013-06-10 10:34     ` Maxime Ripard [this message]
2013-06-10 14:58       ` Arnd Bergmann
2013-06-09 16:36 ` [PATCH 5/6] ARM: sunxi: Add Olimex A10s-Olinuxino-micro device tree Maxime Ripard
2013-06-14 18:09   ` [linux-sunxi] " Emilio López
2013-06-17  8:38     ` Maxime Ripard
2013-06-09 16:36 ` [PATCH 6/6] ARM: multi_v7: Enable Allwinner EMAC in multi_v7_defconfig Maxime Ripard
2013-06-15 13:14 ` [PATCH 0/6] Add support for Allwinner A10s SoCs Maxime Ripard

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=20130610103435.GJ2748@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=arnd@arndb.de \
    --cc=emilio@elopez.com.ar \
    --cc=kevin@allwinnertech.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=shuge@allwinnertech.com \
    --cc=sunny@allwinnertech.com \
    /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