linux-kernel - Re: [PATCH v4 0/7] ARM: mvebu: switch to DT probed irqchip and clocksource

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130725181903.GP23879@titan.lakedaemon.net>
Date:	Thu, 25 Jul 2013 14:19:03 -0400
From:	Jason Cooper <jason@...edaemon.net>
To:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Cc:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Andrew Lunn <andrew@...n.ch>,
	Russell King <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org,
	Gregory CLEMENT <gregory.clement@...e-electrons.com>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v4 0/7] ARM: mvebu: switch to DT probed irqchip and
 clocksource

On Tue, Jul 02, 2013 at 01:03:36PM +0200, Sebastian Hesselbarth wrote:
> This patch set converts Marvell Dove and Kirkwood DT enabled boards
> to probe irqchip and clocksource by DT. The corresponding irqchip and
> clocksource drivers have been taken by Thomas Gleixner and Daniel Lezcano
> respectively. This patch set is based on next-20130701 plus tip/core and
> timers/clockevents. Also, mv643xx_eth DT patches sent earlier are applied.
> 
> Unfortunately, the same compatible string is used by irqchip driver and
> irq DT stub in plat-orion/irq.c while reg layout is different. This patch
> set should be applied as a whole only, as device tree conversion breaks
> kernel boot until the corresponding second patch is applied. As this set
> is Marvell SoC related only, I suggest to take it all through Jason
> Cooper's branch.
> 
> Patch set version has been bumped to v4, but this only contains the
> remaining Marvell related patches. irqchip and clocksource drivers from
> v3 have already been taken by the respective maintainers.
> 
> The first three patches convert Dove, Kirkwood, and Orion5x DT files to
> the new reg layout. Patch 4 and 5 add the new clocksource and irqchip
> nodes. Patch 6 also removes an obsolete clock gate workaround from
> Kirkwood DT board setup. Patch 7 then updates the irq driver DT stub in
> plat-orion/irq to reflect the changed reg layout. The irq driver DT stub
> is still used on Orion5x until proper DT clk provider is available.
> 
> The patch set has been tested on Dove, and compile-tested on Kirkwood
> and Orion5x defconfig.
> 
> Sebastian Hesselbarth (7):
>   ARM: dove: move device tree nodes to DT irqchip and clocksource
>   ARM: kirkwood: move device tree nodes to DT irqchip and clocksource
>   ARM: orion5x: update intc device tree node to new reg layout
>   ARM: dove: convert to DT irqchip and clocksource
>   ARM: kirkwood: convert to DT irqchip and clocksource
>   ARM: kirkwood: remove obsolete SDIO clock gate workaround
>   ARM: plat-orion: add reg offset to DT irq driver stub
> 
>  arch/arm/boot/dts/dove.dtsi       |   21 +++++++++++++++++++--
>  arch/arm/boot/dts/kirkwood.dtsi   |   35 +++++++++++++++++++++++++++--------
>  arch/arm/boot/dts/orion5x.dtsi    |    5 +++--
>  arch/arm/mach-dove/Kconfig        |    2 ++
>  arch/arm/mach-dove/Makefile       |    4 ++--
>  arch/arm/mach-dove/board-dt.c     |   23 ++++++++++++++++-------
>  arch/arm/mach-kirkwood/Kconfig    |   22 ++++++++++++++++++++++
>  arch/arm/mach-kirkwood/Makefile   |    4 ++--
>  arch/arm/mach-kirkwood/board-dt.c |   28 +++++++++++++++++-----------
>  arch/arm/plat-orion/irq.c         |    2 +-
>  10 files changed, 111 insertions(+), 35 deletions(-)

Whole series (with v5 of #5) applied to mvebu/boards

thx,

Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/