From: Sudeep Holla <sudeep.holla@arm.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, vincent.guittot@linaro.org,
f.fainelli@gmail.com, Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 0/5] Introduce SCMI System Power Control driver
Date: Fri, 1 Jul 2022 14:49:20 +0100 [thread overview]
Message-ID: <20220701134920.3elmh4bww3s63trr@bogus> (raw)
In-Reply-To: <20220623124742.2492164-1-cristian.marussi@arm.com>
On Thu, Jun 23, 2022 at 01:47:37PM +0100, Cristian Marussi wrote:
> Hi,
>
> This series is a respin of an old series[0] parked for a while waiting for
> a required SCMI specification change to be published.
>
> The series, building on top of the SCMI System Power Protocol, adds a new
> SCMI driver which, registering for SystemPower notifications, takes care to
> satisfy SCMI plaform system-transitions graceful requests like shutdown or
> reboot involving userspace interactions as needed.
>
> Interaction with userspace boils down to the same orderly_ Kernel methods
> used by ACPI to handle similar shutdown requests.
>
> The latest SCMI v3.1 specification [1], which adds a new timeout field to
> the graceful notifications payload, let the platform advertise for how long
> it will possibly wait for the requested system state transition to happen
> before forcibly enforcing it.
>
> As a part of the series, patch 2/3 enforces, at the SCMI core level, the
> creation of one single SCMI SystemPower device, to avoid promoting the
> design of systems in which multiple SCMI platforms can advertise the
> concurrent support of SystemPower protocol: when multiple SCMI platform
> are defined, only one of them should be in charge of SystemPower comms
> with the OSPM, so only one such SystemPower device across all platforms
> is allowed to be created.
>
Other than the comment in 2/5, I am happy with the other changes.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-07-01 13:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 12:47 [PATCH 0/5] Introduce SCMI System Power Control driver Cristian Marussi
2022-06-23 12:47 ` [PATCH 1/5] firmware: arm_scmi: Remove deprecated ida_simple_ calls Cristian Marussi
2022-07-01 13:46 ` Sudeep Holla
2022-06-23 12:47 ` [PATCH 2/5] firmware: arm_scmi: Support only one single SystemPower device Cristian Marussi
2022-07-01 13:45 ` Sudeep Holla
2022-07-01 14:31 ` Cristian Marussi
2022-07-01 15:00 ` Sudeep Holla
2022-06-23 12:47 ` [PATCH 3/5] firmware: arm_scmi: Add SCMIv3.1 SystemPower extensions Cristian Marussi
2022-06-23 12:47 ` [PATCH 4/5] firmware: arm_scmi: Add devm_protocol_acquire helper Cristian Marussi
2022-06-23 12:47 ` [PATCH 5/5] firmware: arm_scmi: Add SCMI System Power Control driver Cristian Marussi
2022-06-27 13:54 ` Greg Kroah-Hartman
2022-07-01 13:49 ` Sudeep Holla [this message]
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=20220701134920.3elmh4bww3s63trr@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vincent.guittot@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