From: Hans de Goede <hdegoede@redhat.com>
To: Maximilian Luz <luzmaximilian@gmail.com>
Cc: Mark Gross <markgross@kernel.org>, Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] platform/surface: aggregator: Add support for Surface Laptop Studio
Date: Thu, 21 Oct 2021 20:33:43 +0200 [thread overview]
Message-ID: <1e99ab2b-c5c3-49c9-18c3-1f103c4dbe85@redhat.com> (raw)
In-Reply-To: <20211021130904.862610-1-luzmaximilian@gmail.com>
Hi,
On 10/21/21 15:09, Maximilian Luz wrote:
> This series adds Surface Aggregator Module (SAM) support for the new
> Surface Laptop Studio (SLS).
>
> This is mostly straight-forward addition of devices to the Surface
> Aggregator registry, but the Surface HID driver needs a couple of small
> changes. Specifically, we need to allow it to probe against SAM devices
> with target ID 1 and also need to use the corresponding registry for
> those.
>
> I hope it's okay that I've CCed stable to get these included in v5.14+
> stable kernels. The changes are fairly small and enable keyboard and
> touchpad on the SLS. Most other things (except touch) should already
> work well on the latest stable kernels, so back-porting this series
> would make the SLS a usable device on those.
Thank you for your patch-series, I've applied the series to my
review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
>
> Maximilian Luz (3):
> platform/surface: aggregator_registry: Add support for Surface Laptop
> Studio
> HID: surface-hid: Use correct event registry for managing HID events
> HID: surface-hid: Allow driver matching for target ID 1 devices
>
> drivers/hid/surface-hid/surface_hid.c | 4 +-
> .../surface/surface_aggregator_registry.c | 54 +++++++++++++++++++
> include/linux/surface_aggregator/controller.h | 4 +-
> 3 files changed, 58 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2021-10-21 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 13:09 [PATCH 0/3] platform/surface: aggregator: Add support for Surface Laptop Studio Maximilian Luz
2021-10-21 13:09 ` [PATCH 1/3] platform/surface: aggregator_registry: " Maximilian Luz
2021-10-21 13:09 ` [PATCH 2/3] HID: surface-hid: Use correct event registry for managing HID events Maximilian Luz
2021-10-21 13:09 ` [PATCH 3/3] HID: surface-hid: Allow driver matching for target ID 1 devices Maximilian Luz
2021-10-21 18:33 ` Hans de Goede [this message]
2021-10-22 6:55 ` [PATCH 0/3] platform/surface: aggregator: Add support for Surface Laptop Studio Benjamin Tissoires
2021-10-22 8:56 ` 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=1e99ab2b-c5c3-49c9-18c3-1f103c4dbe85@redhat.com \
--to=hdegoede@redhat.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).