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 18:59:43 +0000 [thread overview]
Message-ID: <20160809185943.GA31642@kroah.com> (raw)
In-Reply-To: <AT5PR84MB0177723391A9CA3EAEE43C0088050@AT5PR84MB0177.NAMPRD84.PROD.OUTLOOK.COM>
On Tue, Aug 09, 2016 at 11:48:59AM -0700, divakar wrote:
> May be i missed one piece of information. I thought i had that in my
> inline response but just realized i missed it.
>
> Device 0 ( FPGA 0), has custom logic which will detect the presence of
> the card 1 and card 2 and controls the power switches to the same. So If
> this makes fpga0 a "hotplug controller " then i can add the resource
> management logic/code for devices on card 1 and card 2 to this driver.
> Currently fpga_0 driver does some init for some of the devices on
> itself. can i follow any hp controller driver example to do the above or
> is there any specific driver/eg i can follow? noted your point on reading
> the spec for the details and i am on it.
You might get away with it for your limited hardware platform, but all
bets are off if you plug it into something else.
Again, PCI resource management is handled by the firmware/bios and the
pci hotplug controller. You can try to fake it out, with limited
success, but really, why do you want to do so? Just use a real machine,
that's what the pci hotplug hardware was designed for. It's much
cheaper than trying to work around it in the end, trust me...
greg k-h
next prev parent reply other threads:[~2016-08-09 18:59 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
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 [this message]
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=20160809185943.GA31642@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 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).