From: Tony Lindgren <tony@atomide.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Ezequiel Garcia <elezegarcia@gmail.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"zonque@gmail.com" <zonque@gmail.com>,
"matthias.bgg@googlemail.com" <matthias.bgg@googlemail.com>,
Javier Martinez Canillas <martinez.javier@gmail.com>,
Enric Balletbo Serra <eballetbo@gmail.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"b-cousson@ti.com" <b-cousson@ti.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"jon-hunter@ti.com" <jon-hunter@ti.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH v3 3/3] arm: omap2: gpmc: add DT bindings for OneNAND
Date: Fri, 1 Feb 2013 14:12:10 -0800 [thread overview]
Message-ID: <20130201221209.GA22517@atomide.com> (raw)
In-Reply-To: <20130128115339.GD7754@e106331-lin.cambridge.arm.com>
* Mark Rutland <mark.rutland@arm.com> [130128 03:57]:
>
> So if I've understood correctly, the first address cell is the CS, and the
> second the offset within this (as the comment in the onenand@0 node hints)?
>
> If so, the code now makes sense to me :)
Sounds like further checking can be added as needed, so applying this
series into omap-for-v3.9/gpmc.
Regards,
Tony
prev parent reply other threads:[~2013-02-01 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 12:23 [PATCH v3 1/3] mtd: omap-onenand: pass device_node in platform data Ezequiel Garcia
2013-01-25 12:23 ` [PATCH v3 2/3] arm: omap2: gpmc-onenand: drop __init annotation Ezequiel Garcia
2013-01-25 12:23 ` [PATCH v3 3/3] arm: omap2: gpmc: add DT bindings for OneNAND Ezequiel Garcia
2013-01-25 15:56 ` Mark Rutland
2013-01-25 18:11 ` Ezequiel Garcia
2013-01-28 11:53 ` Mark Rutland
2013-02-01 22:12 ` Tony Lindgren [this message]
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=20130201221209.GA22517@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=dedekind1@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=eballetbo@gmail.com \
--cc=elezegarcia@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=grant.likely@secretlab.ca \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martinez.javier@gmail.com \
--cc=matthias.bgg@googlemail.com \
--cc=zonque@gmail.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;
as well as URLs for NNTP newsgroup(s).