From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Tue, 28 Jul 2009 00:04:14 +0000 Subject: Re: [PATCH 2/2] hid2hci: when recovering from S3 use parent devpath Message-Id: List-Id: References: <4A6E19FF.5070207@dell.com> In-Reply-To: <4A6E19FF.5070207@dell.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: linux-hotplug@vger.kernel.org On Mon, Jul 27, 2009 at 23:19, Mario Limonciello 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