From: Greg KH <gregkh@linuxfoundation.org>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Olof Johansson <olof@lixom.net>,
Jason Cooper <jason@lakedaemon.net>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Arnd Bergmann <arnd@arndb.de>,
Gregory Clement <gregory.clement@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
Maen Suleiman <maen@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Subject: Re: [PATCH] drivers: memory: Introduce Marvell EBU Device Bus driver
Date: Tue, 23 Apr 2013 12:48:22 -0700 [thread overview]
Message-ID: <20130423194822.GA7214@kroah.com> (raw)
In-Reply-To: <1366744886-3019-1-git-send-email-elezegarcia@gmail.com>
On Tue, Apr 23, 2013 at 04:21:26PM -0300, Ezequiel Garcia wrote:
> From: Ezequiel Garcia <ezequiel.garcia@free-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@free-electrons.com>
> Acked-by: Arnd Bergmann <arnd@arndb.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.
thanks,
greg k-h
next prev parent reply other threads:[~2013-04-23 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 19:21 [PATCH] drivers: memory: Introduce Marvell EBU Device Bus driver Ezequiel Garcia
2013-04-23 19:48 ` Greg KH [this message]
2013-04-23 19:55 ` Ezequiel Garcia
2013-05-13 20:12 ` Jason Cooper
2013-05-16 22:15 ` Ezequiel Garcia
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=20130423194822.GA7214@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=elezegarcia@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maen@marvell.com \
--cc=olof@lixom.net \
--cc=thomas.petazzoni@free-electrons.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