From: s-anna@ti.com (Suman Anna)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] remoteproc: add support to handle internal memories
Date: Fri, 13 Feb 2015 10:13:40 -0600 [thread overview]
Message-ID: <54DE22B4.7020807@ti.com> (raw)
In-Reply-To: <CAK=WgbaK+TNJR1UHm7orcFk7kaGTWMQsW0XhX_t7qvWwe+YJEg@mail.gmail.com>
Ohad,
On 02/12/2015 11:20 PM, Ohad Ben-Cohen wrote:
> On Thu, Feb 12, 2015 at 10:54 PM, Suman Anna <s-anna@ti.com> wrote:
>> My original motivation was that it would only need to be added on
>> firmwares requiring support for loading into internal memories,
>> otherwise, these are something left to be managed by the software
>> running on the remote processor completely, and MPU will not even touch
>> them.
>
> Sure. But even if you guys will use this interface correctly, this
> patch essentially exposes ioremap to user space, which is something we
> generally want to avoid.
>
>> So, let me know if this is a NAK. If so, we have two options - one to go
>> the sram node model where each of them have to be defined separately,
>> and have a specific property in the rproc nodes to be able to get the
>> gen_pool handles. The other one is simply to define these as <reg> and
>> use devm_ioremap_resource() (so use DT for defining the regions instead
>> of a resource table entry).
>
> Any approach where these regions are defined explicitly really sounds
> better. If you could look into these two alternatives that would be
> great.
OK, will do. Meanwhile, can you pick up Patch 1, that is independent of
this patch.
regards
Suman
next prev parent reply other threads:[~2015-02-13 16:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 21:21 [PATCH v3 0/2] couple of generic remoteproc enhancements Suman Anna
2015-01-09 21:21 ` [PATCH v3 1/2] remoteproc: use a flag to detect the presence of IOMMU Suman Anna
2015-03-12 9:04 ` Ohad Ben-Cohen
2015-03-13 23:35 ` Suman Anna
2015-01-09 21:21 ` [PATCH v3 2/2] remoteproc: add support to handle internal memories Suman Anna
2015-02-10 10:10 ` Ohad Ben-Cohen
2015-02-11 20:57 ` Tony Lindgren
2015-02-11 22:28 ` Suman Anna
2015-02-11 22:48 ` Tony Lindgren
2015-02-12 0:01 ` Suman Anna
2015-02-12 0:18 ` Tony Lindgren
2015-02-12 1:07 ` Suman Anna
2015-02-12 9:09 ` Ohad Ben-Cohen
2015-02-12 20:54 ` Suman Anna
2015-02-13 5:20 ` Ohad Ben-Cohen
2015-02-13 16:13 ` Suman Anna [this message]
2015-02-13 18:35 ` Tony Lindgren
2015-01-22 21:52 ` [PATCH v3 0/2] couple of generic remoteproc enhancements Suman Anna
2015-02-03 20:55 ` Suman Anna
2015-02-05 15:11 ` Ohad Ben-Cohen
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=54DE22B4.7020807@ti.com \
--to=s-anna@ti.com \
--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 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).