From: Suman Anna <s-anna@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@oracle.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Tero Kristo <t-kristo@ti.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Vitaly Andrianov <vitalya@ti.com>
Subject: Re: [PATCH 0/5] Use mmio-sram driver for Keystone MSMC RAM
Date: Wed, 7 Sep 2016 11:22:02 -0500 [thread overview]
Message-ID: <f6920801-554d-18e8-f140-44aeeb2f878e@ti.com> (raw)
In-Reply-To: <d797bb0d-41b5-45a7-6faf-95baaab0215b@oracle.com>
Hi Santosh,
On 09/07/2016 11:11 AM, Santosh Shilimkar wrote:
> Hi Suman,
>
> On 9/1/2016 3:58 PM, Suman Anna wrote:
>> Hi,
>>
>> The Keystone 2 family of SoCs have an on-chip RAM called the
>> Multicore Shared Memory (MSM) RAM. This RAM is accessible through
>> the Multicore Shared Memory Controller (MSMC). This series represents
>> these on-chip RAMs as sram nodes so that the memory allocations
>> can be managed by the in-kernel mmio-sram driver.
>>
>> The first 4 patches adds the basic SRAM nodes on each of the SoCs,
>> and the last patch enables the generic on-chip SRAM driver for
>> keystone defconfig.
>>
> The series looks good in general but I would like to understand
> the users of this memory in kernel. Is that going to be posted
> as a follow up patch ? Is the Power controller going to make
> use of this SRAM for PM code ?
Yes, the users will eventually follow. Power Controller code is not
gonna be using this SRAM, it has its own RAM. This memory is gonna be
split between various functional features like IPC, OPTEE integration,
we already have the Boot Monitor code using this. We will have the
memory split by either having static child nodes or drivers requesting
the memory using gen_pool API.
regards
Suman
next prev parent reply other threads:[~2016-09-07 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 22:58 Suman Anna
2016-09-01 22:58 ` [PATCH 1/5] ARM: dts: keystone-k2hk: Add MSM RAM node Suman Anna
2016-09-01 22:58 ` [PATCH 2/5] ARM: dts: keystone-k2l: " Suman Anna
2016-09-01 22:58 ` [PATCH 3/5] ARM: dts: keystone-k2e: " Suman Anna
2016-09-01 22:58 ` [PATCH 4/5] ARM: dts: keystone-k2g: " Suman Anna
2016-09-01 22:58 ` [PATCH 5/5] ARM: configs: keystone: Enable Generic on-chip SRAM driver Suman Anna
2016-09-07 16:11 ` [PATCH 0/5] Use mmio-sram driver for Keystone MSMC RAM Santosh Shilimkar
2016-09-07 16:22 ` Suman Anna [this message]
2016-09-07 16:25 ` Santosh Shilimkar
2016-09-07 16:31 ` Suman Anna
2017-01-06 18:56 ` santosh.shilimkar
2017-01-06 19:10 ` Suman Anna
2017-01-06 19:13 ` Santosh Shilimkar
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=f6920801-554d-18e8-f140-44aeeb2f878e@ti.com \
--to=s-anna@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m-karicheri2@ti.com \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=vitalya@ti.com \
/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
all inboxes | Powered by JetHome®