From: Linus Walleij <linus.walleij@linaro.org>
To: "Wood, Brian J" <brian.j.wood@intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
David Cohen <david.a.cohen@linux.intel.com>,
"Koskinen, Ilkka" <ilkka.koskinen@intel.com>
Subject: Re: [PATCH v2 1/1] gpio: merrifield: Introduce GPIO driver to support Merrifield
Date: Mon, 11 Jul 2016 11:12:37 +0200 [thread overview]
Message-ID: <CACRpkdYoq_i3cks80wrMLxSGHV77a25r11D5r=RAAAePNEmd2Q@mail.gmail.com> (raw)
In-Reply-To: <89AE17FDD09DD746ACFB52B7F3E0AF788895FA89@ORSMSX115.amr.corp.intel.com>
On Fri, Jul 8, 2016 at 6:54 PM, Wood, Brian J <brian.j.wood@intel.com> wrote:
> +Ilkka (he's investigating adding in pinctrl code for getting/setting the GPIO pins on BXT platform)
>
> Ilkka, not being too familiar with pinctrl would there need to be more added to these functions
> mrfld_gpio_get()/mrfld_gpio_set() for the mux'ing needs we were discussing for Brillo?
I don't know if that was intended to be internal but as it happens I
keep an eye out for
Brillo. I have been including people from Google in the review of the
new chardev
ABI that will be merged for v4.8.
If special userspace concerns are needed for Brillo or any other IoT business, I
would be happy if we could do it here on the GPIO list, so we all have a good
picture of what IoT/Brillo/makespaces need for doing their GPIO business
from userspace.
I'd be especially scared if userspace need to do muxing beyond "set as GPIO"
but whatever comes up, we need some structure to it.
> Andy, the code looks good. +1 from me :-)
I'm recording that as an Acked-by in the changelog.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-07-11 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 11:08 [PATCH v2 1/1] gpio: merrifield: Introduce GPIO driver to support Merrifield Andy Shevchenko
2016-07-08 13:16 ` Mika Westerberg
2016-07-08 16:54 ` Wood, Brian J
2016-07-08 17:05 ` Andy Shevchenko
2016-07-11 9:12 ` Linus Walleij [this message]
2016-07-11 4:55 ` Mika Westerberg
2016-07-11 9:13 ` Linus Walleij
2016-07-11 9:43 ` Andy Shevchenko
2016-07-11 10:08 ` Andy Shevchenko
2016-07-11 9:06 ` Linus Walleij
2016-07-11 9:45 ` Andy Shevchenko
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='CACRpkdYoq_i3cks80wrMLxSGHV77a25r11D5r=RAAAePNEmd2Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brian.j.wood@intel.com \
--cc=david.a.cohen@linux.intel.com \
--cc=ilkka.koskinen@intel.com \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.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;
as well as URLs for NNTP newsgroup(s).