Re: [PATCH 2/2] hid2hci: when recovering from S3 use parent devpath

[Kay Sievers <kay.sievers@vrfy.org>]

On Tue, 2009-07-28 at 13:10 -0500, Mario Limonciello wrote:
> Kay Sievers wrote:
> > On Mon, Jul 27, 2009 at 23:19, Mario
> > Limonciello<mario_limonciello@dell.com> wrote:
> >
> > No, we can't do this. DEVPATH is the unique property of every device,
> > it can not be imported from a different device.

> The device that is gone after S3 (the BT device), is:
> 
>     ../../../devices/pci0000:00/0000:00:04.0/usb3/3-4/3-4.3

> The parent device that I was calling with in that patch to find the
> sibling was:
> 
>     ../../../devices/pci0000:00/0000:00:04.0/usb3/3-4

That should work (in theory) with the current logic. I can do here:

$ UDEV_LOG=7 extras/hid2hci/hid2hci -p /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.4 --methodfill --find-sibling-intf\x01:01:00
libudev: udev_device_new_from_syspath: device 0x60b0d0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.4'
libudev: udev_device_new_from_syspath: device 0x60b3d0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1'
libudev: udev_device_new_from_syspath: device 0x61c580 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1'
libudev: udev_device_new_from_syspath: device 0x61c580 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0'
libudev: udev_device_new_from_syspath: device 0x61c580 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3'
libudev: udev_device_new_from_syspath: device 0x61c580 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3/2-1.3:1.0'
libudev: udev_device_new_from_syspath: device 0x61c580 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3/2-1.3:1.0'
libudev: udev_device_new_from_syspath: device 0x61c580 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3/2-1.3:1.0'
libudev: udev_device_new_from_syspath: device 0x6205e0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3/2-1.3:1.1'
libudev: udev_device_new_from_syspath: device 0x6205e0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3/2-1.3:1.1'
libudev: udev_device_new_from_syspath: device 0x6205e0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.4'
libudev: udev_device_new_from_syspath: device 0x6205e0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.4/2-1.4:1.0'
libudev: udev_device_new_from_syspath: device 0x60c5a0 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3/2-1.3:1.0'
libudev: udev_device_new_from_syspath: device 0x60c850 has devpath '/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.3'
libusb couldn't open USB device /dev/bus/usb/002/006: Permission denied.

Where /dev/bus/usb/002/006 belongs to "2-1.3", which has a matching
interface and is the sibling from "2-1.4".

Can you try the same on the real hardware?

Thanks,
Kay

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html