From: Toshi Kani <toshi.kani@hp.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH] ACPI: Enable SCI_EMULATE to manually simulate physical hotplug testing.
Date: Tue, 04 Sep 2012 15:54:21 -0600 [thread overview]
Message-ID: <1346795661.4732.229.camel@misato.fc.hp.com> (raw)
In-Reply-To: <CAE9FiQVT-0zmE9jyyoWmzM5dd-XAXmHgT+vGqSUKgE2yuPOOvg@mail.gmail.com>
On Tue, 2012-09-04 at 14:46 -0700, Yinghai Lu wrote:
> On Tue, Sep 4, 2012 at 2:34 PM, Toshi Kani <toshi.kani@hp.com> wrote:
> > On Tue, 2012-09-04 at 12:17 -0700, Yinghai Lu wrote:
> > - If a full path is specified in acpi_name, it ignores the arg hsb
> > ("\_SB").
> > - If a relative path is specified in acpi_name, it appends the arg hsb.
> >
> > So, the code looks good to me; assuming that is the intent.
> >
> > However, the error message below will show up like "\_SB.\_SB.PCIB" when
> > a full path is specified.
>
> I always use
> echo "\_SB.PCIB 3" > /sys/kernel/debug/acpi/sci_notify
>
> and it works.
>
> so assume that function can accept \_SB.PCIB and PCIB both.
I agree. And that's what I tried to say.
The error message below will be confusing when a (invalid) full path
name is specified, though.
>> + if (ACPI_FAILURE(status) || ACPI_FAILURE(status1)) {
>> + pr_err(PREFIX
>> + "acpi getting handle to <\\_SB.%s> failed inside notify_client
\n",
>> + acpi_name);
>> + return;
>> + }
Thanks,
-Toshi
next prev parent reply other threads:[~2012-09-04 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 21:27 [PATCH] ACPI: Enable SCI_EMULATE to manually simulate physical hotplug testing Yinghai Lu
2012-09-04 16:27 ` Toshi Kani
2012-09-04 19:17 ` Yinghai Lu
2012-09-04 21:34 ` Toshi Kani
2012-09-04 21:46 ` Yinghai Lu
2012-09-04 21:54 ` Toshi Kani [this message]
2012-09-14 0:22 ` Toshi Kani
2012-09-14 3:50 ` Yinghai Lu
2012-09-14 14:49 ` Toshi Kani
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=1346795661.4732.229.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=ashok.raj@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox