Skip to content

Commit 22f3e90

Browse files
kwillis01jeevantelukula
authored andcommitted
refactor(pm_wakeup_sources): Fix inconsistent style for DTS node
For the MCU GPIO wakeup node, there is an explanation of what each property does. The explanation mixed different styles. Fix the styles and explanation to be consistent. Signed-off-by: Kendall Willis <[email protected]>
1 parent fc4af37 commit 22f3e90

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

source/linux/Foundational_Components/Power_Management/pm_wakeup_sources.rst

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -364,7 +364,8 @@ MCU GPIO
364364
wakeup-source;
365365
};
366366
367-
#. The label is the descriptive name of the key. The string will reflect under /proc/interrupts as:
367+
#. label: Descriptive name of the switch node. If the MCU GPIO node is setup
368+
correctly, the label will appear under /proc/interrupts:
368369

369370
.. code-block:: console
370371
@@ -373,8 +374,9 @@ MCU GPIO
373374
374375
#. linux,code: Keycode to emit.
375376
#. gpios: the gpio required to be used as the gpio-key.
376-
#. The `wakeup-source <https://www.kernel.org/doc/Documentation/devicetree/bindings/power/wakeup-source.txt>`__ property describes
377-
devices which have wakeup capability.
377+
#. wakeup-source:
378+
`wakeup-source <https://www.kernel.org/doc/Documentation/devicetree/bindings/power/wakeup-source.txt>`__
379+
property describes devices which have wakeup capability.
378380

379381
This indicates that gpio_keys can wake-up the system from Deep Sleep or MCU Only mode.
380382

0 commit comments

Comments
 (0)