mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Luck, Tony" <tony.luck@intel.com>,
	Toshi Kani <toshi.kani@hp.com>, Aaron Lu <aaron.lu@intel.com>
Subject: [PATCH 0/5] ACPI / scan: Make it possible to use the container hotplug with other scan handlers
Date: Thu, 13 Jun 2013 01:23:01 +0200	[thread overview]
Message-ID: <1417592.vuSG0cUIGo@vostro.rjw.lan> (raw)

Hi All,

It turns out that some BIOSes add container device IDs as _CIDs to device
object that in principle may be matched against the other scan handlers (or
ACPI drivers, but that's not a problem, because the container scan handler
can co-exist with an ACPI driver).  That's why our recent fix for an issue
related to the ACPI video driver had to be reverted right before -rc5.

Although I submitted an alternative fix for that bug, I think the problem
with the container scan handler possibly matching devices already having
some other scan handlers attached needs addressing, because we may need to
use the container hotplug profile for those devices.  The following patch
series is supposed to address it.

[1/5] ACPI / scan: Do not bind ACPI drivers to objects with scan handlers
   (this version shouldn't break the Tony's IA64 HP box the previous one broke)
[2/5] ACPI / scan: Separate hotplug profiles from scan handlers
[3/5] ACPI / scan: Add hotplug profile pointer to struct acpi_device
[4/5] ACPI / scan: Use container hotplug profile for matching device objects
[5/5] ACPI / ia64 / sba_iommu: Use ACPI scan handler for discovery

Patches [1-4/5] were run on my Toshiba test box and didn't break it, but it
really doesn't do any ACPI hotplug notifications.

Patch [5/5] is kind of additional, but it wouldn't work correctly without the
previous ones (to be honest, I haven't tried to compile it yet, but here it
goes for completness).

The patches are against the linux-next branch of the linux-pm.git tree.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

             reply	other threads:[~2013-06-12 23:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 23:23 Rafael J. Wysocki [this message]
2013-06-12 23:23 ` [PATCH 1/5] ACPI / scan: Do not bind ACPI drivers to objects with " Rafael J. Wysocki
2013-06-12 23:24 ` [PATCH 2/5] ACPI / scan: Separate hotplug profiles from " Rafael J. Wysocki
2013-06-12 23:25 ` [PATCH 3/5] ACPI / scan: Add hotplug profile pointer to struct acpi_device Rafael J. Wysocki
2013-06-12 23:26 ` [PATCH 4/5] ACPI / scan: Use container hotplug profile for matching device objects Rafael J. Wysocki
2013-06-12 23:26 ` [PATCH 5/5] ACPI / ia64 / sba_iommu: Use ACPI scan handler for discovery Rafael J. Wysocki
2013-06-13 21:28 ` [PATCH 0/5] ACPI / scan: Make it possible to use the container hotplug with other scan handlers Toshi Kani
2013-06-13 22:13   ` Rafael J. Wysocki
2013-06-13 22:23     ` Toshi Kani
2013-06-14 18:01       ` Luck, Tony
2013-06-14 22:23         ` Rafael J. Wysocki
2013-06-14 22:32           ` Tony Luck
2013-06-14 23:20             ` Rafael J. Wysocki
2013-06-19 17:37               ` Tony Luck
2013-06-19 22:24                 ` Rafael J. Wysocki
2013-06-19 22:40                   ` Tony Luck
2013-06-19 22:51                     ` Rafael J. Wysocki
2013-06-19 23:22                   ` Toshi Kani
2013-06-19 23:35                     ` Rafael J. Wysocki

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=1417592.vuSG0cUIGo@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=aaron.lu@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=toshi.kani@hp.com \
    /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

all inboxes | Powered by JetHome®