Yes, We can have a black list instead of white list. Are you planning to submit changes? Thanks, Srinivas -----Original Message----- From: Alexander Holler [mailto:holler@xxxxxxxxxxxxx] Sent: Wednesday, December 05, 2012 12:15 PM To: Pandruvada, Srinivas Cc: linux-iio@xxxxxxxxxxxxxxx; linux-input@xxxxxxxxxxxxxxx Subject: Re: HID-sensor(-hub.c) and device IDs Am 05.12.2012 20:21, schrieb Pandruvada, Srinivas: > We have not tested on sensor hubs from different vendors except few. It is possible that some vendors are using sensor hub as raw devices . We can remove vendor product ids once we have a good list for support. Hmm, sorry, I don't understand that fully. Does that mean that the list is there to use the driver only with a small group of devices because otherwise some HID-sensors aren't usable as raw devices? I don't know how many HID-sensor devices are already out in the wild, but because the standard looks fairly new, I don't think there are that many. And I wonder how you want to get the list larger, if nobody notifies that they should use hid-sensor-hub.c. I think the correct way would be to build a blacklist instead of a whitelist. Regards, Alexander > Thanks, > Srinivas > > -----Original Message----- > From: Alexander Holler [mailto:holler@xxxxxxxxxxxxx] > Sent: Wednesday, December 05, 2012 10:45 AM > To: linux-iio@xxxxxxxxxxxxxxx; linux-input@xxxxxxxxxxxxxxx; > Pandruvada, Srinivas > Subject: HID-sensor(-hub.c) and device IDs > > Hello, > > is there any special reason why vendor and devices IDs for HID-sensors must be listed in drivers/hid/hid-sensor-hub.c and drivers/hid/hid-core.c? > > Maybe I'm missing something, but I don't think this is how HID is supposed to work. > > Regards, > > Alexander > -- > To unsubscribe from this list: send the line "unsubscribe linux-iio" > in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo > info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
