[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YwI6n+PkFZZV/FW6@kroah.com>
Date: Sun, 21 Aug 2022 16:01:03 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Vimal Kumar <vimal.kumar32@...il.com>
Cc: chinmoyghosh2001@...il.com, Mintu Patel <mintupatel89@...il.com>,
Vishal Badole <badolevishal1116@...il.com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Pavel Machek <pavel@....cz>, Len Brown <len.brown@...el.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] PM: runtime: Add support to disable wakeup sources
On Sun, Aug 21, 2022 at 07:15:32PM +0530, Vimal Kumar wrote:
> User could find many wakeup sources available in the bsp, which
> they won't be using. Currently users can only get the status and
> list of enabled wakeup sources, but users can't disable it runtime.
> It's very difficult to find the driver for each wakeup sources from
> where it's getting enabled and make the changes for disabling it.
>
> This will help users to disable any wakeup sources at runtime,
> avoiding any code change and re-compilation. A new class attribute
> "disable_ws" will be added in the wakeup calss. If user want to disable
> any wakeup sources, user need to find the wakeup dev node associated
> with the particular wakeup source and write the devnode name to the
> class attribute "disable_ws".
>
> Example:
> Need to disable the wakeup source '1c08000.qcom,pcie'. The dev node
> associated with this wakeup source is:
> cat /sys/class/wakeup3/name ==> "1c08000.qcom,pcie", then for disabling
> this wakeup source :
> echo wakeup3 > /sys/class/wakeup/disable_ws
>
> Co-developed-by: Mintu Patel <mintupatel89@...il.com>
> Signed-off-by: Mintu Patel <mintupatel89@...il.com>
> Co-developed-by: Vishal Badole <badolevishal1116@...il.com>
> Signed-off-by: Vishal Badole <badolevishal1116@...il.com>
> Signed-off-by: Vimal Kumar <vimal.kumar32@...il.com>
That's a lot of gmail accounts, no "company" accounts? :)
> ---
> drivers/base/power/wakeup_stats.c | 63 ++++++++++++++++++++++++++++++-
You need a Documentation/ABI/ entry for any new sysfs file so we can
properly review this and support it over time.
thanks,
greg k-h
Powered by blists - more mailing lists