From: Neil Armstrong <narmstrong@baylibre.com>
To: Kevin Hilman <khilman@kernel.org>, linux-amlogic@lists.infradead.org
Cc: Kevin Hilman <khilman@baylibre.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: amlogic: g12 CPU timers stop in suspend
Date: Mon, 12 Aug 2019 09:50:01 +0200 [thread overview]
Message-ID: <1392df2d-4dbb-e29e-bf82-711138a95bf4@baylibre.com> (raw)
In-Reply-To: <20190808170510.4141-1-khilman@kernel.org>
On 08/08/2019 19:05, Kevin Hilman wrote:
> From: Kevin Hilman <khilman@baylibre.com>
>
> The Arm per-CPU architected timers stop ticking in suspend, when the
> SCP powers down the CPUs. Flag that in the DT.
>
> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
> ---
> Applies on my v5.4/dt64 branch
>
> arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi b/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
> index 27bb242dc95d..cd3d23d2c6a2 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi
> @@ -2407,6 +2407,7 @@
> (GIC_CPU_MASK_RAW(0xff) | IRQ_TYPE_LEVEL_LOW)>,
> <GIC_PPI 10
> (GIC_CPU_MASK_RAW(0xff) | IRQ_TYPE_LEVEL_LOW)>;
> + arm,no-tick-in-suspend;
> };
>
> xtal: xtal-clk {
>
Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-08-12 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 17:05 [PATCH] arm64: dts: amlogic: g12 CPU timers stop in suspend Kevin Hilman
2019-08-12 7:50 ` Neil Armstrong [this message]
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=1392df2d-4dbb-e29e-bf82-711138a95bf4@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=khilman@baylibre.com \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.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 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).