On Mon, Jan 12, 2015 at 11:26 AM, Paulo Fortuna Carvalho <pricardofc@xxxxxxxxx> wrote: > Hello Helgas, > I cannot see that line in dmesg. I think that something else is missing... > Do you know what may cause that not appearing in dmesg? Hotplug Surprise? Can you just collect the entire dmesg log, so I can see what controller is involved and what is happening? Surprise hotplug should work. Are you inserting an ExpressCard, or is it some other form factor? Exactly what hardware are you adding, and what are you adding it to? Bjorn > 2015-01-12 16:58 GMT, Bjorn Helgaas <bhelgaas@xxxxxxxxxx>: >> On Mon, Jan 12, 2015 at 5:42 AM, Paulo Fortuna Carvalho >> <pricardofc@xxxxxxxxx> wrote: >>> Hello, >>> I want to automatically load/unload a PCIe device driver when a card >>> is inserted/removed from the system. I can see in the system logger >>> with dmesg that the interrupt event is captured and acknowledged by >>> the pciehp hotplug service driver. >>> What I want to do next is that the operating system load/unload the >>> corresponding PCIe device driver for that card. >> >> When pciehp receives the interrupt, it should enumerate the device, >> and you should see a line in dmesg similar to this (of course, it will >> have different bus/device/function and different vendor/device IDs): >> >> pci 0000:00:16.0: [8086:9c3a] type 00 class 0x078000 >> >> The PCI core should then add the device using device_add(), and part >> of that is to emit a uevent, which can be read by user-space. >> Generally udev would handle the event and load the appropriate driver. >> I don't know the details of how the user-space side works. >> >> Bjorn >> -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
