From: Maximilian Luz <luzmaximilian@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: "Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Mark Gross" <mgross@linux.intel.com>,
"Blaž Hrastnik" <blaz@mxxn.io>,
linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] HID: Add support for Surface Aggregator Module HID transport
Date: Sat, 27 Mar 2021 21:49:54 +0100 [thread overview]
Message-ID: <a0e28af7-3451-83a5-ca16-e230ec70c518@gmail.com> (raw)
In-Reply-To: <20210310225329.2393372-1-luzmaximilian@gmail.com>
On 3/10/21 11:53 PM, Maximilian Luz wrote:
> This series adds support for the Surface System Aggregator Module (SSAM)
> HID transport subsystem.
>
> The SSAM is an embedded controller, found on 5th- and later generation
> Microsoft Surface devices. On some of these devices (specifically
> Surface Laptops 1, 2, and 3, as well as Surface Book 3), built-in input
> devices are connected via the SSAM. These devices communicate (mostly)
> via normal HID reports, so adding support for them is (mostly) just a
> matter of implementing an HID transport driver.
>
> SSAM actually has two different HID interfaces: One (legacy) interface
> used on Surface Laptops 1 and 2, and a newer interface for the rest. The
> newer interface allows for multiple HID devices to be addressed and is
> implemented in the first patch. The older interface only allows a single
> HID device to be connected and, furthermore, only allows a single output
> report, specifically one for the caps lock LED. This is implemented in
> the second patch.
>
> See the commit messages of the respective patches for more details.
>
> Regards,
> Max
>
> Note: This patch depends on the
>
> platform/surface: Add Surface Aggregator device registry
>
> series. More specifically patch
>
> platform/surface: Set up Surface Aggregator device registry
>
> The full series has been merged into the for-next branch of the
> platform-drivers-x86 tree [1]. The commit in question can be found at
> [2].
>
> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=for-next
> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next&id=fc622b3d36e6d91330fb21506b9ad1e3206a4dde
>
> Maximilian Luz (2):
> HID: Add support for Surface Aggregator Module HID transport
> HID: surface-hid: Add support for legacy keyboard interface
>
> MAINTAINERS | 7 +
> drivers/hid/Kconfig | 2 +
> drivers/hid/Makefile | 2 +
> drivers/hid/surface-hid/Kconfig | 42 +++
> drivers/hid/surface-hid/Makefile | 7 +
> drivers/hid/surface-hid/surface_hid.c | 253 +++++++++++++++++
> drivers/hid/surface-hid/surface_hid_core.c | 272 +++++++++++++++++++
> drivers/hid/surface-hid/surface_hid_core.h | 77 ++++++
> drivers/hid/surface-hid/surface_kbd.c | 300 +++++++++++++++++++++
> 9 files changed, 962 insertions(+)
> create mode 100644 drivers/hid/surface-hid/Kconfig
> create mode 100644 drivers/hid/surface-hid/Makefile
> create mode 100644 drivers/hid/surface-hid/surface_hid.c
> create mode 100644 drivers/hid/surface-hid/surface_hid_core.c
> create mode 100644 drivers/hid/surface-hid/surface_hid_core.h
> create mode 100644 drivers/hid/surface-hid/surface_kbd.c
>
Hi, is there any status update on this?
Regards,
Max
next prev parent reply other threads:[~2021-03-27 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 22:53 [PATCH 0/2] HID: Add support for Surface Aggregator Module HID transport Maximilian Luz
2021-03-10 22:53 ` [PATCH 1/2] " Maximilian Luz
2021-03-10 22:53 ` [PATCH 2/2] HID: surface-hid: Add support for legacy keyboard interface Maximilian Luz
2021-03-17 17:51 ` [PATCH 0/2] HID: Add support for Surface Aggregator Module HID transport Hans de Goede
2021-03-27 20:49 ` Maximilian Luz [this message]
2021-03-30 7:22 ` 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=a0e28af7-3451-83a5-ca16-e230ec70c518@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=blaz@mxxn.io \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).