Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753316Ab2JDSgT (ORCPT ); Thu, 4 Oct 2012 14:36:19 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:35280 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751306Ab2JDSgR (ORCPT ); Thu, 4 Oct 2012 14:36:17 -0400 MIME-Version: 1.0 In-Reply-To: <20121004174746.GA24119@google.com> References: <1349305214-3241-1-git-send-email-yinghai@kernel.org> <20121004174746.GA24119@google.com> Date: Thu, 4 Oct 2012 11:36:15 -0700 X-Google-Sender-Auth: 4KEI3fn0yOzP4N2IjYeuGuYP67Q Message-ID: Subject: Re: [PATCH 0/4] ACPI: kill acpi_pci_root_start From: Yinghai Lu To: Bjorn Helgaas Cc: Len Brown , Greg Kroah-Hartman , Andrew Morton , Linus Torvalds , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org 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: 1149 Lines: 22 On Thu, Oct 4, 2012 at 10:47 AM, Bjorn Helgaas wrote: > On Wed, Oct 03, 2012 at 04:00:10PM -0700, Yinghai Lu wrote: > This is a fundamental difference: at boot-time, all the ACPI devices below the > host bridge already exist before the pci_root.c driver claims the bridge, > while at hot-add time, pci_root.c claims the bridge *before* those ACPI > devices exist. > > I think this is wrong. The hot-plug case (where the driver is already > loaded and binds to the device as soon as it's discovered, before the > ACPI hierarchy below it is enumerated) seems like the obviously correct > order. I think we should change the boot-time order to match that, i.e., > we should register pci_root.c *before* enumerating ACPI devices. in booting path, all device get probed at first, and then register driver... do you want to register all pci driver before probing pci devices? 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/