linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] Device Bus support for Marvell EBU SoC
Date: Mon, 8 Apr 2013 12:29:34 -0300	[thread overview]
Message-ID: <20130408152933.GB877@localhost> (raw)
In-Reply-To: <201304081617.31644.arnd@arndb.de>

On Mon, Apr 08, 2013 at 04:17:31PM +0200, Arnd Bergmann wrote:
> On Monday 08 April 2013, Ezequiel Garcia wrote:
> >   * Rename devbus,dev-width to devbus,bus-width and changed the
> >     parameter value from bytes to bits: <8>, <16>, ...
> >     Suggested by Arnd Bergmann.
> > 
> >   * As suggested by Jason Gunthorpe and agreed by Arnd Bergmann.
> >     Reworked the whole devbus child chip-select device tree design.
> >     Now there's a separate devbus at addr DT node for each controller
> >     chip select. The impact of this is:
> >       1. Timing parameters now go into the parent node.
> >       2. There can only be one child per devbus node.
> > 
> >   * Remove unneeded bank-width parameter read.
> > 
> 
> Whole series:
> 
> Acked-by: Arnd Bergmann <arnd@arndb.de>
> 
> It may be nicer to use #address-cells=<2> for devbus device nodes now that
> each of them has only a 32 bit address space, but the current code is correct
> as well using a 64 bit notation.
> 

I'll probably be sending a v5 fixing this later.

@Jason Cooper:
How would you like to handle this, regarding the LPAE series?
Do you want me to rebase this devbus on top of that?

-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2013-04-08 15:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 11:06 [PATCH v4 0/5] Device Bus support for Marvell EBU SoC Ezequiel Garcia
2013-04-08 11:06 ` [PATCH v4 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver Ezequiel Garcia
2013-04-08 17:19   ` Jason Gunthorpe
2013-04-08 19:15     ` Arnd Bergmann
2013-04-09  0:42     ` Ezequiel Garcia
2013-04-09  9:40       ` Arnd Bergmann
2013-04-09 10:34         ` Ezequiel Garcia
2013-04-09 10:44           ` Arnd Bergmann
2013-04-09 11:00             ` Ezequiel Garcia
2013-04-09 16:00             ` Jason Gunthorpe
2013-04-09 16:03       ` Jason Gunthorpe
2013-04-09 20:28         ` Ezequiel Garcia
2013-04-08 11:06 ` [PATCH v4 2/5] ARM: mvebu: Add Device Bus support for Armada 370/XP SoC Ezequiel Garcia
2013-04-08 11:06 ` [PATCH v4 3/5] ARM: mvebu: Add support for NOR flash device on Armada XP-GP board Ezequiel Garcia
2013-04-08 11:06 ` [PATCH v4 4/5] ARM: mvebu: Add support for NOR flash device on Openblocks AX3 board Ezequiel Garcia
2013-04-08 11:06 ` [PATCH v4 5/5] ARM: mvebu: Add Device Bus and CFI flash memory support to defconfig Ezequiel Garcia
2013-04-08 14:17 ` [PATCH v4 0/5] Device Bus support for Marvell EBU SoC Arnd Bergmann
2013-04-08 15:29   ` Ezequiel Garcia [this message]
2013-04-08 18:30     ` Jason Cooper
2013-04-08 19:10       ` 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=20130408152933.GB877@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).