From: Grant Likely <grant.likely@secretlab.ca>
To: Tomasz Figa <t.figa@samsung.com>, Stephen Warren <swarren@wwwdotorg.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Laura Abbott <lauraa@codeaurora.org>,
Pawel Moll <pawel.moll@arm.com>, Arnd Bergmann <arnd@arndb.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Tomasz Figa <tomasz.figa@gmail.com>,
Michal Nazarewicz <mina86@mina86.com>,
linaro-mm-sig@lists.linaro.org, Marc <marc.ceeeee@gmail.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Kumar Gala <galak@codeaurora.org>,
Olof Johansson <olof@lixom.net>,
Ian Campbell <ian.campbell@citrix.com>,
Nishanth Peethambaran <nishanth.p@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH v6 3/4] drivers: of: add initialization code for dma reserved memory
Date: Thu, 29 Aug 2013 22:20:54 +0100 [thread overview]
Message-ID: <20130829212054.568123E1222@localhost> (raw)
In-Reply-To: <2011590.EGDykoeEOS@amdc1227>
On Wed, 21 Aug 2013 17:39:48 +0200, Tomasz Figa <t.figa@samsung.com> wrote:
> On Tuesday 20 of August 2013 10:35:51 Stephen Warren wrote:
> > >> a) Adjust memory.txt to allow multiple entries in memory-regions, and
> > >> add an associated memory-region-names property.
> > >>
> > I don't believe that's a good approach unless you have at least a
> > partial idea of how the current bindings will be extended to support
> > multiple memory regions.
>
> I believe that at least three "at least partial" ideas have been brought in
> this thread. Moreover, I don't think that defining the simple binding now
> would stop us from extending it according to any of those ideas in any way.
I would plan on extending later with suggestion 'a)' above. Making the
memory-region an array of phandles is a better match with how most of
the core bindings work. I actually regret the *-gpio properties that
were defined earlier becasue it makes it harder for software to look at
a tree and determine if there are any gpio references.
It of course doesn't need to be done immediately, only when it becomes
required.
g.
prev parent reply other threads:[~2013-08-29 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1376924669-28873-1-git-send-email-m.szyprowski@samsung.com>
[not found] ` <1376924669-28873-3-git-send-email-m.szyprowski@samsung.com>
2013-08-26 12:09 ` [PATCH v6 2/4] drivers: of: add function to scan fdt nodes given by path Rob Herring
[not found] ` <1376924669-28873-4-git-send-email-m.szyprowski@samsung.com>
2013-08-26 12:20 ` [PATCH v6 3/4] drivers: of: add initialization code for dma reserved memory Rob Herring
[not found] ` <521292E0.105@wwwdotorg.org>
[not found] ` <98354044.bRIxVeGEeu@flatron>
2013-08-29 21:12 ` Grant Likely
[not found] ` <52134B92.10308@samsung.com>
[not found] ` <52139AE7.4050300@wwwdotorg.org>
[not found] ` <2011590.EGDykoeEOS@amdc1227>
2013-08-29 21:20 ` Grant Likely [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=20130829212054.568123E1222@localhost \
--to=grant.likely@secretlab.ca \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ian.campbell@citrix.com \
--cc=kyungmin.park@samsung.com \
--cc=lauraa@codeaurora.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=marc.ceeeee@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mina86@mina86.com \
--cc=nishanth.p@gmail.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=s.hauer@pengutronix.de \
--cc=s.nawrocki@samsung.com \
--cc=swarren@wwwdotorg.org \
--cc=t.figa@samsung.com \
--cc=tomasz.figa@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).