| Message ID | 20230918093240.29824-3-bagasdotme@gmail.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | Documentation fixes for dpll subsystem | expand |
| Context | Check | Description |
|---|---|---|
| netdev/tree_selection | success | Not a local patch |
On 18/09/2023 10:32, Bagas Sanjaya wrote: > DPLL_CMD_PIN_GET netlink command output for mux-type pins looks ugly > with normal paragraph formatting. Format it as a code block instead. > > Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev> > --- > Documentation/driver-api/dpll.rst | 24 ++++++++++++------------ > 1 file changed, 12 insertions(+), 12 deletions(-) > > diff --git a/Documentation/driver-api/dpll.rst b/Documentation/driver-api/dpll.rst > index 01eb4de867036f..69670deb8c4e09 100644 > --- a/Documentation/driver-api/dpll.rst > +++ b/Documentation/driver-api/dpll.rst > @@ -119,19 +119,19 @@ with. > If a pin was registered with multiple parent pins, they behave like a > multiple output multiplexer. In this case output of a > ``DPLL_CMD_PIN_GET`` would contain multiple pin-parent nested > -attributes with current state related to each parent, like: > +attributes with current state related to each parent, like:: > > -'pin': [{{ > - 'clock-id': 282574471561216, > - 'module-name': 'ice', > - 'capabilities': 4, > - 'id': 13, > - 'parent-pin': [ > - {'parent-id': 2, 'state': 'connected'}, > - {'parent-id': 3, 'state': 'disconnected'} > - ], > - 'type': 'synce-eth-port' > - }}] > + 'pin': [{{ > + 'clock-id': 282574471561216, > + 'module-name': 'ice', > + 'capabilities': 4, > + 'id': 13, > + 'parent-pin': [ > + {'parent-id': 2, 'state': 'connected'}, > + {'parent-id': 3, 'state': 'disconnected'} > + ], > + 'type': 'synce-eth-port' > + }}] > > Only one child pin can provide its signal to the parent MUX-type pin at > a time, the selection is done by requesting change of a child pin state
diff --git a/Documentation/driver-api/dpll.rst b/Documentation/driver-api/dpll.rst index 01eb4de867036f..69670deb8c4e09 100644 --- a/Documentation/driver-api/dpll.rst +++ b/Documentation/driver-api/dpll.rst @@ -119,19 +119,19 @@ with. If a pin was registered with multiple parent pins, they behave like a multiple output multiplexer. In this case output of a ``DPLL_CMD_PIN_GET`` would contain multiple pin-parent nested -attributes with current state related to each parent, like: +attributes with current state related to each parent, like:: -'pin': [{{ - 'clock-id': 282574471561216, - 'module-name': 'ice', - 'capabilities': 4, - 'id': 13, - 'parent-pin': [ - {'parent-id': 2, 'state': 'connected'}, - {'parent-id': 3, 'state': 'disconnected'} - ], - 'type': 'synce-eth-port' - }}] + 'pin': [{{ + 'clock-id': 282574471561216, + 'module-name': 'ice', + 'capabilities': 4, + 'id': 13, + 'parent-pin': [ + {'parent-id': 2, 'state': 'connected'}, + {'parent-id': 3, 'state': 'disconnected'} + ], + 'type': 'synce-eth-port' + }}] Only one child pin can provide its signal to the parent MUX-type pin at a time, the selection is done by requesting change of a child pin state
DPLL_CMD_PIN_GET netlink command output for mux-type pins looks ugly with normal paragraph formatting. Format it as a code block instead. Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> --- Documentation/driver-api/dpll.rst | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-)