From: Sudeep Holla <sudeep.holla@arm.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: <cristian.marussi@arm.com>, <ulf.hansson@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>, <arm-scmi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<ranjani.vaidyanathan@nxp.com>, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] pmdomain: arm: scmi_pm_domain: Initialize state as off
Date: Mon, 13 Jan 2025 10:31:21 +0000 [thread overview]
Message-ID: <Z4TreQ5bA9qiMTgC@bogus> (raw)
In-Reply-To: <20250110061346.2440772-1-peng.fan@oss.nxp.com>
On Fri, Jan 10, 2025 at 02:13:46PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Per ARM SCMI Spec DEN0056E, page 16, "The platform may disable a resource
> if no agent has requested to use that resource."
>
True, but ...
> Linux Kernel should not rely on a state that it has not requested, so
> make state as off during initialization.
>
IIUC, this was done to avoid any transitions if the bootloader like U-Boot
has turned on the resource and OS can just rely on that stay. Anyways if
the resource is not used by any driver/device in the kernel, won't it be
turned off anyways ? What am I missing ?
I need to dig details, but I remember doing what this patch does and
reverting to what we have based on the feedback IIRC.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-01-13 10:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 6:13 [PATCH] pmdomain: arm: scmi_pm_domain: Initialize state as off Peng Fan (OSS)
2025-01-13 10:31 ` Sudeep Holla [this message]
2025-01-13 11:37 ` Peng Fan
2025-01-13 13:49 ` Sudeep Holla
2025-01-13 15:30 ` [EXT] " Ranjani Vaidyanathan
2025-01-13 17:20 ` Sudeep Holla
2025-01-13 17:54 ` Cristian Marussi
2025-01-13 19:40 ` Ranjani Vaidyanathan
2025-01-13 19:54 ` Ranjani Vaidyanathan
2025-01-14 15:24 ` Sudeep Holla
2025-01-14 16:09 ` Ranjani Vaidyanathan
2025-01-14 18:16 ` Sudeep Holla
2025-01-15 9:15 ` Cristian Marussi
2025-01-15 18:42 ` Ranjani Vaidyanathan
2025-01-16 16:18 ` Cristian Marussi
2025-01-17 1:22 ` Peng Fan
2025-01-17 5:13 ` Dan Carpenter
2025-01-13 19:33 ` Cristian Marussi
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=Z4TreQ5bA9qiMTgC@bogus \
--to=sudeep.holla@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=ranjani.vaidyanathan@nxp.com \
--cc=ulf.hansson@linaro.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).