[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221123102007.2hrncka2nnpxp75h@bogus>
Date: Wed, 23 Nov 2022 10:20:07 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Samuel Holland <samuel@...lland.org>
Cc: Palmer Dabbelt <palmer@...osinc.com>, conor.dooley@...rochip.com,
apatel@...tanamicro.com, anup@...infault.org,
Sudeep Holla <sudeep.holla@....com>,
Conor Dooley <conor@...nel.org>, rafael@...nel.org,
daniel.lezcano@...aro.org,
Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, linux-pm@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux@...osinc.com
Subject: Re: [PATCH] cpuidle: riscv-sbi: Stop using non-retentive suspend
On Tue, Nov 22, 2022 at 11:11:23PM -0600, Samuel Holland wrote:
[...]
> While the comment in include/linux/clockchips.h and the name of the flag
> imply that C3STOP is Intel-specific, it really isn't. The flag is used
> on ARM, MIPS, and PowerPC as well.
>
+1. I agree the name is confusing but it used to just indicate that the
timer is not always on and could stop in deeper CPU idle states. It probably
was introduced to be used on x86 for C3 state but it is used for other
purposes as well. May be one should have or even can now rename it to
something more appropriate, but I am sure it might trigger some bikeshedding
discussions 😉.
--
Regards,
Sudeep
Powered by blists - more mailing lists