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 v3 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver
Date: Sat, 6 Apr 2013 11:50:52 -0300	[thread overview]
Message-ID: <20130406145051.GA2358@localhost> (raw)
In-Reply-To: <201304061534.36682.arnd@arndb.de>

Hi Arnd,

On Sat, Apr 06, 2013 at 03:34:36PM +0200, Arnd Bergmann wrote:
> On Saturday 06 April 2013, Ezequiel Garcia wrote:
> > +       device-bus at d0010400 {
> > +               status = "okay";
> > +               ranges = <0 0 0xf0000000 0x1000000>; /* CS0 @addr 0xf0000000, size 0x1000000 */
> > +               #address-cells = <2>;
> > +               #size-cells = <1>;
> > +
> > +               flash at 0 {
> > +                       compatible = "cfi-flash";
> > +
> > +                       /* CS0, 16 MiB */
> > +                       reg = <0 0 0x1000000>;
> > +                       bank-width = <2>;
> > +                       #address-cells = <1>;
> > +                       #size-cells = <1>;
> > +
> > +                       /* Device Bus parameters are required */
> > +
> > +                       /* Read parameters */
> > +                       devbus,dev-width    = <1>;
> > +                       devbus,turn-off-ps  = <60000>;
> > +                       devbus,badr-skew-ps = <0>;
> > +                       devbus,acc-first-ps = <124000>;
> > +                       devbus,acc-next-ps  = <248000>;
> > +                       devbus,rd-setup-ps  = <0>;
> > +                       devbus,rd-hold-ps   = <0>;
> 
> I just read the email from Jason Gunthorpe suggesting to have a separate
> device-bus instance for each CS under it.
> 
> I think the implication of that is that all the "devbus,..." properties can
> now be moved into the parent node, which makes the split between the
> devbus node and its attached device clearer.
> 

Okey, I'll send a v4 fixing all your comments and implementing Jason's idea.

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

  reply	other threads:[~2013-04-06 14:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 11:15 [PATCH v3 0/5] Device Bus support for Marvell EBU SoC Ezequiel Garcia
2013-04-06 11:15 ` [PATCH v3 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver Ezequiel Garcia
2013-04-06 13:05   ` Arnd Bergmann
2013-04-06 13:34   ` Arnd Bergmann
2013-04-06 14:50     ` Ezequiel Garcia [this message]
2013-04-06 11:15 ` [PATCH v3 2/5] ARM: mvebu: Add Device Bus support for Armada 370/XP SoC Ezequiel Garcia
2013-04-06 11:15 ` [PATCH v3 3/5] ARM: mvebu: Add support for NOR flash device on Armada XP-GP board Ezequiel Garcia
2013-04-06 11:15 ` [PATCH v3 4/5] ARM: mvebu: Add support for NOR flash device on Openblocks AX3 board Ezequiel Garcia
2013-04-06 11:15 ` [PATCH v3 5/5] ARM: mvebu: Add Device Bus and CFI flash memory support to defconfig Ezequiel Garcia
2013-04-06 13:09 ` [PATCH v3 0/5] Device Bus support for Marvell EBU SoC Arnd Bergmann

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=20130406145051.GA2358@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).