From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Toshi Kani <toshi.kani@hp.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>, Jiang Liu <liuj97@gmail.com>
Subject: Re: [PATCH] ACPI / scan: Treat power resources in a special way
Date: Mon, 07 Jan 2013 22:02:59 +0100 [thread overview]
Message-ID: <1458998.lg5S0BfPCV@vostro.rjw.lan> (raw)
In-Reply-To: <1357579019.2153.2.camel@misato.fc.hp.com>
On Monday, January 07, 2013 10:16:59 AM Toshi Kani wrote:
> On Mon, 2012-12-31 at 00:46 +0000, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >
> > Commit 1d57433 (ACPI: Separate adding ACPI device objects from
> > probing ACPI drivers) introduced an ACPI power resources management
>
> I am seeing a different commit id for this.
>
> commit 805d410fb0dbd65e1a57a810858fa2491e75822d
> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Date: Fri Dec 21 00:36:39 2012 +0100
>
> ACPI: Separate adding ACPI device objects from probing ACPI drivers
>
My bad, sorry.
I rebased the branch without modifying the changelog of this patch. It should
be fixed now, but please note that the acpi-scan branch has changed.
> > regression, because it didn't ensure that the power resources
> > driver bind to the struct acpi_device objects corresponding
> > to power resources as soon as they were created. As a result,
> > ACPI power management routines may attempt to access power resource
> > objects before they are ready to use.
> >
> > To fix this problem, tell the acpi_add_single_object() in
> > acpi_bus_check_add() to probe the driver for objects of type
> > ACPI_BUS_TYPE_POWER. This fix has been verified to work on
> > HP nx6325 where the problem was first observed.
> >
> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The change looks good.
>
> Acked-by: Toshi Kani <toshi.kani@hp.com>
Thanks a lot,
Rafael
> > ---
> >
> > The commit mentioned in the changelog is in linux-next only for now, but
> > it's likely to go upstream in this form anyway and the fix on top of the
> > whole ACPI scan series is trivial.
> >
> > Thanks,
> > Rafael
> >
> > ---
> > drivers/acpi/scan.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > Index: linux/drivers/acpi/scan.c
> > ===================================================================
> > --- linux.orig/drivers/acpi/scan.c
> > +++ linux/drivers/acpi/scan.c
> > @@ -1606,7 +1606,8 @@ static acpi_status acpi_bus_check_add(ac
> > return AE_CTRL_DEPTH;
> > }
> >
> > - acpi_add_single_object(&device, handle, type, sta, false);
> > + acpi_add_single_object(&device, handle, type, sta,
> > + type == ACPI_BUS_TYPE_POWER);
> > if (!device)
> > return AE_CTRL_DEPTH;
> >
> >
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-01-07 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 0:46 [PATCH] ACPI / scan: Treat power resources in a special way Rafael J. Wysocki
2013-01-07 17:16 ` Toshi Kani
2013-01-07 21:02 ` 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=1458998.lg5S0BfPCV@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=toshi.kani@hp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox