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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 27, 2009 at 23:19, Mario
Limonciello<mario_limonciello@xxxxxxxx> wrote:
> After the previous cleanup submitted to hid2hci, the code for finding
> the sibling device changed significantly.  Although this works perfectly
> fine when all the devices are on the bus, it doesn't for the recovery
> from S3 situation.  The device is already off the bus by the time
> hid2hci is called so the devpath is not found in the udev database.  The
> easiest way to solve this is to use the parent's devpath instead, but
> this does introduce a dependency on importing the env variable DEVPATH
> from the parent.

No, we can't do this. DEVPATH is the unique property of every device,
it can not be imported from a different device.

What does:
  ls -l /sys/bus/usb/devices/
print, and which device is the one the remove event hooks into and
which one is the one that needs to be found?

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

[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux