From: Maximilian Luz <luzmaximilian@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mark Gross <markgross@kernel.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Maximilian Luz <luzmaximilian@gmail.com>
Subject: [PATCH 0/3] platform/surface: aggregator_registry: Rename and add more HID device nodes
Date: Wed, 10 Aug 2022 16:41:14 +0200 [thread overview]
Message-ID: <20220810144117.493710-1-luzmaximilian@gmail.com> (raw)
This series is twofold:
Patch 1 and 2 rename existing HID firmware nodes to better reflect the
devices they represent and the hierarchy they are placed under. In
particular, the three previously unknown nodes are for sensors, firmware
updates via the CFU mechanism, and for a USB Type-C Connector System
Software Interface (UCSI) HID client.
Patch 3 adds support for sensors and the UCSI client to the Surface Pro
8 by adding the missing SAM-connected HID nodes.
Regards,
Max
Maximilian Luz (3):
platform/surface: aggregator_registry: Rename HID device nodes based
on their function
platform/surface: aggregator_registry: Rename HID device nodes based
on new findings
platform/surface: aggregator_registry: Add HID devices for sensors and
UCSI client to SP8
.../surface/surface_aggregator_registry.c | 44 ++++++++++---------
1 file changed, 23 insertions(+), 21 deletions(-)
--
2.37.1
next reply other threads:[~2022-08-10 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 14:41 Maximilian Luz [this message]
2022-08-10 14:41 ` [PATCH 1/3] platform/surface: aggregator_registry: Rename HID device nodes based on their function Maximilian Luz
2022-08-10 14:41 ` [PATCH 2/3] platform/surface: aggregator_registry: Rename HID device nodes based on new findings Maximilian Luz
2022-08-10 14:41 ` [PATCH 3/3] platform/surface: aggregator_registry: Add HID devices for sensors and UCSI client to SP8 Maximilian Luz
2022-08-15 13:03 ` [PATCH 0/3] platform/surface: aggregator_registry: Rename and add more HID device nodes Hans de Goede
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=20220810144117.493710-1-luzmaximilian@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--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 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®