From: Yijing Wang <wangyijing@huawei.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] PCI: Enable pci bridge when it is needed
Date: Sat, 27 Apr 2013 10:03:00 +0800 [thread overview]
Message-ID: <517B31D4.9020909@huawei.com> (raw)
In-Reply-To: <CAE9FiQWLfdgR8VoqeVOpCdHa3TpK26Bgs7mZ7Ed+Zq60S=g8Vg@mail.gmail.com>
On 2013/4/27 9:57, Yinghai Lu wrote:
> On Fri, Apr 26, 2013 at 6:51 PM, Yijing Wang <wangyijing@huawei.com> wrote:
>> I think it's cool! Now we enable bridge in various places, this is a headache.
>>
>> hi, yinghai, in this patch, enable bridges depend on the driver call pci_enable_device() explicitly.
>> I was a little worried If there has some devices don't have some drivers bound, but used by system.
>> like ioapic, these devices maybe implemented as pci device, but no pci drivers bind, also, maybe they
>> won't call pci_enable_device() explicity. So if they are under the pci bridge, no one will enable the bridge
>> for them.
>
> If there is really that case, we could call pci_enable_device in
> pci_final quirk for
> them.
Hmm, ok, and I tested this patch in my hotplug machine, it looks good.
>
> Yinghai
>
>
--
Thanks!
Yijing
prev parent reply other threads:[~2013-04-27 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 1:09 [RFC PATCH] PCI: Enable pci bridge when it is needed Yinghai Lu
2013-04-27 1:51 ` Yijing Wang
2013-04-27 1:57 ` Yinghai Lu
2013-04-27 2:03 ` Yijing Wang [this message]
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=517B31D4.9020909@huawei.com \
--to=wangyijing@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=yinghai@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