From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Rahul Rameshbabu <rrameshbabu@nvidia.com>
Subject: [PATCH RFC v1 0/3] HID: nvidia-shield: More functionality on top of initial driver
Date: Mon, 29 May 2023 15:20:49 -0700 [thread overview]
Message-ID: <20230529222052.68913-1-rrameshbabu@nvidia.com> (raw)
This patch series introduces more functionality on top of the initial
nvidia-shield HID driver sent to the linux-input mailing list. The android
media buttons, capacitive slider, and led on the Thunderstrike controller
are now supported. If possible, would appreciate an acknowledgment of the
initial driver patch or more feedback if needed.
Link: https://lore.kernel.org/linux-input/20230418203747.24000-1-rrameshbabu@nvidia.com/
Rahul Rameshbabu (3):
HID: nvidia-shield: Add mappings for consumer HID USAGE buttons
HID: nvidia-shield: Support LED functionality for Thunderstrike
HID: nvidia-shield: Remove space prefix from label in
shield_haptics_create
drivers/hid/hid-nvidia-shield.c | 173 ++++++++++++++++++++++++++++++--
1 file changed, 162 insertions(+), 11 deletions(-)
--
2.38.4
next reply other threads:[~2023-05-29 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 22:20 Rahul Rameshbabu [this message]
2023-05-29 22:20 ` [PATCH RFC v1 1/3] HID: nvidia-shield: Add mappings for consumer HID USAGE buttons Rahul Rameshbabu
2023-05-29 22:20 ` [PATCH RFC v1 2/3] HID: nvidia-shield: Support LED functionality for Thunderstrike Rahul Rameshbabu
2023-05-29 22:20 ` [PATCH RFC v1 3/3] HID: nvidia-shield: Remove space prefix from label in shield_haptics_create Rahul Rameshbabu
2023-06-09 15:53 ` [PATCH RFC v1 0/3] HID: nvidia-shield: More functionality on top of initial driver 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=20230529222052.68913-1-rrameshbabu@nvidia.com \
--to=rrameshbabu@nvidia.com \
--cc=benjamin.tissoires@redhat.com \
--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