svn commit: r346512 - in stable/11/share/man: man4 man9
Ian Lepore
ian at FreeBSD.org
Mon Apr 22 02:37:48 UTC 2019
Author: ian
Date: Mon Apr 22 02:37:46 2019
New Revision: 346512
URL: https://svnweb.freebsd.org/changeset/base/346512
Log:
MFC r330358, r330360
r330358: Minor changes to wording.
r330360: Minor (mostly) wording changes.
Modified:
stable/11/share/man/man4/fdt_pinctrl.4
stable/11/share/man/man9/fdt_pinctrl.9
Directory Properties:
stable/11/ (props changed)
Modified: stable/11/share/man/man4/fdt_pinctrl.4
==============================================================================
--- stable/11/share/man/man4/fdt_pinctrl.4 Mon Apr 22 01:08:14 2019 (r346511)
+++ stable/11/share/man/man4/fdt_pinctrl.4 Mon Apr 22 02:37:46 2019 (r346512)
@@ -24,7 +24,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd March 2, 2018
+.Dd March 3, 2018
.Dt "FDT_PINCTRL" 4
.Os
.Sh NAME
@@ -36,13 +36,13 @@
.Pp
Pin multiplexing is a technology used to re-purpose a single
physical connection (depending on chip packaging it may be
-pin, ball, or pad) to pull signal from one of SoC internal
-controllers to peripheral devices.
+pin, ball, or pad) by routing its signal to any one of several
+different SoC internal devices.
For example, based on the actual device design, a single SoC chip
-pin can perform any of these roles: SPI clock, I2C
+pin might perform any of these roles: SPI clock, I2C
data, GPIO pin, or PWM signal.
Function selection is performed by the pinmux controller, a SoC
-hardware block, usually controlled a set of registers.
+hardware block which is usually controlled by a set of registers.
Pinmux controller capabilities and register format depend
on the actual hardware implementation.
.Pp
@@ -104,11 +104,11 @@ backlight at 7f000000 {
}
.Ed
.Pp
-The pinctrl driver should implement FDT_PINCTRL_CONFIGURE
-method, register itself as pin configuration handler by
+The pinctrl driver should implement the FDT_PINCTRL_CONFIGURE
+method, register itself as a pin configuration handler by
calling fdt_pinctrl_register function, and call
.Xr fdt_pinctrl_configure_tree 9
-to configure pins for all enabled devices (device where
+to configure pins for all enabled devices (devices where
the "status" property is not set to "disabled").
.Sh SEE ALSO
.Xr fdt_pinctrl 9
Modified: stable/11/share/man/man9/fdt_pinctrl.9
==============================================================================
--- stable/11/share/man/man9/fdt_pinctrl.9 Mon Apr 22 01:08:14 2019 (r346511)
+++ stable/11/share/man/man9/fdt_pinctrl.9 Mon Apr 22 02:37:46 2019 (r346512)
@@ -28,7 +28,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd March 2, 2018
+.Dd March 3, 2018
.Dt fdt_pinctrl 9
.Os
.Sh NAME
@@ -50,15 +50,17 @@ provides an API for manipulating I/O pin configuration
pinmux controllers and pinmux clients.
On the controller side, the standard newbus probe and
attach methods are implemented.
-This driver also implements the
-.Fn fdt_pinctrl_configure
-method, in which it calls the
+As part of handling attach, it calls the
.Fn fdt_pinctrl_register
function to register itself as a pinmux controller.
Then
.Fn fdt_pinctrl_configure_tree
is used to walk the device tree and configure pins specified by the pinctrl-0
property for all active devices.
+The driver also implements the
+.Fn fdt_pinctrl_configure
+method, which allows client devices to change their
+pin configurations after startup.
If a client device requires a pin configuration change at some
point of its lifecycle, it uses the
.Fn fdt_pinctrl_configure
@@ -84,14 +86,9 @@ registers a pinctrl driver so that it can be used by o
.Fn fdt_pinctrl_configure
or
.Fn fdt_pinctrl_configure_by_name .
-The
-.Fa pinprop
-argument is the name of a property that
-identifies each descendant of the pinctrl
-node.
-The pinctrl node is a pin configuration
-node whose xref phandle can be passed to
-.Fn FDT_PINCTRL_CONFIGURE .
+It also registers each child node of the pinctrl driver's node which contains
+a property with the name given in
+.Fa pinprop .
If
.Fa pinprop
is
More information about the svn-src-stable
mailing list