From: Yinghai Lu <yinghai@kernel.org>
To: Chuck Tuffli <ctuffli@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Error assigning BAR 0 to hotplugged device
Date: Wed, 16 Jul 2014 16:49:01 -0700 [thread overview]
Message-ID: <CAE9FiQX9p-nTGeRo365d9m10OXF9-QqUJ+4z6GD37ztd+s8EEQ@mail.gmail.com> (raw)
In-Reply-To: <CAE9FiQW+GbprQZNvHC-ek1cSydP3KWcjgAU0ii5_jECC1+tXrg@mail.gmail.com>
On Wed, Jul 16, 2014 at 4:47 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> On Wed, Jul 16, 2014 at 1:55 PM, Yinghai Lu <yinghai@kernel.org> wrote:
>
> in the tree:
> 80:03.0 ==> 96:00.0 ==> 97:08.0 ==> 98:00.0 ==> 99:00.0 ==> 9a:00.0
> ==> 9b:15.0
>
> only 97:08.0 and 99:00.0 is hotplug+.
>
> and kernel will honor BIOS set value at first, and realloc will only work on
> unassigned/invalid assigned BARs. and hpmem_size will be only treated at
> optional size even on hotplug slots.
>
> a5:00.0 is not in 9b:15.0 at first, so yo just put the card in can
> rescan the card,
> right?
>
> In this case we don't to realloc, as other devices could already have
> driver loaded.
>
> You need to fix the BIOS to have correct setting for 96:1b.0.
should 9b:15.0
>
> SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd-
> HotPlug- Surprise-
> Slot #21, PowerLimit 25.000W; Interlock- NoCompl-
> SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet-
> CmdCplt- HPIrq- LinkChg-
> Control: AttnInd Unknown, PwrInd Unknown,
> Power- Interlock-
> SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt-
> PresDet+ Interlock-
> Changed: MRL- PresDet+ LinkState+
>
> to make it really hotplug slot.
>
> And BIOS need to make sure parent bus/bridge have enough resource ranges
> for the hotplug slots.
>
> Yinghai
next prev parent reply other threads:[~2014-07-16 23:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 19:37 Error assigning BAR 0 to hotplugged device Chuck Tuffli
2014-07-16 17:19 ` Chuck Tuffli
2014-07-16 18:54 ` Bjorn Helgaas
2014-07-16 20:55 ` Yinghai Lu
2014-07-16 23:47 ` Yinghai Lu
2014-07-16 23:49 ` Yinghai Lu [this message]
2014-07-17 1:00 ` Chuck Tuffli
2014-07-17 2:15 ` Yinghai Lu
2014-07-17 15:08 ` Chuck Tuffli
2014-07-17 16:33 ` Yinghai Lu
2014-07-17 16:47 ` Chuck Tuffli
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=CAE9FiQX9p-nTGeRo365d9m10OXF9-QqUJ+4z6GD37ztd+s8EEQ@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=ctuffli@gmail.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 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).