From: Luke Jones <luke@ljones.dev>
To: "Barnabás Pőcze" <pobrn@protonmail.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net, hdegoede@redhat.com,
corentin.chary@gmail.com, markgross@kernel.org,
jdelvare@suse.com, linux@roeck-us.net
Subject: Re: [PATCH] platform/x86: asus-wmi: add support for ASUS screenpad
Date: Fri, 05 May 2023 16:36:10 +1200 [thread overview]
Message-ID: <AS46UR.T68QO79EHLHI3@ljones.dev> (raw)
In-Reply-To: <R0Q3UR.1AXX7YQ75CIN1@ljones.dev>
On Thu, May 4 2023 at 09:22:03 +1200, Luke Jones <luke@ljones.dev>
wrote:
>
>
> On Wed, May 3 2023 at 17:46:53 +0000, Barnabás Pőcze
> <pobrn@protonmail.com> wrote:
>> Hi
>>
>>
>> 2023. május 3., szerda 6:02 keltezéssel, Luke D. Jones
>> \x7f<luke@ljones.dev> írta:
>>
>>> Add support for the WMI methods used to turn off and adjust the
>>> brightness of the secondary "screenpad" device found on some
>>> \x7f\x7fhigh-end
>>> ASUS laptops like the GX650P series and others.
>>
>> Is it this one: https://www.asus.com/content/rog-screenpad-plus/ ?
>> Or is the "plus" version something different?
>>
>> If it's a "proper" screen, wouldn't it be better to add support for
>> it
>> in the respective subsystems? E.g. why not register a backlight
>> \x7fdevice?
>
> I think it is similar yes, likely the same thing.
>
> Adding as a proper backlight is what I wanted to do but at first
> blush I wasn't sure.
>
> Looking at include/linux/backlight.h + some examples it looks clear
> now. I'll try to
> work up a revised patch and get it tested by the folks with the
> actual laptop.
>
> My only possible issue would be how to handle the on/off part?
>
> Cheers,
> Luke.
This has now been addressed with "[PATCH v2 0/1] platform/x86:
asus-wmi: add support for ASUS screenpad" at
https://lkml.org/lkml/2023/5/5/9
next prev parent reply other threads:[~2023-05-05 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 4:02 [PATCH] platform/x86: asus-wmi: add support for ASUS screenpad Luke D. Jones
2023-05-03 17:46 ` Barnabás Pőcze
2023-05-03 21:22 ` Luke Jones
2023-05-05 4:36 ` Luke Jones [this message]
2023-05-04 12:19 ` kernel test robot
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=AS46UR.T68QO79EHLHI3@ljones.dev \
--to=luke@ljones.dev \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.com \
/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