From: "José Expósito" <jose.exposito89@gmail.com>
To: jikos@kernel.org
Cc: benjamin.tissoires@redhat.com, rydberg@bitmath.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"José Expósito" <jose.exposito89@gmail.com>
Subject: [PATCH RESEND 0/1] HID: input: map battery system charging
Date: Thu, 24 Nov 2022 18:59:36 +0100 [thread overview]
Message-ID: <20221124175937.7631-1-jose.exposito89@gmail.com> (raw)
Hi everyone,
This patch adds support for reporting battery status (charging/discharging)
for devices with a charging usage in their HID descriptor:
0x05, 0x85, /* Usage Page (Battery System), */
0x09, 0x44, /* Usage Page (Charging), */
I tested it on Apple hardware (mouse, trackpad and keyboard) as well as
on UCLogic tablets with battery [1].
On other hardware (HID_DC_BATTERYSTRENGTH or digitizers with battery)
discharging should be reported for backwards compatibility.
I did my best to keep the old behaviour by adding KUnit tests; However,
I don't own any of those devices, so I'd appreciate any help testing
the patch from someone with the actual hardware.
Best wishes,
José Expósito
[1] https://lore.kernel.org/linux-input/20221029161240.15548-2-jose.exposito89@gmail.com/
José Expósito (1):
HID: input: map battery system charging
drivers/hid/.kunitconfig | 1 +
drivers/hid/Kconfig | 1 +
drivers/hid/hid-input-test.c | 80 ++++++++++++++++++++++++++++++++++++
drivers/hid/hid-input.c | 36 +++++++++++++++-
include/linux/hid.h | 2 +
5 files changed, 118 insertions(+), 2 deletions(-)
create mode 100644 drivers/hid/hid-input-test.c
--
2.38.1
next reply other threads:[~2022-11-24 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 17:59 José Expósito [this message]
2022-11-24 17:59 ` [PATCH RESEND 1/1] HID: input: map battery system charging José Expósito
2022-12-20 14:31 ` [PATCH RESEND 0/1] " Jiri Kosina
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=20221124175937.7631-1-jose.exposito89@gmail.com \
--to=jose.exposito89@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@bitmath.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;
as well as URLs for NNTP newsgroup(s).