From: Jisheng Zhang <jszhang@marvell.com>
To: "Antoine Ténart" <antoine.tenart@free-electrons.com>
Cc: "sebastian.hesselbarth@gmail.com"
<sebastian.hesselbarth@gmail.com>,
"alexandre.belloni@free-electrons.com"
<alexandre.belloni@free-electrons.com>,
Jimmy Xu <zmxu@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] ARM: dts: document the berlin enable-method property
Date: Thu, 3 Apr 2014 17:14:15 +0800 [thread overview]
Message-ID: <20140403171415.13adae45@xhacker> (raw)
In-Reply-To: <533D21AF.2070508@free-electrons.com>
Hi Antoine,
On Thu, 3 Apr 2014 01:54:07 -0700
Antoine Ténart <antoine.tenart@free-electrons.com> wrote:
> Jisheng,
>
> On 03/04/2014 10:22, Jisheng Zhang wrote:
> > Hi,
> >
> > On Thu, 3 Apr 2014 01:08:15 -0700
> > Antoine Ténart <antoine.tenart@free-electrons.com> wrote:
> >
> >> Signed-off-by: Antoine Ténart <antoine.tenart@free-electrons.com>
> >> ---
> >> Documentation/devicetree/bindings/arm/cpus.txt | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/arm/cpus.txt
> >> b/Documentation/devicetree/bindings/arm/cpus.txt index
> >> 333f4aea3029..a9e42a2dbc99 100644 ---
> >> a/Documentation/devicetree/bindings/arm/cpus.txt +++
> >> b/Documentation/devicetree/bindings/arm/cpus.txt @@ -185,6 +185,8 @@
> >> nodes to be present and contain the properties described below.
> >> "qcom,gcc-msm8660" "qcom,kpss-acc-v1"
> >> "qcom,kpss-acc-v2"
> >> + "marvell,88de31-smp" - cpu-core handling for
> >
> > why not "marvell,berlin-smp"?
>
> We have SMP on the BG2 and the BG2Q currently. Future boards may not be
> compatible with this method (BG3 ?), I think "marvell,berlin-smp" is too
Yes. It's not compatible. But it will be PSCI. FWICT, current smp method
would be only used for BG2/BG2CT.
Thanks
next prev parent reply other threads:[~2014-04-03 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 8:08 [PATCH 0/3] ARM: berlin: convert smp to CPU_METHOD_OF_DECLARE Antoine Ténart
[not found] ` <1396512496-8030-1-git-send-email-antoine.tenart-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-04-03 8:08 ` [PATCH 1/3] ARM: berlin: use CPU_METHOD_OF_DECLARE for smp Antoine Ténart
2014-04-03 8:08 ` [PATCH 2/3] ARM: dts: document the berlin enable-method property Antoine Ténart
[not found] ` <1396512496-8030-3-git-send-email-antoine.tenart-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-04-03 8:22 ` Jisheng Zhang
2014-04-03 8:54 ` Antoine Ténart
2014-04-03 9:14 ` Jisheng Zhang [this message]
[not found] ` <533D21AF.2070508-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-04-03 9:14 ` Antoine Ténart
[not found] ` <533D268E.7070502-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-04-03 9:40 ` Sebastian Hesselbarth
2014-04-03 8:29 ` Alexandre Belloni
2014-04-03 9:02 ` Mark Rutland
2014-04-03 8:08 ` [PATCH 3/3] ARM: dts: berlin: add enable-method property in cpus node for smp Antoine Ténart
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=20140403171415.13adae45@xhacker \
--to=jszhang@marvell.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=antoine.tenart@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=zmxu@marvell.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;
as well as URLs for NNTP newsgroup(s).