From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Tomasz Nowicki <tomasz.nowicki@linaro.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
linus.walleij@linaro.org, gnurou@gmail.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linaro-acpi@lists.linaro.org
Subject: Re: [PATCH] ACPI: Add GPIO-signaled event emulator.
Date: Tue, 26 Aug 2014 00:39:59 +0200 [thread overview]
Message-ID: <1828087.V5efjsXTdI@vostro.rjw.lan> (raw)
In-Reply-To: <53F604B2.6020004@linaro.org>
On Thursday, August 21, 2014 04:39:46 PM Tomasz Nowicki wrote:
> Hi Mika,
>
> On 21.08.2014 12:45, Mika Westerberg wrote:
> > On Wed, Aug 20, 2014 at 04:58:20PM +0200, Tomasz Nowicki wrote:
[cut]
> >> +
> >> +static int gpio_evt_trigger(void *data, u64 val)
> >> +{
> >> + struct gpio_pin_data *pin_data = (struct gpio_pin_data *)data;
> >> + int pin = pin_data->pin;
> >> +
> >> + if (ACPI_FAILURE(acpi_execute_simple_method(pin_data->handle, NULL,
> >> + pin <= 255 ? 0 : pin)))
> >> + pr_err(PREFIX "evaluating event method failed\n");
> >
> > acpi_execute_simple_method() passes one argument to the method. You
> > can't use it with _Lxx or _Exx which don't expect any arguments.
> > Otherwise you get this:
> >
> > [ 122.258191] ACPI: \_SB_.GPO2._E12: Excess arguments - Caller passed 1, method requires 0 (20140724/nsarguments-263)
> Right, I will fix it.
OK, so here's my concern.
If AML does any kind of tracking of state in _Exx/_Lxx, you'll likely totally
confuse it by calling those things at random.
I'm not sure I'm seeing a compelling reason to put this thing into the tree
for this reason.
Rafael
next prev parent reply other threads:[~2014-08-25 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 14:58 [PATCH] ACPI: Add GPIO-signaled event emulator Tomasz Nowicki
2014-08-21 10:45 ` Mika Westerberg
2014-08-21 14:39 ` Tomasz Nowicki
2014-08-21 14:54 ` Mika Westerberg
2014-08-21 15:04 ` Tomasz Nowicki
2014-08-25 22:39 ` Rafael J. Wysocki [this message]
2014-08-28 11:19 ` Tomasz Nowicki
2014-08-29 22:37 ` 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=1828087.V5efjsXTdI@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=gnurou@gmail.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=tomasz.nowicki@linaro.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