From: Sudeep Holla <sudeep.holla@arm.com>
To: Michael Walle <michael@walle.cc>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: remove generic ARM cpuidle support
Date: Wed, 22 Jun 2022 15:07:48 +0100 [thread overview]
Message-ID: <20220622140748.laklytigxtfdbbg2@bogus> (raw)
In-Reply-To: <09f392794c815cbfb38e5103d92310da@walle.cc>
On Wed, Jun 22, 2022 at 01:59:07PM +0200, Michael Walle wrote:
> Am 2022-05-29 20:13, schrieb Michael Walle:
> > 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(-)
>
> Through which tree should this patchset go? I've seen it is marked as
> "Handled Elsewere" in the linux pm patchwork [1].
>
Generally based on the changes, it is decided. I can see why Rafael would
have marked so in PM patchwork. Daniel has already acked small change in
CPUidle config file while the bulk is removal of arm64 code. So, it is
better to route it via arm64 tree.
Will,
Assuming you will handle v5.20, can you pick this up ?
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-22 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 18:13 [PATCH 0/2] arm64: remove generic ARM cpuidle support Michael Walle
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 [this message]
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=20220622140748.laklytigxtfdbbg2@bogus \
--to=sudeep.holla@arm.com \
--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=lpieralisi@kernel.org \
--cc=michael@walle.cc \
--cc=rafael@kernel.org \
--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