Commit 0cca6c89 authored by Ludovic Desroches's avatar Ludovic Desroches Committed by Linus Walleij
Browse files

pinctrl: generic: update references to Documentation/pinctrl.txt 



Update deprecated references to Documentation/pinctrl.txt since it has been
moved to Documentation/driver-api/pinctl.rst.

Signed-off-by: default avatarLudovic Desroches <ludovic.desroches@o2linux.fr>
Fixes: 5a9b7383 ("pinctrl.txt: move it to the driver-api book")
Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
parent 5d996132

Documentation/gpio/gpio-legacy.txt

+1 −1
Original line number Diff line number Diff line
@@ -459,7 +459,7 @@ pin controller? 


This is done by registering "ranges" of pins, which are essentially

cross-reference tables. These are described in

Documentation/pinctrl.txt

Documentation/driver-api/pinctl.rst



While the pin allocation is totally managed by the pinctrl subsystem,

gpio (under gpiolib) is still maintained by gpio drivers. It may happen

MAINTAINERS

+1 −1
Original line number Diff line number Diff line
@@ -10375,7 +10375,7 @@ L: linux-gpio@vger.kernel.org 
T:	git git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git

S:	Maintained

F:	Documentation/devicetree/bindings/pinctrl/

F:	Documentation/pinctrl.txt

F:	Documentation/driver-api/pinctl.rst

F:	drivers/pinctrl/

F:	include/linux/pinctrl/

include/linux/device.h

+1 −1
Original line number Diff line number Diff line
@@ -843,7 +843,7 @@ struct dev_links_info { 
 * 		hibernation, system resume and during runtime PM transitions

 * 		along with subsystem-level and driver-level callbacks.

 * @pins:	For device pin management.

 *		See Documentation/pinctrl.txt for details.

 *		See Documentation/driver-api/pinctl.rst for details.

 * @msi_list:	Hosts MSI descriptors

 * @msi_domain: The generic MSI domain this device is using.

 * @numa_node:	NUMA node this device is close to.

include/linux/pinctrl/pinconf-generic.h

+2 −2
Original line number Diff line number Diff line
@@ -81,8 +81,8 @@ 
 * 	it.

 * @PIN_CONFIG_OUTPUT: this will configure the pin as an output and drive a

 * 	value on the line. Use argument 1 to indicate high level, argument 0 to

 * 	indicate low level. (Please see Documentation/pinctrl.txt, section

 * 	"GPIO mode pitfalls" for a discussion around this parameter.)

 *	indicate low level. (Please see Documentation/driver-api/pinctl.rst,

 *	section "GPIO mode pitfalls" for a discussion around this parameter.)

 * @PIN_CONFIG_POWER_SOURCE: if the pin can select between different power

 *	supplies, the argument to this parameter (on a custom format) tells

 *	the driver which alternative power source to use.

CRA Git | Maintained and supported by SUSTech CRA and CCSE