* [PATCH V2] firmware: arm_scmi: power_control: support suspend command
@ 2024-04-28 7:51 Peng Fan (OSS)
2024-05-01 13:36 ` Cristian Marussi
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Peng Fan (OSS) @ 2024-04-28 7:51 UTC (permalink / raw)
To: sudeep.holla, cristian.marussi; +Cc: linux-arm-kernel, linux-kernel, Peng Fan
From: Peng Fan <peng.fan@nxp.com>
Support System suspend notification. Using a work struct to call
pm_suspend. There is no way to pass suspend level to pm_suspend,
so use MEM as of now.
- The choice of S2R(MEM) by default. The userspace can configure whatever
default behaviour expected as S2R, if issuing suspend from userspace.
- The userspace needs to keep the wakeup source enabled, otherwise the
system may never resume back.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
V2:
Update commit log
Add comment for suspend_work
.../firmware/arm_scmi/scmi_power_control.c | 21 ++++++++++++++++++-
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/drivers/firmware/arm_scmi/scmi_power_control.c b/drivers/firmware/arm_scmi/scmi_power_control.c
index 6eb7d2a4b6b1..21f467a92942 100644
--- a/drivers/firmware/arm_scmi/scmi_power_control.c
+++ b/drivers/firmware/arm_scmi/scmi_power_control.c
@@ -50,6 +50,7 @@
#include <linux/reboot.h>
#include <linux/scmi_protocol.h>
#include <linux/slab.h>
+#include <linux/suspend.h>
#include <linux/time64.h>
#include <linux/timer.h>
#include <linux/types.h>
@@ -78,6 +79,7 @@ enum scmi_syspower_state {
* @reboot_nb: A notifier_block optionally used to track reboot progress
* @forceful_work: A worker used to trigger a forceful transition once a
* graceful has timed out.
+ * @suspend_work: A worker used to trigger system suspend
*/
struct scmi_syspower_conf {
struct device *dev;
@@ -90,6 +92,7 @@ struct scmi_syspower_conf {
struct notifier_block reboot_nb;
struct delayed_work forceful_work;
+ struct work_struct suspend_work;
};
#define userspace_nb_to_sconf(x) \
@@ -249,6 +252,9 @@ static void scmi_request_graceful_transition(struct scmi_syspower_conf *sc,
case SCMI_SYSTEM_WARMRESET:
orderly_reboot();
break;
+ case SCMI_SYSTEM_SUSPEND:
+ schedule_work(&sc->suspend_work);
+ break;
default:
break;
}
@@ -277,7 +283,8 @@ static int scmi_userspace_notifier(struct notifier_block *nb,
struct scmi_system_power_state_notifier_report *er = data;
struct scmi_syspower_conf *sc = userspace_nb_to_sconf(nb);
- if (er->system_state >= SCMI_SYSTEM_POWERUP) {
+ if (er->system_state >= SCMI_SYSTEM_MAX ||
+ er->system_state == SCMI_SYSTEM_POWERUP) {
dev_err(sc->dev, "Ignoring unsupported system_state: 0x%X\n",
er->system_state);
return NOTIFY_DONE;
@@ -315,6 +322,16 @@ static int scmi_userspace_notifier(struct notifier_block *nb,
return NOTIFY_OK;
}
+static void scmi_suspend_work_func(struct work_struct *work)
+{
+ struct scmi_syspower_conf *sc =
+ container_of(work, struct scmi_syspower_conf, suspend_work);
+
+ pm_suspend(PM_SUSPEND_MEM);
+
+ sc->state = SCMI_SYSPOWER_IDLE;
+}
+
static int scmi_syspower_probe(struct scmi_device *sdev)
{
int ret;
@@ -338,6 +355,8 @@ static int scmi_syspower_probe(struct scmi_device *sdev)
sc->userspace_nb.notifier_call = &scmi_userspace_notifier;
sc->dev = &sdev->dev;
+ INIT_WORK(&sc->suspend_work, scmi_suspend_work_func);
+
return handle->notify_ops->devm_event_notifier_register(sdev,
SCMI_PROTOCOL_SYSTEM,
SCMI_EVENT_SYSTEM_POWER_STATE_NOTIFIER,
--
2.37.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH V2] firmware: arm_scmi: power_control: support suspend command
2024-04-28 7:51 [PATCH V2] firmware: arm_scmi: power_control: support suspend command Peng Fan (OSS)
@ 2024-05-01 13:36 ` Cristian Marussi
2024-05-01 23:52 ` Peng Fan
2024-05-30 9:34 ` Peng Fan
2024-06-17 9:50 ` Sudeep Holla
2 siblings, 1 reply; 5+ messages in thread
From: Cristian Marussi @ 2024-05-01 13:36 UTC (permalink / raw)
To: Peng Fan (OSS); +Cc: sudeep.holla, linux-arm-kernel, linux-kernel, Peng Fan
On Sun, Apr 28, 2024 at 03:51:05PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Support System suspend notification. Using a work struct to call
> pm_suspend. There is no way to pass suspend level to pm_suspend,
> so use MEM as of now.
>
> - The choice of S2R(MEM) by default. The userspace can configure whatever
> default behaviour expected as S2R, if issuing suspend from userspace.
>
> - The userspace needs to keep the wakeup source enabled, otherwise the
> system may never resume back.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
Have you tried triggering a suspend with this on your setup ?
Anyway, LGTM.
Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
Thanks,
Cristian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [PATCH V2] firmware: arm_scmi: power_control: support suspend command
2024-05-01 13:36 ` Cristian Marussi
@ 2024-05-01 23:52 ` Peng Fan
0 siblings, 0 replies; 5+ messages in thread
From: Peng Fan @ 2024-05-01 23:52 UTC (permalink / raw)
To: Cristian Marussi, Peng Fan (OSS)
Cc: sudeep.holla@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
> Subject: Re: [PATCH V2] firmware: arm_scmi: power_control: support
> suspend command
>
> On Sun, Apr 28, 2024 at 03:51:05PM +0800, Peng Fan (OSS) wrote:
> > From: Peng Fan <peng.fan@nxp.com>
> >
> > Support System suspend notification. Using a work struct to call
> > pm_suspend. There is no way to pass suspend level to pm_suspend, so
> > use MEM as of now.
> >
> > - The choice of S2R(MEM) by default. The userspace can configure whatever
> > default behaviour expected as S2R, if issuing suspend from userspace.
> >
> > - The userspace needs to keep the wakeup source enabled, otherwise the
> > system may never resume back.
> >
> > Signed-off-by: Peng Fan <peng.fan@nxp.com>
> > ---
>
> Have you tried triggering a suspend with this on your setup ?
Yes, this feature is already in NXP internal git tree and tested.
>
> Anyway, LGTM.
> Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
>
Thanks,
Peng.
> Thanks,
> Cristian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [PATCH V2] firmware: arm_scmi: power_control: support suspend command
2024-04-28 7:51 [PATCH V2] firmware: arm_scmi: power_control: support suspend command Peng Fan (OSS)
2024-05-01 13:36 ` Cristian Marussi
@ 2024-05-30 9:34 ` Peng Fan
2024-06-17 9:50 ` Sudeep Holla
2 siblings, 0 replies; 5+ messages in thread
From: Peng Fan @ 2024-05-30 9:34 UTC (permalink / raw)
To: Peng Fan (OSS), sudeep.holla@arm.com, cristian.marussi@arm.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Hi Sudeep,
> Subject: [PATCH V2] firmware: arm_scmi: power_control: support suspend
> command
Is this patch good for you to pick up?
Thanks,
Peng.
>
> From: Peng Fan <peng.fan@nxp.com>
>
> Support System suspend notification. Using a work struct to call pm_suspend.
> There is no way to pass suspend level to pm_suspend, so use MEM as of now.
>
> - The choice of S2R(MEM) by default. The userspace can configure whatever
> default behaviour expected as S2R, if issuing suspend from userspace.
>
> - The userspace needs to keep the wakeup source enabled, otherwise the
> system may never resume back.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>
> V2:
> Update commit log
> Add comment for suspend_work
>
> .../firmware/arm_scmi/scmi_power_control.c | 21 ++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/arm_scmi/scmi_power_control.c
> b/drivers/firmware/arm_scmi/scmi_power_control.c
> index 6eb7d2a4b6b1..21f467a92942 100644
> --- a/drivers/firmware/arm_scmi/scmi_power_control.c
> +++ b/drivers/firmware/arm_scmi/scmi_power_control.c
> @@ -50,6 +50,7 @@
> #include <linux/reboot.h>
> #include <linux/scmi_protocol.h>
> #include <linux/slab.h>
> +#include <linux/suspend.h>
> #include <linux/time64.h>
> #include <linux/timer.h>
> #include <linux/types.h>
> @@ -78,6 +79,7 @@ enum scmi_syspower_state {
> * @reboot_nb: A notifier_block optionally used to track reboot progress
> * @forceful_work: A worker used to trigger a forceful transition once a
> * graceful has timed out.
> + * @suspend_work: A worker used to trigger system suspend
> */
> struct scmi_syspower_conf {
> struct device *dev;
> @@ -90,6 +92,7 @@ struct scmi_syspower_conf {
> struct notifier_block reboot_nb;
>
> struct delayed_work forceful_work;
> + struct work_struct suspend_work;
> };
>
> #define userspace_nb_to_sconf(x) \
> @@ -249,6 +252,9 @@ static void scmi_request_graceful_transition(struct
> scmi_syspower_conf *sc,
> case SCMI_SYSTEM_WARMRESET:
> orderly_reboot();
> break;
> + case SCMI_SYSTEM_SUSPEND:
> + schedule_work(&sc->suspend_work);
> + break;
> default:
> break;
> }
> @@ -277,7 +283,8 @@ static int scmi_userspace_notifier(struct
> notifier_block *nb,
> struct scmi_system_power_state_notifier_report *er = data;
> struct scmi_syspower_conf *sc = userspace_nb_to_sconf(nb);
>
> - if (er->system_state >= SCMI_SYSTEM_POWERUP) {
> + if (er->system_state >= SCMI_SYSTEM_MAX ||
> + er->system_state == SCMI_SYSTEM_POWERUP) {
> dev_err(sc->dev, "Ignoring unsupported system_state:
> 0x%X\n",
> er->system_state);
> return NOTIFY_DONE;
> @@ -315,6 +322,16 @@ static int scmi_userspace_notifier(struct
> notifier_block *nb,
> return NOTIFY_OK;
> }
>
> +static void scmi_suspend_work_func(struct work_struct *work) {
> + struct scmi_syspower_conf *sc =
> + container_of(work, struct scmi_syspower_conf,
> suspend_work);
> +
> + pm_suspend(PM_SUSPEND_MEM);
> +
> + sc->state = SCMI_SYSPOWER_IDLE;
> +}
> +
> static int scmi_syspower_probe(struct scmi_device *sdev) {
> int ret;
> @@ -338,6 +355,8 @@ static int scmi_syspower_probe(struct scmi_device
> *sdev)
> sc->userspace_nb.notifier_call = &scmi_userspace_notifier;
> sc->dev = &sdev->dev;
>
> + INIT_WORK(&sc->suspend_work, scmi_suspend_work_func);
> +
> return handle->notify_ops->devm_event_notifier_register(sdev,
>
> SCMI_PROTOCOL_SYSTEM,
>
> SCMI_EVENT_SYSTEM_POWER_STATE_NOTIFIER,
> --
> 2.37.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH V2] firmware: arm_scmi: power_control: support suspend command
2024-04-28 7:51 [PATCH V2] firmware: arm_scmi: power_control: support suspend command Peng Fan (OSS)
2024-05-01 13:36 ` Cristian Marussi
2024-05-30 9:34 ` Peng Fan
@ 2024-06-17 9:50 ` Sudeep Holla
2 siblings, 0 replies; 5+ messages in thread
From: Sudeep Holla @ 2024-06-17 9:50 UTC (permalink / raw)
To: cristian.marussi, Peng Fan (OSS)
Cc: Sudeep Holla, linux-arm-kernel, linux-kernel, Peng Fan
On Sun, 28 Apr 2024 15:51:05 +0800, Peng Fan (OSS) wrote:
> Support System suspend notification. Using a work struct to call
> pm_suspend. There is no way to pass suspend level to pm_suspend,
> so use MEM as of now.
>
> - The choice of S2R(MEM) by default. The userspace can configure whatever
> default behaviour expected as S2R, if issuing suspend from userspace.
>
> [...]
Applied to sudeep.holla/linux (for-next/scmi/updates), thanks!
[1/1] firmware: arm_scmi: power_control: support suspend command
https://git.kernel.org/sudeep.holla/c/dd22cc907a74
--
Regards,
Sudeep
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-06-17 9:51 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-04-28 7:51 [PATCH V2] firmware: arm_scmi: power_control: support suspend command Peng Fan (OSS)
2024-05-01 13:36 ` Cristian Marussi
2024-05-01 23:52 ` Peng Fan
2024-05-30 9:34 ` Peng Fan
2024-06-17 9:50 ` Sudeep Holla
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).