[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190927125912.GB8704@bogus>
Date: Fri, 27 Sep 2019 13:59:12 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Benjamin GAIGNARD <benjamin.gaignard@...com>
Cc: Marc Zyngier <maz@...nel.org>,
Alexandre TORGUE <alexandre.torgue@...com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-stm32@...md-mailman.stormreply.com"
<linux-stm32@...md-mailman.stormreply.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: dts: stm32: Enable high resolution timer
On Fri, Sep 27, 2019 at 12:44:55PM +0000, Benjamin GAIGNARD wrote:
[...]
>
> Even in low-power modes this timer is always powered and clocked so it
> is working fine.
>
Is that tested ? I see only cpu_{on,off} available on this platform with
PSCI v0.1. Did you add cpu_suspend, idle-states and then gave it a spin ?
Or do you have some other idle driver with which this is tested ?
Also I don't understand how "always-on" is linked to hrtimer. Always on
timers are just selected to be broadcast timer without sacrificing(simply
keeping) a cpu to be always active for broadcast purposes.
--
Regards,
Sudeep
Powered by blists - more mailing lists