From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] gpiolib-acpi: introduce acpi_get_gpio_by_index() helper
Date: Thu, 4 Apr 2013 13:13:38 +0300 [thread overview]
Message-ID: <20130404101338.GK21804@intel.com> (raw)
In-Reply-To: <CAN+gG=Edb-iTLeafeDw+E33rJWthSM8Qr37yQJNOG9p45_rrbw@mail.gmail.com>
On Thu, Apr 04, 2013 at 12:01:23PM +0200, Benjamin Tissoires wrote:
> > One option is to provide acpi_get_gpio_all() that returns all GPIOs and
> > their corresponding types. That should allow clients like i2c-hid to find
> > the right GPIO (I'm hoping that there will be only one GpioInt associated
> > with these devices).
>
> That could do the trick.
Great.
> However, I won't be able to test it. I still don't have access to any
> ACPI 5 device with i2c-hid devices...
I have few such devices but none of them has GpioInt resources (they have
the interrupt line routed to ioapic), so I can't test the i2c-hid with
GpioInt either :-/
next prev parent reply other threads:[~2013-04-04 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 10:56 [PATCH] gpiolib-acpi: introduce acpi_get_gpio_by_index() helper Mika Westerberg
2013-04-03 11:04 ` Rafael J. Wysocki
2013-04-11 7:29 ` Mika Westerberg
2013-04-11 22:35 ` Linus Walleij
2013-04-12 6:57 ` Mika Westerberg
2013-04-04 9:19 ` Benjamin Tissoires
2013-04-04 9:38 ` Mika Westerberg
2013-04-04 9:42 ` Benjamin Tissoires
2013-04-04 9:57 ` Mika Westerberg
2013-04-04 10:01 ` Benjamin Tissoires
2013-04-04 10:13 ` Mika Westerberg [this message]
2013-04-11 22:33 ` Linus Walleij
2013-04-11 22:43 ` 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=20130404101338.GK21804@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=benjamin.tissoires@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=rafael.j.wysocki@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