[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161123230725.c3euemhmfnm3qjtn@rob-hp-laptop>
Date: Wed, 23 Nov 2016 17:07:25 -0600
From: Rob Herring <robh@...nel.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: tglx@...utronix.de, linux-kernel@...r.kernel.org,
Brian Norris <briannorris@...omium.org>,
Marc Zyngier <marc.zyngier@....com>,
Mark Rutland <mark.rutland@....com>,
Will Deacon <will.deacon@....com>,
Douglas Anderson <dianders@...omium.org>,
Scott Wood <oss@...error.net>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"moderated list:ARM ARCHITECTED TIMER DRIVER"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/4] clocksource/drivers/arm_arch_timer: Don't assume
clock runs in suspend
On Tue, Nov 22, 2016 at 10:44:21AM +0100, Daniel Lezcano wrote:
> From: Brian Norris <briannorris@...omium.org>
>
> The ARM specifies that the system counter "must be implemented in an
> always-on power domain," and so we try to use the counter as a source of
> timekeeping across suspend/resume. Unfortunately, some SoCs (e.g.,
> Rockchip's RK3399) do not keep the counter ticking properly when
> switched from their high-power clock to the lower-power clock used in
> system suspend. Support this quirk by adding a new device tree property.
>
> Signed-off-by: Brian Norris <briannorris@...omium.org>
> Reviewed-by: Douglas Anderson <dianders@...omium.org>
> Acked-by: Marc Zyngier <marc.zyngier@....com>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@...aro.org>
> ---
> Documentation/devicetree/bindings/arm/arch_timer.txt | 5 +++++
Acked-by: Rob Herring <robh@...nel.org>
> drivers/clocksource/arm_arch_timer.c | 9 ++++++++-
> 2 files changed, 13 insertions(+), 1 deletion(-)
Powered by blists - more mailing lists