From: Mathieu Olivari <mathieu@codeaurora.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, dwmw2@infradead.org,
computersforpeace@gmail.com, agross@codeaurora.org,
bjorn.andersson@sonymobile.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 2/3] ARM: qcom: add SMEM device node to IPQ806x dts
Date: Fri, 14 Aug 2015 11:54:48 -0700 [thread overview]
Message-ID: <20150814185446.GB7516@codeaurora.org> (raw)
In-Reply-To: <55CD2EFE.8040606@codeaurora.org>
On Thu, Aug 13, 2015 at 04:57:50PM -0700, Stephen Boyd wrote:
> On 08/13/2015 02:33 PM, Mathieu Olivari wrote:
> >@@ -79,6 +79,15 @@
> > #hwlock-cells = <1>;
> > };
> >+
> >+ smem {
> >+ compatible = "qcom,smem";
> >+
> >+ memory-region = <&smem>;
> >+ reg = <0x41000000 0x4000>;
>
> Does this reg property do something? I thought we were supposed to leave
> this out when not using the rpm msg ram. Also, if there's no reg, it should
> be at the root /.
Actually; no it doesn't do much. I'll remove it.
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
WARNING: multiple messages have this Message-ID (diff)
From: mathieu@codeaurora.org (Mathieu Olivari)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: qcom: add SMEM device node to IPQ806x dts
Date: Fri, 14 Aug 2015 11:54:48 -0700 [thread overview]
Message-ID: <20150814185446.GB7516@codeaurora.org> (raw)
In-Reply-To: <55CD2EFE.8040606@codeaurora.org>
On Thu, Aug 13, 2015 at 04:57:50PM -0700, Stephen Boyd wrote:
> On 08/13/2015 02:33 PM, Mathieu Olivari wrote:
> >@@ -79,6 +79,15 @@
> > #hwlock-cells = <1>;
> > };
> >+
> >+ smem {
> >+ compatible = "qcom,smem";
> >+
> >+ memory-region = <&smem>;
> >+ reg = <0x41000000 0x4000>;
>
> Does this reg property do something? I thought we were supposed to leave
> this out when not using the rpm msg ram. Also, if there's no reg, it should
> be at the root /.
Actually; no it doesn't do much. I'll remove it.
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
next prev parent reply other threads:[~2015-08-14 18:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 21:33 [PATCH 0/3] qcom: Add SMEM MTD parser Mathieu Olivari
2015-08-13 21:33 ` Mathieu Olivari
2015-08-13 21:33 ` Mathieu Olivari
2015-08-13 21:33 ` [PATCH 1/3] ARM: qcom: add SFPB nodes to IPQ806x dts Mathieu Olivari
2015-08-13 21:33 ` Mathieu Olivari
2015-08-13 21:33 ` Mathieu Olivari
2015-08-13 23:18 ` Stephen Boyd
2015-08-13 23:18 ` Stephen Boyd
2015-08-13 23:18 ` Stephen Boyd
2015-08-14 17:25 ` Mathieu Olivari
2015-08-14 17:25 ` Mathieu Olivari
2015-08-13 21:33 ` [PATCH 2/3] ARM: qcom: add SMEM device node " Mathieu Olivari
2015-08-13 21:33 ` Mathieu Olivari
2015-08-13 23:57 ` Stephen Boyd
2015-08-13 23:57 ` Stephen Boyd
2015-08-13 23:57 ` Stephen Boyd
2015-08-14 18:54 ` Mathieu Olivari [this message]
2015-08-14 18:54 ` Mathieu Olivari
2015-08-13 21:33 ` [PATCH 3/3] mtd: add SMEM parser for QCOM platforms Mathieu Olivari
2015-08-13 21:33 ` Mathieu Olivari
2015-08-14 0:38 ` Stephen Boyd
2015-08-14 0:38 ` Stephen Boyd
2015-08-14 0:38 ` Stephen Boyd
2015-08-14 19:08 ` Mathieu Olivari
2015-08-14 19:08 ` Mathieu Olivari
-- strict thread matches above, loose matches on Subject: below --
2015-08-15 0:46 [PATCH 0/3] qcom: Add SMEM MTD parser Mathieu Olivari
2015-08-15 0:46 ` [PATCH 2/3] ARM: qcom: add SMEM device node to IPQ806x dts Mathieu Olivari
2015-08-15 0:46 ` Mathieu Olivari
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=20150814185446.GB7516@codeaurora.org \
--to=mathieu@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.