Re: [PATCH v2 1/1] gpio: merrifield: Introduce GPIO driver to support Merrifield

[Linus Walleij <linus.walleij@xxxxxxxxxx>]

On Fri, Jul 8, 2016 at 6:54 PM, Wood, Brian J <brian.j.wood@xxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html