mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	"Zheng, Lv" <lv.zheng@intel.com>,
	"Huang, Ying" <ying.huang@intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	x86 list <x86@kernel.org>
Subject: Re: [PATCH 1/5] driver core / ACPI: Move ACPI support to core device and driver types
Date: Wed, 31 Oct 2012 22:06 +0100	[thread overview]
Message-ID: <4946697.LIFggnbCY6@vostro.rjw.lan> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F19D5B8C0@ORSMSX108.amr.corp.intel.com>

On Wednesday, October 31, 2012 08:33:53 PM Luck, Tony wrote:
> > By "tested" I mean "run with some new devices that use the ACPI enumeration
> > provided here, on x86".  Sorry for being too vague.
> 
> Do you or Mika have access to an ia64 box to test.

I don't.  I'm not sure about Mika.

> If not, can you suggest some way that I could exercise this code w/o the new
> devices. Or at least reassure myself that all is benign in a system full of
> old devices.

There are two parts of the new code, one that's always executed, regardless of
whether or not there are devices using the support provided by this series, and
the other that's executed only for those devices.

All depends on what's there in acpi_platform_device_ids[] (added by patch [5/5]),
which is empty for now (Mika has a separate patch adding some IDs in there).
The second part of the new code will only be run and platform device objects
will only be created by it if there is at least one entry in
acpi_platform_device_ids[] matching a device ID of an ACPI node in the BIOS.

The BIOSes of currently available ia64 systems don't contain ACPI nodes whose
IDs will match the IDs of the new devices (ie. the ones that are going to be
added to acpi_platform_device_ids[]), so for ia64 it should be sufficient to
test that code as is (ie. without any new devices in the system).

Thanks,
Rafael


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

  reply	other threads:[~2012-10-31 21:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31  9:31 [PATCH 0/5] ACPI-based enumeration of devices that are not discoverable natively Rafael J. Wysocki
2012-10-31  9:33 ` [PATCH 2/5] ACPI: Provide generic functions for matching ACPI device nodes Rafael J. Wysocki
2012-10-31  9:34 ` [PATCH 3/5] ACPI / x86: Export acpi_[un]register_gsi() Rafael J. Wysocki
2012-10-31  9:35 ` [PATCH 4/5] ACPI / ia64: " Rafael J. Wysocki
2012-10-31  9:36 ` [PATCH 5/5] ACPI: Add support for platform bus type Rafael J. Wysocki
2012-11-01  6:34   ` Yinghai Lu
2012-11-01 14:35     ` Rafael J. Wysocki
2012-11-01 16:19       ` Yinghai Lu
2012-11-01 21:21         ` Rafael J. Wysocki
2012-11-01 22:38           ` Yinghai Lu
2012-11-01 23:17             ` Rafael J. Wysocki
2012-10-31  9:38 ` [PATCH 1/5] driver core / ACPI: Move ACPI support to core device and driver types Rafael J. Wysocki
2012-10-31 16:24   ` Greg Kroah-Hartman
2012-10-31 18:42     ` Rafael J. Wysocki
2012-10-31 18:44       ` H. Peter Anvin
2012-10-31 19:00         ` Rafael J. Wysocki
2012-10-31 20:03         ` Luck, Tony
2012-10-31 20:30           ` Rafael J. Wysocki
2012-10-31 20:33             ` Luck, Tony
2012-10-31 21:06               ` Rafael J. Wysocki [this message]
2012-10-31 21:19                 ` Mika Westerberg
2012-10-31 21:36                 ` Luck, Tony
2012-10-31 21:46                   ` 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=4946697.LIFggnbCY6@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.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®