All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: linux-pm@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	luke@ljones.dev, me@kylegospodneti.ch
Subject: Re: [PATCH v1 1/4] acpi/x86: s2idle: add support for screen off and screen on callbacks
Date: Thu, 19 Sep 2024 15:17:31 -0500	[thread overview]
Message-ID: <5ecb2665-a14d-4f93-9699-f82f93dea65d@amd.com> (raw)
In-Reply-To: <CAGwozwEquttfbzat4ZQbQ3h_7Gi2QZ7qDBr=QgaZBU0MejEQ6Q@mail.gmail.com>

On 9/19/2024 12:36, Antheas Kapenekakis wrote:
> As stated in the cover letter, I would like to add you as a co-author.
> Just did not (could not?) do it before asking.
> 
> I will do it on the next revision. Just tell me which patches you think
> it should be on.

Patch 1 and 3.

Thanks,

> 
> (hit reply instead of reply all by mistake, so you have this email twice now)
> 
> Best,
> Antheas
> 
> On Thu, 19 Sept 2024 at 19:29, Mario Limonciello
> <mario.limonciello@amd.com> wrote:
>>
>> On 9/19/2024 12:19, Antheas Kapenekakis wrote:
>>> The screen off and screen on firmware functions are meant to signify
>>> the system entering a state where the user is not actively interacting
>>> with it (i.e., in Windows this state is called "Screen Off" and the
>>> system enters it once it turns the screen off e.g., due to inactivity).
>>>
>>> In this state, the kernel and userspace are fully active, and the user
>>> might still be interacting with the system somehow (such as with
>>> listening to music or having a hotspot). Userspace is supposed to
>>> minimize non-essential activities, but this is not required.
>>> In addition, there is no requirement of suspending post the screen off
>>> call. If the user interacts with the system, the kernel should call
>>> screen on and resume normal operation.
>>>
>>> This patch adds a set of callbacks to allow calling the screen on/off
>>> callbacks outside of the suspend/resume path. It is based on
>>> Mario Limonciello's patch on the superm1/dsm-screen-on-off branch.
>>
>> Based on?  It's nearly an identical patch [1].  The screen_off/screen_on
>> lines in struct platform_s2idle_ops are just placed in a different location.
>>
>> IMO there should be more attribution here, either a Co-developed-by tag
>> or sending my patch directly and adding your S-o-b to it.
>>
>> Link:
>> https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git/commit/?h=superm1/dsm-screen-on-off&id=7b80581428315f973410dccf0402a86266fb0d9a
>> [1]
>>
>>> However, the intent here is completely different.
>>>
>>> Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
>>> ---
>>>    include/linux/suspend.h |  5 +++++
>>>    kernel/power/suspend.c  | 12 ++++++++++++
>>>    2 files changed, 17 insertions(+)
>>>
>>> diff --git a/include/linux/suspend.h b/include/linux/suspend.h
>>> index da6ebca3ff77..96ceaad07839 100644
>>> --- a/include/linux/suspend.h
>>> +++ b/include/linux/suspend.h
>>> @@ -132,6 +132,7 @@ struct platform_suspend_ops {
>>>    };
>>>
>>>    struct platform_s2idle_ops {
>>> +     int (*screen_off)(void);
>>>        int (*begin)(void);
>>>        int (*prepare)(void);
>>>        int (*prepare_late)(void);
>>> @@ -140,6 +141,7 @@ struct platform_s2idle_ops {
>>>        void (*restore_early)(void);
>>>        void (*restore)(void);
>>>        void (*end)(void);
>>> +     int (*screen_on)(void);
>>>    };
>>>
>>>    #ifdef CONFIG_SUSPEND
>>> @@ -160,6 +162,9 @@ extern unsigned int pm_suspend_global_flags;
>>>    #define PM_SUSPEND_FLAG_FW_RESUME   BIT(1)
>>>    #define PM_SUSPEND_FLAG_NO_PLATFORM BIT(2)
>>>
>>> +int platform_suspend_screen_off(void);
>>> +int platform_suspend_screen_on(void);
>>> +
>>>    static inline void pm_suspend_clear_flags(void)
>>>    {
>>>        pm_suspend_global_flags = 0;
>>> diff --git a/kernel/power/suspend.c b/kernel/power/suspend.c
>>> index 09f8397bae15..19734b297527 100644
>>> --- a/kernel/power/suspend.c
>>> +++ b/kernel/power/suspend.c
>>> @@ -254,6 +254,18 @@ static bool sleep_state_supported(suspend_state_t state)
>>>               (valid_state(state) && !cxl_mem_active());
>>>    }
>>>
>>> +int platform_suspend_screen_off(void)
>>> +{
>>> +     return s2idle_ops && s2idle_ops->screen_off ? s2idle_ops->screen_off() : 0;
>>> +}
>>> +EXPORT_SYMBOL_GPL(platform_suspend_screen_off);
>>> +
>>> +int platform_suspend_screen_on(void)
>>> +{
>>> +     return s2idle_ops && s2idle_ops->screen_on ? s2idle_ops->screen_on() : 0;
>>> +}
>>> +EXPORT_SYMBOL_GPL(platform_suspend_screen_on);
>>> +
>>>    static int platform_suspend_prepare(suspend_state_t state)
>>>    {
>>>        return state != PM_SUSPEND_TO_IDLE && suspend_ops->prepare ?
>>


  reply	other threads:[~2024-09-19 20:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 17:19 [PATCH v1 0/4] acpi/x86: s2idle: move Display off/on calls outside suspend (fixes ROG Ally suspend) Antheas Kapenekakis
2024-09-19 17:19 ` [PATCH v1 1/4] acpi/x86: s2idle: add support for screen off and screen on callbacks Antheas Kapenekakis
2024-09-19 17:29   ` Mario Limonciello
2024-09-19 17:36     ` Antheas Kapenekakis
2024-09-19 20:17       ` Mario Limonciello [this message]
2024-09-19 17:19 ` [PATCH v1 2/4] acpi/x86: s2idle: handle screen off/on calls outside of suspend sequence Antheas Kapenekakis
2024-09-19 17:35   ` Mario Limonciello
2024-09-19 18:21     ` Alex Deucher
2024-09-19 18:32       ` Mario Limonciello
2024-09-19 18:35         ` Antheas Kapenekakis
2024-09-19 17:19 ` [PATCH v1 3/4] acpi/x86: s2idle: call screen on and off as part of callbacks Antheas Kapenekakis
2024-09-19 19:01   ` Mario Limonciello
2024-09-19 20:45     ` Antheas Kapenekakis
2024-09-19 20:51       ` Mario Limonciello
2024-09-19 20:54         ` Antheas Kapenekakis
2024-09-21  1:03           ` Denis Benato
2024-09-21  6:22             ` Antheas Kapenekakis
2024-09-21 14:47               ` Denis Benato
2024-09-21 19:44                 ` Antheas Kapenekakis
2024-09-22  2:07                   ` Denis Benato
2024-09-22  7:48                     ` Antheas Kapenekakis
2024-09-19 17:19 ` [PATCH v1 4/4] platform/x86: asus-wmi: remove Ally (1st gen) and Ally X suspend quirk Antheas Kapenekakis
2024-09-19 18:36   ` Mario Limonciello

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=5ecb2665-a14d-4f93-9699-f82f93dea65d@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=lkml@antheas.dev \
    --cc=luke@ljones.dev \
    --cc=me@kylegospodneti.ch \
    --cc=platform-driver-x86@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.