All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Fortuna Carvalho <pricardofc@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Hot add a PCIe device driver upon hotplug event
Date: Mon, 12 Jan 2015 17:26:24 +0000	[thread overview]
Message-ID: <CAH9N0t-D0rM05E0nSDaDcVSdwnFt142aG=+FH_6c51Hf+nTMCw@mail.gmail.com> (raw)
In-Reply-To: <CAErSpo48mPENuHpES1Q73ep+NKG8x2Zgb+g71do02y7vufbtfQ@mail.gmail.com>

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?
Thx,
Paulo.

2015-01-12 16:58 GMT, Bjorn Helgaas <bhelgaas@google.com>:
> On Mon, Jan 12, 2015 at 5:42 AM, Paulo Fortuna Carvalho
> <pricardofc@gmail.com> 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
>

  reply	other threads:[~2015-01-12 17:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 11:42 Hot add a PCIe device driver upon hotplug event Paulo Fortuna Carvalho
2015-01-12 16:58 ` Bjorn Helgaas
2015-01-12 17:26   ` Paulo Fortuna Carvalho [this message]
2015-01-12 17:41     ` Bjorn Helgaas
     [not found]       ` <CAH9N0t-EP9p2V3JMht1F_EyK+bOdiiH1krPLrsTMDQ_961damQ@mail.gmail.com>
2015-01-13 17:29         ` Bjorn Helgaas
     [not found]   ` <CAH9N0t8s+kcG_Qok0wpoDz9jzwvPk_QmBK_p-qbACZJjrr+iVQ@mail.gmail.com>
2015-01-22 17:41     ` Bjorn Helgaas
     [not found]       ` <CAH9N0t-+gog9wNFo7hqhzrWuttrRyf5HjjHciFrDGz1rZUiUfw@mail.gmail.com>
2015-01-22 22:20         ` Bjorn Helgaas
2015-01-23 11:35           ` Paulo Fortuna Carvalho
2015-01-23 14:36             ` Bjorn Helgaas
2015-01-27 16:31               ` Paulo Fortuna Carvalho
2015-01-27 16:43                 ` Bjorn Helgaas
2015-01-27 16:47                 ` Greg Kroah-Hartman
2015-01-27 17:10                   ` Paulo Fortuna Carvalho
     [not found]                   ` <CAH9N0t-M2QfW84Jd3fRaLr+NdFvZEkjXzrXsgncoLhtYv-xQ3g@mail.gmail.com>
     [not found]                     ` <CAH9N0t-_JbwtZeU+Kyds8=NX=CBT-+_ecKiUWPKr1zXiLKm0vQ@mail.gmail.com>
2015-01-27 17:11                       ` Greg Kroah-Hartman
     [not found]               ` <54C5EF11.8070604@desy.de>
2015-01-27 16:50                 ` Bjorn Helgaas
2015-01-28  7:51                   ` Ludwig Petrosyan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH9N0t-D0rM05E0nSDaDcVSdwnFt142aG=+FH_6c51Hf+nTMCw@mail.gmail.com' \
    --to=pricardofc@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.