I need to call a _DSM method for a device hardwired to a motherboard USB slot. There will be two such devices. I've done this from Windows, but I have a couple of questions about a Linux implementation. I believe that I am not an idiot, but feel free to express an alternative opinion. Everything is pretty clear to me, except for the mechanism to find the DSDT path for the slots. I'm hoping I can do all of the USB handling from user-mode without a custom kernel driver. Given the sysfs name of the device in /sys/bus/usb/devices (for example, 1-1.3 or 2-1.3), I can parse that and hack up the path name (\_SB.PCI0.EHC1.HUBN.PR01.PR13 or ..EHC2...), but that seems rather delicate, and I don't know that the naming scheme there is standardized, should this need to move to another manufacturer. I couldn't find any way to link from the sysfs tree for the USB device back to the /sys/devices/LNXSYSTM:00 tree, which would give me the DSDT path. So, in a udev arrival script for a device, or in a USB kernel driver for a device, how can I learn the DSDT path to that device's slot, or at least acquire an acpi_handle so I can call a _DSM? And am I correct in thinking there is no way to enable a GPE callback without using a kernel driver? -- Tim Roberts, timr@xxxxxxxxx Providenza & Boekelheide, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
