Am 11.06.2013 16:52, schrieb Alexandre Relange: > Implements the Boolean Switch sensor from the USB sensor usage tables > http://www.usb.org/developers/hidpage/HUTRR39b.pdf > > This code is based on drivers/iio/light/hid-sensor-als.c > > Signed-off-by: Alexandre Relange <alexandre@xxxxxxxxxxx> > --- ... > + > +/*Format: HID-SENSOR-usage_id_in_hex*/ > +/*Usage ID from spec for Boolean-Switch: 0x200061*/ > +#define DRIVER_NAME "HID-SENSOR-200061" > + ... > +static struct platform_driver hid_switch_platform_driver = { > + .driver = { > + .name = DRIVER_NAME, > + .owner = THIS_MODULE, > + }, > + .probe = hid_switch_probe, > + .remove = hid_switch_remove, > +}; > +module_platform_driver(hid_switch_platform_driver); > + You already might add the fix I've recently posted for all the other iio HID drivers to let the module automatically loaded. It gives a nicier driver name too. I've pasted the patch for the als-driver for your reference below. Be sure to change the usage id to the one for your driver. Regards, Alexander Holler -------- --- a/drivers/iio/light/hid-sensor-als.c +++ b/drivers/iio/light/hid-sensor-als.c @@ -30,10 +30,6 @@ #include <linux/iio/triggered_buffer.h> #include "../common/hid-sensors/hid-sensor-trigger.h" -/*Format: HID-SENSOR-usage_id_in_hex*/ -/*Usage ID from spec for Ambiant-Light: 0x200041*/ -#define DRIVER_NAME "HID-SENSOR-200041" - #define CHANNEL_SCAN_INDEX_ILLUM 0 struct als_state { @@ -355,9 +351,19 @@ static int hid_als_remove(struct platform_device *pdev) return 0; } +static struct platform_device_id hid_als_ids[] = { + { + /* Format: HID-SENSOR-usage_id_in_hex_lowercase */ + .name = "HID-SENSOR-200041", + }, + { /* sentinel */ } +}; +MODULE_DEVICE_TABLE(platform, hid_als_ids); + static struct platform_driver hid_als_platform_driver = { + .id_table = hid_als_ids, .driver = { - .name = DRIVER_NAME, + .name = KBUILD_MODNAME, .owner = THIS_MODULE, }, .probe = hid_als_probe, -- 1.8.1.5 -- 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
