From: Linus Walleij <linus.walleij@linaro.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Irina Tirdea <irina.tirdea@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Octavian Purdila <octavian.purdila@intel.com>,
Cristina Ciocan <cristina.ciocan@intel.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2 0/3] Add ACPI support for pinctrl configuration
Date: Thu, 7 Apr 2016 19:48:57 +0200 [thread overview]
Message-ID: <CACRpkdZu1MFZ+0m7VUq8hArpjiESzjqaLvFDZHOK-JUidFtwvg@mail.gmail.com> (raw)
In-Reply-To: <20160407125634.GO1727@lahna.fi.intel.com>
On Thu, Apr 7, 2016 at 2:56 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> On Tue, Apr 05, 2016 at 06:33:23PM +0300, Irina Tirdea wrote:
>> Changes from v1:
>> - address code review comments regarding coding style, documentation
>> and fixes
>> - rewrote patch 3 ("pinctrl: Parse GpioInt/GpioIo resources") to
>> avoid using triple pointers
>> - define pinconf_generic_dt_node_to_map since it is used by pinctrl
>> sirf driver
>> - add dependency on PINCONF_GENERIC to the entire ACPI parsing code
>> - dropped first patch from the series since it got merged
>> ("pinctrl: Rename pinctrl_utils_dt_free_map to pinctrl_utils_free_map")
>>
>> Irina Tirdea (3):
>> pinctrl: pinconf-generic: Add ACPI support
>> pinctrl: Add ACPI support
>> pinctrl: Parse GpioInt/GpioIo resources
>
> The series looks good to me now,
>
> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> Of course this all depends on the decision whether this is the preferred
> way of controlling and muxing pins in ACPI.
I think the discussion is very interesting and intense right now so
let us see. We need to form some rough consensus before we
know how to proceed.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-04-07 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 15:33 [RFC PATCH v2 0/3] Add ACPI support for pinctrl configuration Irina Tirdea
2016-04-05 15:33 ` [RFC PATCH v2 1/3] pinctrl: pinconf-generic: Add ACPI support Irina Tirdea
[not found] ` <1459870406-15219-1-git-send-email-irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-05 15:33 ` [RFC PATCH v2 2/3] pinctrl: " Irina Tirdea
2016-04-07 12:56 ` [RFC PATCH v2 0/3] Add ACPI support for pinctrl configuration Mika Westerberg
2016-04-07 17:48 ` Linus Walleij [this message]
2016-04-05 15:33 ` [RFC PATCH v2 3/3] pinctrl: Parse GpioInt/GpioIo resources Irina Tirdea
2016-04-14 11:58 ` [RFC PATCH v2 0/3] Add ACPI support for pinctrl configuration Linus Walleij
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=CACRpkdZu1MFZ+0m7VUq8hArpjiESzjqaLvFDZHOK-JUidFtwvg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=cristina.ciocan@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=irina.tirdea@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=octavian.purdila@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).