From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Assign BAR address for pci device after hotplug
Date: Tue, 09 Aug 2016 00:49:39 +0000 [thread overview]
Message-ID: <20160809004939.GA3875@kroah.com> (raw)
In-Reply-To: <AT5PR84MB0177723391A9CA3EAEE43C0088050@AT5PR84MB0177.NAMPRD84.PROD.OUTLOOK.COM>
On Mon, Aug 08, 2016 at 05:32:42PM -0700, divakar wrote:
> Hi Greg,
>
> Thanks for your comments. I managed to install a client which will do
> the auto format. Hopefully this is better than before. Please find my
> responses inline. Also added extra questions and information about the
> setup.
>
> Questions:
> 1. Since the modified_my_driver_probe is working, is that the recommended
> way of doing it? I couldn't find any sample drivers using it. So wanted
> your guidance
I dont understand, what "modified" probe function?
> 2. There is no hotplug controller as far is know off in the setup (
> assuming native x86 soc has root port which has inbuilt hp controller
> and pcieport driver takes care of it). Am i missing something?
Then your hardware does not support PCI hotplug, so I don't recommend
trying to use it.
Seriously, this is a hardware and BIOS requirement to support this, if
you don't have that hardware, you can't really work around it in the
kernel. Go buy some real hardware for this please.
> 3. When card 2 is inserted there is no hotplug event. Not sure why.
Why would there be? You don't have hardware that notices this.
good luck,
greg k-h
next prev parent reply other threads:[~2016-08-09 0:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 21:11 Assign BAR address for pci device after hotplug Chitturi, Divakar
2016-08-03 5:12 ` Greg KH
2016-08-04 17:09 ` Chitturi, Divakar
2016-08-05 10:53 ` Greg KH
2016-08-09 0:32 ` divakar
2016-08-09 0:49 ` Greg KH [this message]
2016-08-09 17:00 ` divakar
2016-08-09 17:18 ` Greg KH
2016-08-09 18:48 ` divakar
2016-08-09 18:59 ` Greg KH
2016-08-10 0:26 ` divakar
2016-08-10 8:47 ` Greg KH
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=20160809004939.GA3875@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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.