|
|
|
Re: [PATCH 1/2] Documentation/gpio.txt: Explain expected pinctrl interaction | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
On Sun, Feb 19, 2012 at 11:27:42PM -0700, Stephen Warren wrote: > Update gpio.txt based on recent discussions regarding interaction with the > pinctrl subsystem. > > Previously, gpio_request() was described as explicitly not performing any > required mux setup operations etc. > > Now, gpio_request() is explicitly as explicitly performing any required mux > setup operations where possible. In the case it isn't, platform code is > required to have set up any required muxing or other configuration prior to > gpio_request() being called, in order to maintain the same semantics. So what if you need to have the pin as a GPIO, manipulate it as a GPIO, and then hand it off to a special function, and then take it back as a GPIO before you shut the special function down ? -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Site Home] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Linux FS] [Photo] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]
![]() |