From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] drivers: dma-contiguous: add initialization from device tree
Date: Mon, 16 Sep 2013 12:53:18 +1000 [thread overview]
Message-ID: <1379299998.4098.74.camel@pasglop> (raw)
In-Reply-To: <CACxGe6uzau+g0gd=hkNYw1zdkfq18zt_m9OEaiJKR6=q1U4rag@mail.gmail.com>
On Thu, 2013-07-11 at 15:56 +0100, Grant Likely wrote:
> > +contiguous-memory {
> > +
> > + (name): region@(base-address) {
> > + reg = <(baseaddr) (size)>;
> > + (linux,default-contiguous-region);
> > + device = <&device_0 &device_1 ...>
> > + };
> > +};
>
> Okay, I've gone and read all of the backlog on the 3 versions of the
> patch series, and I think I understand the issues. I actually think it
> was better off to have the regions specified as children of the memory
> node. I understand the argument about how would firmware know what
> size the kernel wants and that it would be better to have a kernel
> parameter to override the default. However, it is also reasonable for
> the kernel to be provided with a default amount of CMA based on the
> usage profile of the device. In that regard it is absolutely
> appropriate to put the CMA region data into the memory node. I don't
> think /chosen is the right place for that.
Picking up on that old thread after the rant I just posted ... Grant,
your proposal is all wrong.
First we already had a proposal for reserved memory, which due to the
complete lack of comment, we actually merged support for in powerpc in
3.11, second, do NOT make that a child of "memory". See the email I just
posted today for more details about the breakage in that proposal.
I'm advocating a revert at this stage.
Ben.
next prev parent reply other threads:[~2013-09-16 2:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 13:40 [PATCH v3 0/2] Device Tree support for CMA (Contiguous Memory Allocator) Marek Szyprowski
2013-06-26 13:40 ` Marek Szyprowski
2013-06-26 13:40 ` [PATCH v3 1/2] drivers: dma-contiguous: clean source code and prepare for device tree Marek Szyprowski
2013-06-26 13:40 ` Marek Szyprowski
2013-06-26 13:40 ` [PATCH v3 2/2] drivers: dma-contiguous: add initialization from " Marek Szyprowski
2013-06-26 13:40 ` Marek Szyprowski
2013-06-27 13:58 ` Bartlomiej Zolnierkiewicz
2013-06-27 13:58 ` Bartlomiej Zolnierkiewicz
2013-07-11 14:56 ` Grant Likely
2013-07-11 14:56 ` Grant Likely
2013-07-16 8:42 ` Marek Szyprowski
2013-07-16 8:42 ` Marek Szyprowski
2013-09-16 2:53 ` Benjamin Herrenschmidt [this message]
2013-09-16 2:58 ` Benjamin Herrenschmidt
2013-09-16 2:58 ` Benjamin Herrenschmidt
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=1379299998.4098.74.camel@pasglop \
--to=benh@kernel.crashing.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.