linux-kernel - Re: [PATCH] drivers: memory: Introduce Marvell EBU Device Bus driver

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130423195556.GA3335@localhost>
Date:	Tue, 23 Apr 2013 16:55:58 -0300
From:	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Ezequiel Garcia <elezegarcia@...il.com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Olof Johansson <olof@...om.net>,
	Jason Cooper <jason@...edaemon.net>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Arnd Bergmann <arnd@...db.de>,
	Gregory Clement <gregory.clement@...e-electrons.com>,
	Lior Amsalem <alior@...vell.com>,
	Maen Suleiman <maen@...vell.com>, Andrew Lunn <andrew@...n.ch>
Subject: Re: [PATCH] drivers: memory: Introduce Marvell EBU Device Bus driver

On Tue, Apr 23, 2013 at 12:48:22PM -0700, Greg KH wrote:
> On Tue, Apr 23, 2013 at 04:21:26PM -0300, Ezequiel Garcia wrote:
> > From: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
> > 
> > Marvell EBU SoCs such as Armada 370/XP, Orion5x (88f5xxx) and
> > Discovery (mv78xx0) supports a Device Bus controller to access several
> > kinds of memories and I/O devices (NOR, NAND, SRAM, FPGA).
> > 
> > This commit adds a driver to handle this controller. So far only
> > Armada 370, Armada XP and Discovery SoCs are supported.
> > 
> > The driver must be registered through a device tree node;
> > as explained in the binding document.
> > 
> > For each child node in the device tree, this driver will:
> >   * set timing parameters
> >   * register a child device
> >   * setup an address decoding window, using the mbus driver
> > 
> > Keep in mind the address decoding window setup is only a temporary hack.
> > This code will be removed from this devbus driver as soon as a proper device
> > tree binding for the mbus driver is added.
> > 
> > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
> > Acked-by: Arnd Bergmann <arnd@...db.de>
> > ---
> > Hi Greg,
> > 
> > This patch Applies on today linux-next.
> > I don't know if we are still in time for you to take this
> > and merge it into v3.10.
> > 
> > All of the DT related changes are in linux-next through arm-soc,
> > but this driver was left out and, unless you take it, will
> > get queued for v3.11. So it's up to you.
> 
> It's way too late for new drivers for 3.10, sorry.  I'll hold on to this
> and merge it to my trees after 3.10-rc1 is out for inclusion in 3.11.
> 

That's fine, no problem.

-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
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/