From: Stephen Boyd <sboyd@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@sonymobile.com>
Cc: Andy Gross <agross@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] soc: qcom: smem: Move RPM message ram out of smem DT node
Date: Tue, 8 Sep 2015 16:39:09 -0700 [thread overview]
Message-ID: <55EF719D.80702@codeaurora.org> (raw)
In-Reply-To: <20150908231858.GB13472@usrtlx11787.corpusers.net>
On 09/08/2015 04:18 PM, Bjorn Andersson wrote:
> On Tue 08 Sep 15:20 PDT 2015, Stephen Boyd wrote:
>
>> SMEM is a software construct built on top of a DDR carveout and
>> sometimes a device memory called RPM message ram. Having the RPM
>> message ram in the smem DT node's reg property leads to the smem
>> node being located in different places depending on if the
>> message ram is being used or not. Let's add a qcom specific
>> property, qcom,rpm-msg-ram, and point to the device memory from
>> the SMEM node via a phandle. This allows us to always have the
>> SMEM node at the root of the DT regardless of whether it's using
>> the message ram or not.
>>
> Based on the codeaurora limit of 99 aux-mem regions I figured this had
> to be more generic. But I think this makes sense and we can easily
> extend it with other specific regions (if we ever find any of those
> other 98 supported aux-mems).
Great.
>
>
> Can you update the dt binding document as well?
>
>
Sure. Is there a binding document? I couldn't find one.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-09-08 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 22:20 [PATCH] soc: qcom: smem: Move RPM message ram out of smem DT node Stephen Boyd
2015-09-08 23:18 ` Bjorn Andersson
2015-09-08 23:39 ` Stephen Boyd [this message]
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=55EF719D.80702@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).