From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Lv Zheng <lv.zheng@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>, Lv Zheng <zetalog@gmail.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: [PATCH 2/2] gpio / ACPI: Use pin index and bit length
Date: Wed, 24 Sep 2014 15:29:58 +0200 [thread overview]
Message-ID: <4782234.lB9SpkJVXe@vostro.rjw.lan> (raw)
In-Reply-To: <CACRpkdbdY2JFDbYWaqZ2KepKUv8fQnNAR4bH0KVjVS8zcMbFoA@mail.gmail.com>
On Wednesday, September 24, 2014 01:25:03 PM Linus Walleij wrote:
> On Tue, Sep 23, 2014 at 12:27 PM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> > On Tue, Sep 23, 2014 at 10:35:54AM +0800, Lv Zheng wrote:
> >> From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> >>
> >> Fix code when the operation region callback is for an gpio, which
> >> is not at index 0 and for partial pins in a GPIO definition.
> >> For example:
> >> Name (GMOD, ResourceTemplate ()
> >> {
> >> //3 Outputs that define the Power mode of the device
> >> GpioIo (Exclusive, PullDown, , , , "\\_SB.GPI2") {10, 11, 12}
> >> })
> >> }
> >>
> >> If opregion callback calls is for:
> >> - Set pin 10, then address = 0 and bit length = 1
> >> - Set pin 11, then address = 1 and bit length = 1
> >> - Set for both pin 11 and pin 12, then address = 1, bit length = 2
> >>
> >> This change requires updated ACPICA gpio operation handler code to
> >> send the pin index and bit length.
> >>
> >> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> >> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> >
> > Adding the GPIO maintainers since we need their ACK to get this merged
> > through ACPI tree.
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> When it comes to ACPI GPIO stuff I basically trust Rafael, Mika
> and Darren to do the right thing. I'm trying to learn a bit as we go.
Thanks! We're doing our best. :-)
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-09-24 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 2:35 [PATCH 1/2] ACPICA: Update to GPIO region handler interface Lv Zheng
2014-09-23 2:35 ` [PATCH 2/2] gpio / ACPI: Use pin index and bit length Lv Zheng
2014-09-23 10:27 ` Mika Westerberg
2014-09-23 15:32 ` Rafael J. Wysocki
2014-09-23 15:29 ` Mika Westerberg
2014-09-23 15:52 ` Rafael J. Wysocki
2014-09-23 15:30 ` Srinivas Pandruvada
2014-09-24 11:25 ` Linus Walleij
2014-09-24 13:29 ` Rafael J. Wysocki [this message]
2014-09-24 21:22 ` [PATCH 1/2] ACPICA: Update to GPIO region handler interface 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=4782234.lB9SpkJVXe@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=acourbot@nvidia.com \
--cc=len.brown@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=zetalog@gmail.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