From: Greg KH <greg@kroah.com>
To: Anand Kanaginhal <anand_dk@hotmail.com>
Cc: Linux PCI mailing <linux-pci@vger.kernel.org>,
linux kernel mailing <linux-kernel@vger.kernel.org>,
linux hotplug mailing <linux-hotplug@vger.kernel.org>
Subject: Re: PCIe Hotplugging not working
Date: Tue, 29 Nov 2011 22:55:52 +0000 [thread overview]
Message-ID: <20111129225552.GB27909@kroah.com> (raw)
In-Reply-To: <BAY163-W63C79C972B0F87A46B0FDCFBB30@phx.gbl>
On Tue, Nov 29, 2011 at 09:50:41AM -0800, Anand Kanaginhal wrote:
>
> Resending as earlier sends failed
You can not send html messages to vger.kernel.org mailing lists.
> > Why is a pci driver a "char" driver? Do you have a pointer to the
> > source of this?
>
> I am doing an test before putting it in its right place. Another
> reason is that I am treating it as character device and using IOCTLs
> for various operations. I have attached the framework code here.
Just a note, but your framework is backwards, you should allocate your
character device in your probe function, not in the module init
function.
Also, what type of driver is this, why do you need ioctls for it?
> > > 2. I run depmod and "modules.pcimap" also got updated with my module.
> > >
> > > However
> > > if I unplug and plug in the endpoint, my driver .probe and .remove functions
> > > are not being invoked. Is there something more to be done at the bus
> > > level to get the driver to hot plug ?
> >
> > You need a pci hotplug controller driver, is that loaded? That is what
> > is responsible for eventually calling your remove function.
>
> How do I figure out if a pci hotplug controller driver is installed?
How do you know that your hardware supports PCI hotplugging at all?
You need a PCI hotplug controller in the system, generally if you have
one, the driver will be loaded for it, but if you are using a custom
kernel, you might have to build and install it yourself.
> > > I have tried various kernel version, Currently I am trying on 2.6.38.12 (UBUNTU flavor).
> >
> > We can't help you with distro-specific kernels, please use a kernel.org
> > kernel and we will be glad to help you out.
>
> I have tried with vanilla kernel as well with the same results.
What release did you try?
greg k-h
next prev parent reply other threads:[~2011-11-29 22:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY163-W52E309F419E3588206D889FBB30@phx.gbl>
2011-11-29 11:56 ` PCIe Hotplugging not working Anand Kanaginhal
2011-11-29 14:22 ` Greg KH
2011-11-29 17:50 ` Anand Kanaginhal
2011-11-29 22:55 ` Greg KH [this message]
2011-11-29 15:17 ` Ludvig Petrossian
2011-11-30 15:40 ` Matthew Garrett
2011-11-30 17:18 ` Anand Kanaginhal
2011-11-30 18:24 ` Matthew Garrett
2011-12-07 17:23 ` Bjorn Helgaas
2011-12-09 12:41 ` Anand Kanaginhal
2011-12-09 12:45 ` Matthew Garrett
2011-12-09 15:03 ` Anand Kanaginhal
2011-12-09 16:42 ` Greg KH
2011-12-09 17:19 ` Anand Kanaginhal
2011-12-09 18:07 ` Greg KH
[not found] ` <BAY163-W154A24444BB398F609767CFBB90@phx.gbl>
2011-12-09 22:25 ` Greg KH
[not found] ` <BAY163-W582FC4C5828B20E9487D3EFBB90@phx.gbl>
2011-12-09 23:24 ` Anand Kanaginhal
2011-12-09 23:45 ` Greg KH
2011-12-10 19:36 ` John Stoffel
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=20111129225552.GB27909@kroah.com \
--to=greg@kroah.com \
--cc=anand_dk@hotmail.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).