From: Michael Walle <michael@walle.cc>
To: Catalin Marinas <catalin.marinas@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Michael Walle <michael@walle.cc>
Subject: [PATCH 0/2] arm64: remove generic ARM cpuidle support
Date: Sun, 29 May 2022 20:13:27 +0200 [thread overview]
Message-ID: <20220529181329.2345722-1-michael@walle.cc> (raw)
Playing with an own PSCI implementation, I've noticed that the cpuidle-arm
driver doesn't work on arm64. It doesn't probe because since commit
788961462f34 ("ARM: psci: cpuidle: Enable PSCI CPUidle driver") the
arm_cpuidle_init() can only return -EOPNOTSUPP, because the commit removed
the cpu_idle_init and cpu_suspend ops.
It left me puzzled for quite some time. It seems that the cpuidle-psci is
the preferred one and this has been the case for quite some time. The
mentioned commit first appeared in v5.4.
Remove the ARM64 support for the cpuidle-arm driver, which then let us
remove all the supporting arch code.
Michael Walle (2):
cpuidle: cpuidle-arm: remove arm64 support
arm64: cpuidle: remove generic cpuidle support
arch/arm64/include/asm/cpu_ops.h | 9 ---------
arch/arm64/include/asm/cpuidle.h | 15 ---------------
arch/arm64/kernel/cpuidle.c | 29 -----------------------------
drivers/cpuidle/Kconfig.arm | 3 ++-
4 files changed, 2 insertions(+), 54 deletions(-)
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-05-29 18:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 18:13 Michael Walle [this message]
2022-05-29 18:13 ` [PATCH 1/2] cpuidle: cpuidle-arm: remove arm64 support Michael Walle
2022-05-30 14:32 ` Sudeep Holla
2022-05-29 18:13 ` [PATCH 2/2] arm64: cpuidle: remove generic cpuidle support Michael Walle
2022-05-30 14:33 ` Sudeep Holla
2022-05-30 15:37 ` [PATCH 0/2] arm64: remove generic ARM " Daniel Lezcano
2022-06-22 11:59 ` Michael Walle
2022-06-22 14:07 ` Sudeep Holla
2022-06-23 13:19 ` Will Deacon
2022-06-23 19:31 ` Will Deacon
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=20220529181329.2345722-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.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).