All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: driver changes for v3.12
Date: Thu, 15 Aug 2013 23:15:00 -0700	[thread overview]
Message-ID: <20130816061500.GE7035@quad.lixom.net> (raw)
In-Reply-To: <20130814185945.GC13964@titan.lakedaemon.net>

Hi,

On Wed, Aug 14, 2013 at 02:59:45PM -0400, Jason Cooper wrote:
> Arnd, Olof,
> 
> This rather long branch adds the MBus devicetree binding and converts
> everything over to using it.  It's been in -next over a week and should
> be pretty stable.
> 
> Note:  There is a merge conflict with arm-soc/for-next, I've attached the
> resolution after the summary.

Pulled into next/soc.


> diff --cc arch/arm/boot/dts/kirkwood.dtsi
> index 70f414d,1d6921d..6489b98
> --- a/arch/arm/boot/dts/kirkwood.dtsi
> +++ b/arch/arm/boot/dts/kirkwood.dtsi
> @@@ -47,11 -30,30 +40,35 @@@
>   		#address-cells = <1>;
>   		#size-cells = <1>;
>   
> + 		timer: timer at 20300 {
> + 			compatible = "marvell,orion-timer";
> + 			reg = <0x20300 0x20>;
> + 			interrupt-parent = <&bridge_intc>;
> + 			interrupts = <1>, <2>;
> + 			clocks = <&core_clk 0>;
> + 		};
> + 
> + 		intc: main-interrupt-ctrl at 20200 {
> + 			compatible = "marvell,orion-intc";
> + 			interrupt-controller;
> + 			#interrupt-cells = <1>;
> + 			reg = <0x20200 0x10>, <0x20210 0x10>;
> + 		};
> + 
> + 		bridge_intc: bridge-interrupt-ctrl at 20110 {
> + 			compatible = "marvell,orion-bridge-intc";
> + 			interrupt-controller;
> + 			#interrupt-cells = <1>;
> + 			reg = <0x20110 0x8>;
> + 			interrupts = <1>;
> + 			marvell,#interrupts = <6>;
> + 		};
> + 
>  +		mbusc: mbus-controller at 20000 {
>  +			compatible = "marvell,mbus-controller";
>  +			reg = <0x20000 0x80>, <0x1500 0x20>;
>  +		};
>  +
>   		core_clk: core-clocks at 10030 {
>   			compatible = "marvell,kirkwood-core-clock";
>   			reg = <0x10030 0x4>;

This file is a real mess. :( Nothing is sorted properly under the ocp/ bus.
It's common to sort by memory address. Or I'd even take alphabetically if
there was a good reason to do so. Just some order of some kind.

That would have avoided the conflicts this time around, since it seems that
devices are added in completely random order here, but adjacent. If they'd been
spaced out, git would have handled it nicely on its own.


-Olof

  reply	other threads:[~2013-08-16  6:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 18:59 [GIT PULL] ARM: mvebu: driver changes for v3.12 Jason Cooper
2013-08-16  6:15 ` Olof Johansson [this message]
2013-12-12 15:25   ` [PATCH 0/4] ARM: mvebu: sort DT nodes by reg address Jason Cooper
2013-12-12 15:25     ` [PATCH 1/4] ARM: kirkwood: sort dt nodes by address Jason Cooper
2013-12-12 15:25     ` [PATCH 2/4] ARM: dove: sort DT " Jason Cooper
2013-12-12 15:25     ` [PATCH 3/4] ARM: orion5x: " Jason Cooper
2013-12-12 15:25     ` [PATCH 4/4] ARM: mvebu: " Jason Cooper
2013-12-14 22:27     ` [PATCH 0/4] ARM: mvebu: sort DT nodes by reg address Jason Cooper
2013-12-22 17:28     ` [PATCH] ARM: kirkwood: 6282: sort DT nodes by address Jason Cooper

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=20130816061500.GE7035@quad.lixom.net \
    --to=olof@lixom.net \
    --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.