On Tue, Sep 25, 2012 at 11:13:43PM +0800, Lan Tianyu wrote: > > hi Greg: [linux-usb added as it concerns them as well] > I find only devices which has bus_type or class can add uevent callback > and output the uevent information. This is because the dev_uevent_filter just return > true for these devices. But some device may not have class and bus_type. > e.g usb endpoint, if we assigned them to usb_bus_type, device core will > try to create sysfs directory link under /sys/bus/usb. But endpoint sysfs > directory's name are same for each usb devices.e.g ep_00, every usb device will > create the endpoint. So in this situation, we can't assign usb endpoint to > usb_bus_type. So even if uevent callback was added and with some information, > it still couldn't output anything. Can we add dev->type check in the > dev_uevent_filter() and return 1 if type exits? Wait, why do you want a uevent for a USB endpoint? What is the problem you are trying to solve here? greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
