From: Werner Sembach <wse@tuxedocomputers.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <bentiss@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Disable touchpad on firmware level while not in use
Date: Thu, 24 Apr 2025 12:58:40 +0200 [thread overview]
Message-ID: <99d486e5-8836-4a83-ad05-8bc42d845cdd@tuxedocomputers.com> (raw)
In-Reply-To: <9q411092-1170-qr2r-27or-96594p19qrqo@xreary.bet>
Am 24.04.25 um 11:20 schrieb Jiri Kosina:
> On Tue, 4 Mar 2025, Werner Sembach wrote:
>
>>> Using the new on_hid_hw_open and on_hid_hw_close functions to disable the
>>> touchpad on firmware level while not being in use.
>>>
>>> This safes some battery and triggers touchpad-disabled-leds hardwired to
>>> the touchpads firmware, that exist for example on some TongFang barebones.
>>>
>>> For a lengthy discussion with all the details see
>>> https://gitlab.freedesktop.org/libinput/libinput/-/issues/558
>> Any comments if this is a good idea or not?
> Sorry for the delay.
np
>
> To me this looks like generally a good idea; Benjamin, any comments on the
> hid-mt part?
>
> BTW you'd need to adjust the Subject line of the patches to conform to the
> subsystem style (i.e. HID: core: ....)
sorry an oversight when rewriting the commit log from local testing branch to
upstream ready
will do in v2 after Benjamins reply
Thanks for looking at this,
Werner
>
> Thanks,
>
next prev parent reply other threads:[~2025-04-24 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 13:39 [PATCH 1/2] Add functions for HID drivers to react on first open and last close call Werner Sembach
2025-02-11 13:39 ` [PATCH 2/2] Disable touchpad on firmware level while not in use Werner Sembach
2025-03-04 12:14 ` Werner Sembach
2025-04-24 9:20 ` Jiri Kosina
2025-04-24 10:58 ` Werner Sembach [this message]
2025-05-13 16:39 ` Benjamin Tissoires
2025-05-13 16:36 ` [PATCH 1/2] Add functions for HID drivers to react on first open and last close call Benjamin Tissoires
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=99d486e5-8836-4a83-ad05-8bc42d845cdd@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®