From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 26 Jul 2017 10:11:55 -0700 From: Bjorn Andersson Subject: Re: [PATCH v1 1/2] remoteproc: dt: Provide bindings for iMX6SX/7D Remote Processor Controller driver Message-ID: <20170726171155.GE20643@builder> References: <20170710144220.31594-1-o.rempel@pengutronix.de> <20170710144220.31594-2-o.rempel@pengutronix.de> <20170710221408.GD1618@tuxbook> <91bfe236-0410-b26e-7ef6-73d14ebf120d@pengutronix.de> <20170718163814.GD20973@minitux> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: To: Oleksij Rempel Cc: Oleksij Rempel , Oleksij Rempel , devicetree@vger.kernel.org, kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Rob Herring , Mark Rutland , Russell King , Shawn Guo , Fabio Estevam , Ohad Ben-Cohen , linux-remoteproc@vger.kernel.org List-ID: 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bjorn Andersson Subject: Re: [PATCH v1 1/2] remoteproc: dt: Provide bindings for iMX6SX/7D Remote Processor Controller driver Date: Wed, 26 Jul 2017 10:11:55 -0700 Message-ID: <20170726171155.GE20643@builder> References: <20170710144220.31594-1-o.rempel@pengutronix.de> <20170710144220.31594-2-o.rempel@pengutronix.de> <20170710221408.GD1618@tuxbook> <91bfe236-0410-b26e-7ef6-73d14ebf120d@pengutronix.de> <20170718163814.GD20973@minitux> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Oleksij Rempel Cc: Oleksij Rempel , Oleksij Rempel , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Rob Herring , Mark Rutland , Russell King , Shawn Guo , Fabio Estevam , Ohad Ben-Cohen , linux-remoteproc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: devicetree@vger.kernel.org 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 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: bjorn.andersson@linaro.org (Bjorn Andersson) Date: Wed, 26 Jul 2017 10:11:55 -0700 Subject: [PATCH v1 1/2] remoteproc: dt: Provide bindings for iMX6SX/7D Remote Processor Controller driver In-Reply-To: References: <20170710144220.31594-1-o.rempel@pengutronix.de> <20170710144220.31594-2-o.rempel@pengutronix.de> <20170710221408.GD1618@tuxbook> <91bfe236-0410-b26e-7ef6-73d14ebf120d@pengutronix.de> <20170718163814.GD20973@minitux> Message-ID: <20170726171155.GE20643@builder> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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