Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755933Ab3D0B5I (ORCPT ); Fri, 26 Apr 2013 21:57:08 -0400 Received: from mail-ie0-f178.google.com ([209.85.223.178]:64848 "EHLO mail-ie0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753373Ab3D0B5F (ORCPT ); Fri, 26 Apr 2013 21:57:05 -0400 MIME-Version: 1.0 In-Reply-To: <517B2F1B.6000704@huawei.com> References: <1367024974-6063-1-git-send-email-yinghai@kernel.org> <517B2F1B.6000704@huawei.com> Date: Fri, 26 Apr 2013 18:57:04 -0700 X-Google-Sender-Auth: v1rjwUXB4lU5msXZlMzVg9ePAgs Message-ID: Subject: Re: [RFC PATCH] PCI: Enable pci bridge when it is needed From: Yinghai Lu To: Yijing Wang Cc: Bjorn Helgaas , "Rafael J. Wysocki" , "linux-pci@vger.kernel.org" , Linux Kernel Mailing List Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 937 Lines: 19 On Fri, Apr 26, 2013 at 6:51 PM, Yijing Wang 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. Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/