From: Ezequiel Garcia <elezegarcia@gmail.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
Javier Martinez Canillas <javier@dowhile0.org>,
Tony Lindgren <tony@atomide.com>,
device-tree <devicetree-discuss@lists.ozlabs.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 5/9] ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5
Date: Thu, 14 Mar 2013 12:57:44 -0300 [thread overview]
Message-ID: <CALF0-+U76UpJ35hWpYGkLf5uDxfaZqcB_h-_JJdvapHSTQ0amg@mail.gmail.com> (raw)
In-Reply-To: <5141F1C3.6090009@ti.com>
On Thu, Mar 14, 2013 at 12:50 PM, Jon Hunter <jon-hunter@ti.com> wrote:
>> Yes, I full agree with that as well. The size should be purely HW
>> related. So we should not take any assumption about the page size /
>> alignment.
>
> Ok, what is best to use? The size from hwmod structures or the size from
> the documentation?
>
My personal vote is: according to hardware documentation is the right thing,
and it's what we're doing in mvebu.
--
Ezequiel
next prev parent reply other threads:[~2013-03-14 15:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 17:27 [PATCH 0/9] ARM: dts: Various OMAP2+ device-tree updates Jon Hunter
2013-03-08 17:27 ` [PATCH 1/9] ARM: OMAP2+: Prepare for device-tree PMU support Jon Hunter
2013-03-08 17:27 ` [PATCH 2/9] ARM: dts: OMAP2+: Add PMU nodes Jon Hunter
2013-03-08 17:27 ` [PATCH 3/9] ARM: dts: OMAP2+: Add SDMA controller bindings and nodes Jon Hunter
2013-03-08 17:27 ` [PATCH 4/9] ARM: dts: OMAP3: Add support for OMAP3430 SDP board Jon Hunter
2013-03-09 2:25 ` Anil Kumar
2013-03-11 17:53 ` Jon Hunter
2013-03-12 2:42 ` Kumar, Anil
2013-03-12 8:50 ` Javier Martinez Canillas
2013-03-13 2:50 ` Kumar, Anil
2013-03-12 21:27 ` Jon Hunter
2013-03-13 2:59 ` Kumar, Anil
2013-03-11 2:45 ` Anil Kumar
2013-03-11 17:54 ` Jon Hunter
2013-03-08 17:27 ` [PATCH 5/9] ARM: dts: Add GPMC node for OMAP2, OMAP4 and OMAP5 Jon Hunter
2013-03-08 20:25 ` Javier Martinez Canillas
2013-03-08 21:41 ` Jon Hunter
2013-03-09 1:25 ` Javier Martinez Canillas
2013-03-09 12:42 ` Ezequiel Garcia
2013-03-11 17:56 ` Jon Hunter
2013-03-14 15:45 ` Benoit Cousson
2013-03-14 15:50 ` Jon Hunter
2013-03-14 15:57 ` Ezequiel Garcia [this message]
2013-03-14 15:58 ` Benoit Cousson
2013-03-14 16:00 ` Jon Hunter
2013-03-14 16:03 ` Benoit Cousson
2013-03-08 17:27 ` [PATCH 6/9] ARM: dts: Add OMAP3430 SDP flash memory bindings Jon Hunter
2013-03-08 17:27 ` [PATCH 7/9] ARM: dts: Add OMAP2 gpio bindings Jon Hunter
2013-03-08 17:27 ` [PATCH 8/9] ARM: dts: OMAP3+: Correct gpio #interrupts-cells property Jon Hunter
2013-03-08 17:27 ` [PATCH 9/9] ARM: dts: OMAP3: Add reg and interrupt properties for gpio Jon Hunter
2013-03-14 14:57 ` [PATCH 0/9] ARM: dts: Various OMAP2+ device-tree updates Benoit Cousson
2013-03-14 15:45 ` Florian Vaussard
2013-03-14 15:59 ` Jon Hunter
2013-03-14 16:06 ` Benoit Cousson
2013-03-14 16:02 ` Javier Martinez Canillas
2013-03-14 16:04 ` Jon Hunter
2013-03-14 16:08 ` Benoit Cousson
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=CALF0-+U76UpJ35hWpYGkLf5uDxfaZqcB_h-_JJdvapHSTQ0amg@mail.gmail.com \
--to=elezegarcia@gmail.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=javier@dowhile0.org \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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).