On Sat, Nov 27, 2010 at 11:12:51PM -0500, Jeremy Moles wrote: > > WHOA! Now we're cooking! My probe succeeds and now my > event/input_mapping/input_mapped functions all get called! > > When driver developers are writing HID glue drivers like this, how is it > you generally determine the contents of your drv_data structure? Via > hardware specs or is there some way to poke at the device via USB and > have it tell you? Perhaps this question is a bit TOO out of line, as I'm > sure that information is available in the standard USB HID > information... > If you are talking about data structures that are accessed via hig_get_drvdata() and hid_set_drvdata() then it is entirely up to driver writer to define them. Basically whatever state you need to be able to handle the device. -- Dmitry -- 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
