From: Khiem Nguyen <khiem.nguyen.xt@rvc.renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Simon Horman <horms+renesas@verge.net.au>
Cc: "linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Magnus Damm <magnus.damm@gmail.com>,
"Khiem Trong. Nguyen" <khiem.nguyen.xt@rvc.renesas.com>,
Toru Oishi <toru.oishi.zj@rvc.renesas.com>
Subject: Re: [PATCH v2 1/3] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support
Date: Mon, 23 May 2016 14:51:08 +0700 [thread overview]
Message-ID: <5742B66C.7080102@rvc.renesas.com> (raw)
In-Reply-To: <CAMuHMdXsu=O13rLysob1Xp+5vWcp7gq6byCffR-6hGc+W-837A@mail.gmail.com>
Hi Simon, Geert,
On 5/23/2016 2:07 PM, Geert Uytterhoeven wrote:
> On Mon, May 23, 2016 at 3:28 AM, Simon Horman
> <horms+renesas@verge.net.au> wrote:
>> Basic support for the Gen 3 R-Car M3-W SoC.
>>
>> Based on work for the r8a7795 and r8a7796 SoCs by
>> Takeshi Kihara, Dirk Behme and Geert Uytterhoeven.
>>
>> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/renesas/r8a7796.dtsi
>> @@ -0,0 +1,120 @@
>> + psci {
>> + compatible = "arm,psci-1.0";
>
> Do we want to use 1.0 on r8a7795, too?
I think we should apply same setting as r8a7795.
i.e compatible = "arm,psci-0.2";
Using 1.0 will open Suspend-to-RAM support if secure firmware supports
that feature.
However, we might need additional work in drivers to support
suspend/resume handlers.
So, I suggest that we keep using 0.2 until Suspend-to-RAM feature is
confirmed in r8a7795/r8a7796.
Best regards,
KHIEM Nguyen
WARNING: multiple messages have this Message-ID (diff)
From: khiem.nguyen.xt@rvc.renesas.com (Khiem Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support
Date: Mon, 23 May 2016 14:51:08 +0700 [thread overview]
Message-ID: <5742B66C.7080102@rvc.renesas.com> (raw)
In-Reply-To: <CAMuHMdXsu=O13rLysob1Xp+5vWcp7gq6byCffR-6hGc+W-837A@mail.gmail.com>
Hi Simon, Geert,
On 5/23/2016 2:07 PM, Geert Uytterhoeven wrote:
> On Mon, May 23, 2016 at 3:28 AM, Simon Horman
> <horms+renesas@verge.net.au> wrote:
>> Basic support for the Gen 3 R-Car M3-W SoC.
>>
>> Based on work for the r8a7795 and r8a7796 SoCs by
>> Takeshi Kihara, Dirk Behme and Geert Uytterhoeven.
>>
>> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/renesas/r8a7796.dtsi
>> @@ -0,0 +1,120 @@
>> + psci {
>> + compatible = "arm,psci-1.0";
>
> Do we want to use 1.0 on r8a7795, too?
I think we should apply same setting as r8a7795.
i.e compatible = "arm,psci-0.2";
Using 1.0 will open Suspend-to-RAM support if secure firmware supports
that feature.
However, we might need additional work in drivers to support
suspend/resume handlers.
So, I suggest that we keep using 0.2 until Suspend-to-RAM feature is
confirmed in r8a7795/r8a7796.
Best regards,
KHIEM Nguyen
next prev parent reply other threads:[~2016-05-23 7:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 1:28 [PATCH v2 0/3] arm64: Add Renesas R8A7796 SoC support Simon Horman
2016-05-23 1:28 ` Simon Horman
2016-05-23 1:28 ` [PATCH v2 1/3] arm64: dts: r8a7796: " Simon Horman
2016-05-23 1:28 ` Simon Horman
2016-05-23 7:07 ` Geert Uytterhoeven
2016-05-23 7:07 ` Geert Uytterhoeven
2016-05-23 7:51 ` Khiem Nguyen [this message]
2016-05-23 7:51 ` Khiem Nguyen
2016-05-24 1:42 ` Simon Horman
2016-05-24 1:42 ` Simon Horman
2016-05-24 6:35 ` Geert Uytterhoeven
2016-05-24 6:35 ` Geert Uytterhoeven
2016-05-24 7:29 ` Khiem Nguyen
2016-05-24 7:29 ` Khiem Nguyen
2016-05-24 1:44 ` Simon Horman
2016-05-24 1:44 ` Simon Horman
2016-05-23 1:28 ` [PATCH v2 2/3] arm64: dts: salvator-x: add Salvator-X board on R8A7796 SoC Simon Horman
2016-05-23 1:28 ` Simon Horman
2016-05-23 1:28 ` [PATCH v2 3/3] arm64: defconfig: enable Renesas " Simon Horman
2016-05-23 1:28 ` Simon Horman
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=5742B66C.7080102@rvc.renesas.com \
--to=khiem.nguyen.xt@rvc.renesas.com \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=toru.oishi.zj@rvc.renesas.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 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.