All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khiem Nguyen <khiem.nguyen.xt@rvc.renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms+renesas@verge.net.au>,
	"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>,
	Toru Oishi <toru.oishi.zj@rvc.renesas.com>,
	"Khiem Trong. Nguyen" <khiem.nguyen.xt@rvc.renesas.com>
Subject: Re: [PATCH v2 1/3] arm64: dts: r8a7796: Add Renesas R8A7796 SoC support
Date: Tue, 24 May 2016 14:29:28 +0700	[thread overview]
Message-ID: <574402D8.6030400@rvc.renesas.com> (raw)
In-Reply-To: <CAMuHMdV+atFKJjxcH7RkBCdabsBqk5Y3TTHCPN+sprDaM1xj_w@mail.gmail.com>

Hi Geert,

On 5/24/2016 1:35 PM, Geert Uytterhoeven wrote:
> Hi Khiem,
>
> On Mon, May 23, 2016 at 9:51 AM, Khiem Nguyen
> <khiem.nguyen.xt@rvc.renesas.com> wrote:
>> 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.
>
> Note that we do have suspend/resume support on R-Car Gen2, albeit some
> drivers may lack code to save/restore state when their devices are powered
> down, as R-Car Gen2 doesn't have power domains for devices.
>
> So I'd expect everything to work fine, as long as no R-Car Gen3-specific
> drivers or devices residing in multimedia power domains are involved.

In my test environment using latest integration branch in 
renesas-drivers (v4.6), it failed to resume due to operation inside 
rcar_du_pm_resume().
Probably, it should be fixed soon.

FYI, your secure firmware will have Suspend-to-RAM support if below log 
is output.
    psci: PSCIv1.0 detected in firmware.

Thanks.

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: Tue, 24 May 2016 14:29:28 +0700	[thread overview]
Message-ID: <574402D8.6030400@rvc.renesas.com> (raw)
In-Reply-To: <CAMuHMdV+atFKJjxcH7RkBCdabsBqk5Y3TTHCPN+sprDaM1xj_w@mail.gmail.com>

Hi Geert,

On 5/24/2016 1:35 PM, Geert Uytterhoeven wrote:
> Hi Khiem,
>
> On Mon, May 23, 2016 at 9:51 AM, Khiem Nguyen
> <khiem.nguyen.xt@rvc.renesas.com> wrote:
>> 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.
>
> Note that we do have suspend/resume support on R-Car Gen2, albeit some
> drivers may lack code to save/restore state when their devices are powered
> down, as R-Car Gen2 doesn't have power domains for devices.
>
> So I'd expect everything to work fine, as long as no R-Car Gen3-specific
> drivers or devices residing in multimedia power domains are involved.

In my test environment using latest integration branch in 
renesas-drivers (v4.6), it failed to resume due to operation inside 
rcar_du_pm_resume().
Probably, it should be fixed soon.

FYI, your secure firmware will have Suspend-to-RAM support if below log 
is output.
    psci: PSCIv1.0 detected in firmware.

Thanks.

Best regards,
KHIEM Nguyen

  reply	other threads:[~2016-05-24  7:29 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
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 [this message]
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=574402D8.6030400@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.