From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver
Date: Fri, 19 Apr 2013 15:10:59 -0300 [thread overview]
Message-ID: <20130419181058.GA2243@localhost> (raw)
In-Reply-To: <20130410194337.GA5681@kroah.com>
Hi Greg,
On Wed, Apr 10, 2013 at 12:43:37PM -0700, Greg KH wrote:
> > On Wed, Apr 10, 2013 at 04:04:00PM -0300, Ezequiel Garcia wrote:
> > > 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>
> > > ---
> > > .../bindings/memory-controllers/mvebu-devbus.txt | 156 ++++++++++
> > > drivers/memory/Kconfig | 10 +
> > > drivers/memory/Makefile | 1 +
> > > drivers/memory/mvebu-devbus.c | 340 +++++++++++++++++++++
> > > 4 files changed, 507 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/memory-controllers/mvebu-devbus.txt
> > > create mode 100644 drivers/memory/mvebu-devbus.c
> >
> > As every commit to drivers/memory has been signed by you, would you like
> > to take this patch through your tree? Or, I'll take it through arm-soc
> > with your Ack to keep the series together.
>
> Sure, feel free to take this through your tree and add:
>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Olof (in Cc) has just decided to drop the entire pull request from
Jason Cooper which contained this driver.
This means this patch will have to wait until v3.11.
The reasons for dropping the pull was because of a build error on powerpc64,
completely unrelated to this driver, the faulty commit was 9ecbe03ae85b
("pci: infrastructure to add drivers in drivers/pci/host").
Is it possible that you take this patch instead, so it can make it in v3.10?
Of course, assuming it's not already too late and this doesn't break any rule.
Thanks,
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-04-19 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 19:03 [PATCH v7 0/5] Device Bus support for Marvell EBU SoC Ezequiel Garcia
2013-04-10 19:04 ` [PATCH v7 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver Ezequiel Garcia
2013-04-10 19:16 ` Jason Cooper
2013-04-10 19:43 ` Greg KH
2013-04-19 18:10 ` Ezequiel Garcia [this message]
2013-04-19 18:16 ` Greg KH
2013-04-19 20:02 ` Ezequiel Garcia
2013-04-11 17:27 ` Jason Cooper
2013-04-10 19:04 ` [PATCH v7 2/5] ARM: mvebu: Add Device Bus support for Armada 370/XP SoC Ezequiel Garcia
2013-04-11 17:33 ` Jason Cooper
2013-04-10 19:04 ` [PATCH v7 3/5] ARM: mvebu: Add support for NOR flash device on Armada XP-GP board Ezequiel Garcia
2013-04-10 19:04 ` [PATCH v7 4/5] ARM: mvebu: Add support for NOR flash device on Openblocks AX3 board Ezequiel Garcia
2013-04-10 19:04 ` [PATCH v7 5/5] ARM: mvebu: Add Device Bus and CFI flash memory support to defconfig 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=20130419181058.GA2243@localhost \
--to=ezequiel.garcia@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).