From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] HID: steelseries: Add support for Arctis 1 XBox
Date: Thu, 29 Jun 2023 13:09:38 -0700 [thread overview]
Message-ID: <87mt0i9gjh.fsf@nvidia.com> (raw)
In-Reply-To: <8b8d8d78bb8856b933ee92ba2b9c8a256f90d29b.camel@hadess.net> (Bastien Nocera's message of "Thu, 29 Jun 2023 22:03:05 +0200")
On Thu, 29 Jun, 2023 22:03:05 +0200 Bastien Nocera <hadess@hadess.net> wrote:
> On Thu, 2023-06-29 at 11:50 -0700, Rahul Rameshbabu wrote:
>> On Thu, 29 Jun, 2023 19:20:27 +0200 Bastien Nocera
>> <hadess@hadess.net> wrote:
>> > +static const struct hid_device_id steelseries_devices[] = {
>> > + { HID_USB_DEVICE(USB_VENDOR_ID_STEELSERIES,
>> > USB_DEVICE_ID_STEELSERIES_SRWS1),
>> > + .driver_data = STEELSERIES_SRWS1 },
>> > +
>> > + { /* SteelSeries Arctis 1 Wireless for XBox */
>> > + HID_USB_DEVICE(USB_VENDOR_ID_STEELSERIES, 0x12b6),
>>
>> Shouldn't the USB device id be added to drivers/hid/hid-ids.h?
>
> No, the hid-ids.h is only used if 2 files in the hid directory need to
> reference the same device.
>
> Since changes to the way hid drivers are loaded, there's no need to
> blocklist the devices in the core to handle them in a driver, so
> there's no need to reference the device in another place than the
> driver itself, so no need to add it to hid-ids.h
Makes sense with the fact that the device id is only needed in this
source file. For example, you don't need to recompile the steelcase
driver module when introduce some other unrelated device. Thanks for the
clarification.
-- Rahul Rameshbabu
next prev parent reply other threads:[~2023-06-29 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 17:20 [PATCH] HID: steelseries: Add support for Arctis 1 XBox Bastien Nocera
2023-06-29 18:50 ` Rahul Rameshbabu
2023-06-29 20:03 ` Bastien Nocera
2023-06-29 20:09 ` Rahul Rameshbabu [this message]
2023-06-29 19:49 ` kernel test robot
2023-06-29 20:32 ` kernel test robot
2023-06-30 13:13 ` Bastien Nocera
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=87mt0i9gjh.fsf@nvidia.com \
--to=rrameshbabu@nvidia.com \
--cc=benjamin.tissoires@redhat.com \
--cc=hadess@hadess.net \
--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