From: Olof Johansson <olof@lixom.net>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: arm@kernel.org, linux-renesas-soc@vger.kernel.org,
Kevin Hilman <khilman@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [GIT PULL] Second Round of Renesas ARM Based SoC Updates for v4.16
Date: Thu, 4 Jan 2018 22:52:22 -0800 [thread overview]
Message-ID: <20180105065222.zwpoyylkdjgl2rog@localhost> (raw)
In-Reply-To: <cover.1513936182.git.horms+renesas@verge.net.au>
On Fri, Dec 22, 2017 at 11:30:37AM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these second round of Renesas ARM based SoC updates for v4.16.
>
> This pull request is based on the previous round of
> such requests, tagged as renesas-soc-for-v4.16,
> which I have already sent a pull-request for.
>
>
> The following changes since commit 90f0d2b344313a8a4c366ef60d0df33008d2be84:
>
> soc: renesas: Identify R-Car M3-W ES1.1 (2017-11-27 11:40:57 +0100)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc2-for-v4.16
>
> for you to fetch changes up to 91c719f5ec6671f7b63762d78897af5583dd7693:
>
> soc: renesas: rcar-sysc: Keep wakeup sources active during system suspend (2017-12-20 11:16:05 +0100)
>
> ----------------------------------------------------------------
> Second Round of Renesas ARM Based SoC Updates for v4.16
>
> * rcar-sysc: Keep wakeup sources active during system suspend
>
> Geert Uytterhoeven says "If an R-Car SYSC slave device is part of the
> CPG/MSTP or CPG/MSSR Clock Domain and to be used as a wakeup source, it
> must be kept active during system suspend.
>
> Currently this is handled in device-specific drivers by explicitly
> increasing the use count of the module clock when the device is
> configured as a wakeup source. However, the proper way to prevent the
> device from being stopped is to inform this requirement to the genpd
> core, by setting the GENPD_FLAG_ACTIVE_WAKEUP flag.
>
> Note that this will only affect devices configured as wakeup sources."
Merged, thanks.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC Updates for v4.16
Date: Thu, 4 Jan 2018 22:52:22 -0800 [thread overview]
Message-ID: <20180105065222.zwpoyylkdjgl2rog@localhost> (raw)
In-Reply-To: <cover.1513936182.git.horms+renesas@verge.net.au>
On Fri, Dec 22, 2017 at 11:30:37AM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these second round of Renesas ARM based SoC updates for v4.16.
>
> This pull request is based on the previous round of
> such requests, tagged as renesas-soc-for-v4.16,
> which I have already sent a pull-request for.
>
>
> The following changes since commit 90f0d2b344313a8a4c366ef60d0df33008d2be84:
>
> soc: renesas: Identify R-Car M3-W ES1.1 (2017-11-27 11:40:57 +0100)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-soc2-for-v4.16
>
> for you to fetch changes up to 91c719f5ec6671f7b63762d78897af5583dd7693:
>
> soc: renesas: rcar-sysc: Keep wakeup sources active during system suspend (2017-12-20 11:16:05 +0100)
>
> ----------------------------------------------------------------
> Second Round of Renesas ARM Based SoC Updates for v4.16
>
> * rcar-sysc: Keep wakeup sources active during system suspend
>
> Geert Uytterhoeven says "If an R-Car SYSC slave device is part of the
> CPG/MSTP or CPG/MSSR Clock Domain and to be used as a wakeup source, it
> must be kept active during system suspend.
>
> Currently this is handled in device-specific drivers by explicitly
> increasing the use count of the module clock when the device is
> configured as a wakeup source. However, the proper way to prevent the
> device from being stopped is to inform this requirement to the genpd
> core, by setting the GENPD_FLAG_ACTIVE_WAKEUP flag.
>
> Note that this will only affect devices configured as wakeup sources."
Merged, thanks.
-Olof
next prev parent reply other threads:[~2018-01-05 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 10:30 [GIT PULL] Second Round of Renesas ARM Based SoC Updates for v4.16 Simon Horman
2017-12-22 10:30 ` Simon Horman
2017-12-22 10:30 ` [PATCH 1/1] soc: renesas: rcar-sysc: Keep wakeup sources active during system suspend Simon Horman
2017-12-22 10:30 ` Simon Horman
2018-01-05 6:52 ` Olof Johansson [this message]
2018-01-05 6:52 ` [GIT PULL] Second Round of Renesas ARM Based SoC Updates for v4.16 Olof Johansson
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=20180105065222.zwpoyylkdjgl2rog@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=horms+renesas@verge.net.au \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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.