[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK=WgbaooxQyTYJ8rTP5ss9_hMuWbvYjeAJTKq5kVqYuXaweuA@mail.gmail.com>
Date: Sat, 16 May 2015 11:43:26 +0300
From: Ohad Ben-Cohen <ohad@...ery.com>
To: Suman Anna <s-anna@...com>
Cc: Dave Gerlach <d-gerlach@...com>,
linux-arm <linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Kevin Hilman <khilman@...aro.org>,
Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH v3 4/4] remoteproc/wkup_m3: add a remoteproc driver for TI
Wakeup M3
Hi Suman,
On Mon, May 11, 2015 at 6:01 PM, Suman Anna <s-anna@...com> wrote:
> We don't have any carveouts or usage of any external DDR, as this
> processor is used during Power Management, like cpuidle or suspend path,
> and is used to control the MPU and DDR states. The resource table is
> very simple and straight-forward [1].
Ok thanks.
Could you please document in the patch how the WkupM3 memory is
managed? Perhaps add to this latter explanation of yours also what
stands behind the umem/dmem names, justify usage of '__force' and
document the code around the l4_offset math (which I suspect may not
always be correct, as it seems the value of l4_offset depends on the
order of mem resources returned by platform_get_resource_byname).
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists