On Fri, May 12, 2017 at 10:01:50AM +0200, Uwe Kleine-König wrote: > On Fri, May 12, 2017 at 11:05:38AM +0800, Shawn Guo wrote: > > I went through the code around requesting a pin, and found that we need > > to call pinctrl_request_gpio() from gpio driver to get the result you > > want. In that case, pin_request() will be called with a valid > > gpio_range as below. > > > > pinctrl_request_gpio() > > pinmux_request_gpio() > > pin_request(..., gpio_range) > > > > Right now, pin_request() is being called with a NULL gpio_range from > > pinmux_enable_setting(). That gets us the mux_owner rather than > > gpio_owner for the pin. > > But then again I cannot mux a pin to a different function when the gpio > is requested, right? You will need to free the GPIO before muxing it to a different function, I think. Shawn -- 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