From: Sudeep Holla <sudeep.holla@arm.com>
To: Samuel Holland <samuel@sholland.org>
Cc: Palmer Dabbelt <palmer@rivosinc.com>,
conor.dooley@microchip.com, apatel@ventanamicro.com,
anup@brainfault.org, Sudeep Holla <sudeep.holla@arm.com>,
Conor Dooley <conor@kernel.org>,
rafael@kernel.org, daniel.lezcano@linaro.org,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-pm@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux@rivosinc.com
Subject: Re: [PATCH] cpuidle: riscv-sbi: Stop using non-retentive suspend
Date: Wed, 23 Nov 2022 10:20:07 +0000 [thread overview]
Message-ID: <20221123102007.2hrncka2nnpxp75h@bogus> (raw)
In-Reply-To: <57114829-c205-dece-abdb-1100947286d4@sholland.org>
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
next prev parent reply other threads:[~2022-11-23 10:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 20:56 [PATCH] cpuidle: riscv-sbi: Stop using non-retentive suspend Palmer Dabbelt
2022-11-21 21:10 ` Conor Dooley
2022-11-22 0:45 ` Samuel Holland
2022-11-22 11:06 ` Conor Dooley
2022-11-23 3:42 ` Samuel Holland
2022-11-23 10:46 ` Conor Dooley
2022-11-22 3:45 ` Anup Patel
2022-11-22 5:16 ` Palmer Dabbelt
2022-11-22 5:36 ` Anup Patel
2022-11-22 11:19 ` Conor Dooley
2022-11-22 15:28 ` Palmer Dabbelt
2022-11-23 4:38 ` Anup Patel
2022-11-23 5:11 ` Samuel Holland
2022-11-23 5:35 ` Anup Patel
2022-11-23 5:38 ` Samuel Holland
2022-11-23 6:10 ` Anup Patel
2022-11-23 6:27 ` Samuel Holland
2022-11-23 6:41 ` Anup Patel
2022-11-23 6:49 ` Samuel Holland
2022-11-23 7:13 ` Anup Patel
2022-11-23 10:20 ` Sudeep Holla [this message]
2022-11-23 4:26 ` Anup Patel
2022-11-23 10:09 ` Conor Dooley
2022-11-23 10:36 ` Anup Patel
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=20221123102007.2hrncka2nnpxp75h@bogus \
--to=sudeep.holla@arm.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rivosinc.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=rafael@kernel.org \
--cc=samuel@sholland.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