All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] PCI / ACPI: Make acpiphp ignore root bridges using PCIe native hotplug
Date: Sun, 23 Oct 2011 00:10:37 +0200	[thread overview]
Message-ID: <201110230010.37802.rjw@sisk.pl> (raw)
In-Reply-To: <CAE9FiQUxuajrqka97M_tvbXoMSzPTBGyjiBib_EG4MjRTuNmFQ@mail.gmail.com>

On Saturday, October 22, 2011, Yinghai Lu wrote:
> On Fri, Oct 21, 2011 at 3:43 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > If the kernel has requested control of the PCIe native hotplug
> > feature for a given root complex, the acpiphp driver should not try
> > to handle that root complex and it should leave it to pciehp.
> > Failing to do so causes problems to happen if acpiphp is loaded
> > before pciehp on such systems.
> 
> Should pciehp be built-in kernel instead of as a module?

Well, perhaps.  Still, though, if someone doesn't build pciehp and
the control of the native PCIe hotplug is granted for a given root
complex, acpiphp won't work anyway.

Thanks,
Rafael

  reply	other threads:[~2011-10-22 22:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 22:43 [PATCH] PCI / ACPI: Make acpiphp ignore root bridges using PCIe native hotplug Rafael J. Wysocki
2011-10-22 21:58 ` Yinghai Lu
2011-10-22 22:10   ` Rafael J. Wysocki [this message]
2011-10-25 13:10 ` Kenji Kaneshige
2011-10-25 13:25   ` Rafael J. Wysocki
2011-10-26  0:28     ` Kenji Kaneshige
2011-10-26 11:42       ` Rafael J. Wysocki
2011-10-28  2:45         ` Kenji Kaneshige
2011-11-06 22:11           ` [PATCH] PCI / ACPI: Make acpiphp ignore root bridges using SHPC " Rafael J. Wysocki
2011-11-07  1:43             ` Kenji Kaneshige
2011-11-11 17:49               ` Jesse Barnes

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=201110230010.37802.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.