From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Darren Hart <dvhart@infradead.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Zhang Rui <rui.zhang@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Update][PATCH] ACPI / scan: Add a scan handler for PRP0001
Date: Sat, 25 Apr 2015 04:25:59 +0200 [thread overview]
Message-ID: <39726896.AI3Qx9bJPO@vostro.rjw.lan> (raw)
In-Reply-To: <20150424222100.GA2514@vmdeb7>
On Friday, April 24, 2015 03:21:00 PM Darren Hart wrote:
> On Fri, Apr 24, 2015 at 02:15:22AM +0200, Rafael Wysocki wrote:
> > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >
> > If the special PRP0001 device ID is present in the given device's list
> > of ACPI/PNP IDs and the device has a valid "compatible" property in
> > the _DSD, it should be enumerated using the default mechanism,
> > unless some scan handlers match the IDs preceding PRP0001 in the
> > device's list of ACPI/PNP IDs. In addition to that, no scan handlers
> > matching the IDs following PRP0001 in that list should be attached
> > to the device.
> >
> > To make that happen, define a scan handler that will match PRP0001
> > and trigger the default enumeration for the matching devices if the
> > "compatible" property is present for them.
> >
> > Since that requires the check for platform_id and device->handler
> > to be removed from acpi_default_enumeration(), move the fallback
> > invocation of acpi_default_enumeration() to acpi_bus_attach()
> > (after it's checked if there's a matching ACPI driver for the
> > device), which is a better place to call it, and do the platform_id
> > check in there too (device->handler is guaranteed to be unset at
> > the point where the function is looking for a matching ACPI driver).
> >
> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > Acked-by: Darren Hart <dvhart@linux.intel.com>
> > ---
> >
> > The change from the original patch is to change the scan handler
> > behavior to make it return 1 also if the "compatible" property is
> > not present, in which case the additional scan handlers should not
> > trigger too *and* the default enumeration should not trigger either
> > (as there's no ID to match to), which will allow things like
> > auxiliary nodes (think GPIO buttons/LEDs etc) to be easily represented.
>
>
> This should probably be spelled out in the commit message itself as it's a fairly
> unique condition.
I'm going to document that in Documentation/acpi/enumeration.txt anyway.
> > Darren, I've tentatively added your Acked-by tag to this one, please
> > let me know if that's not appropriate.
>
> Spent a bit more time on it this time, so:
>
> Reviewed-by: Darren Hart <dvhart@linux.intel.com>
Thanks!
prev parent reply other threads:[~2015-04-25 2:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 23:28 [PATCH] ACPI / scan: Add a scan handler for PRP0001 Rafael J. Wysocki
2015-04-14 2:04 ` Darren Hart
2015-04-14 11:50 ` Rafael J. Wysocki
2015-04-14 13:03 ` Rafael J. Wysocki
2015-04-22 1:54 ` Rafael J. Wysocki
2015-04-22 9:57 ` Mika Westerberg
2015-05-05 0:49 ` Rafael J. Wysocki
2015-05-05 11:24 ` Mika Westerberg
2015-05-05 12:14 ` Rafael J. Wysocki
2015-04-24 0:15 ` [Update][PATCH] " Rafael J. Wysocki
2015-04-24 22:21 ` Darren Hart
2015-04-25 2:25 ` Rafael J. Wysocki [this message]
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=39726896.AI3Qx9bJPO@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=dvhart@infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rui.zhang@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