Hi Mauro, On Thu, Mar 11, 2010 at 12:46:19PM -0300, Mauro Carvalho Chehab wrote: > In order to allow userspace programs to autoload an IR table, a link is > needed to point to the corresponding input device. > > $ tree /sys/class/irrcv/irrcv0 > /sys/class/irrcv/irrcv0 > |-- current_protocol > |-- input -> ../../../pci0000:00/0000:00:0b.1/usb1/1-3/input/input22 > |-- power > | `-- wakeup > |-- subsystem -> ../../../../class/irrcv > `-- uevent > > It is now easy to associate an irrcv device with the corresponding > device node, at the input interface. > I guess the question is why don't you make input device a child of your irrcvX device? Then I believe driver core will link them properly. It will also ensure proper power management hierarchy. That probably will require you changing from class_dev into device but that's the direction kernel is going to anyway. Thanks. -- 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
