[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170726171155.GE20643@builder>
Date: Wed, 26 Jul 2017 10:11:55 -0700
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Oleksij Rempel <linux@...pel-privat.de>
Cc: Oleksij Rempel <ore@...gutronix.de>,
Oleksij Rempel <o.rempel@...gutronix.de>,
devicetree@...r.kernel.org, kernel@...gutronix.de,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Russell King <linux@...linux.org.uk>,
Shawn Guo <shawnguo@...nel.org>,
Fabio Estevam <fabio.estevam@....com>,
Ohad Ben-Cohen <ohad@...ery.com>,
linux-remoteproc@...r.kernel.org
Subject: Re: [PATCH v1 1/2] remoteproc: dt: Provide bindings for iMX6SX/7D
Remote Processor Controller driver
On Sun 23 Jul 22:56 PDT 2017, Oleksij Rempel wrote:
> Am 18.07.2017 um 18:38 schrieb Bjorn Andersson:
> > On Tue 18 Jul 01:45 PDT 2017, Oleksij Rempel wrote:
> >> On 11.07.2017 00:14, Bjorn Andersson wrote:
[..]
> >>> Also, as you warn about the user needing to pick the values for "ddr",
> >>> does that mean that it's a carveout of System RAM?
> >>
> >> Yes, it is a part of System RAM.
> >>
> >
> > Then there will be an associated reserved-memory region for the
> > region(s), you should add a label to this and use "memory-region" to get
> > hold of the addresses instead.
>
> Ok. Should only system memory region be assigned over reserved-memory or
> all of named regions?
>
You can do it either way, but unless you see a strong reason against it
I would recommend just having a single region, for simplicity.
Regards,
Bjorn
Powered by blists - more mailing lists