bartoszek/zephyr
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

dts: regulator: Fix reoccurring typo in properties

Browse Source 
Corrects 'propably' to 'probably' in the regulator devicetree
bindings.

Signed-off-by: Ricardo Rivera-Matos <ricardo.rivera-matos@cirrus.com>
This commit is contained in:
Ricardo Rivera-Matos 2023-09-13 13:06:56 -05:00 committed by Anas Nashif
parent c709b3d97f
commit 4c04f4488a
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
dts/bindings/regulator/regulator.yaml
View File

@ -147,7 +147,7 @@ properties:
type: int
description: |
Set over current error limit. This is a limit where part of the hardware
propably is malfunctional and damage prevention is requested. Zero can be
probably is malfunctional and damage prevention is requested. Zero can be
passed to disable error detection and value '1' indicates that detection
should be enabled but limit setting can be omitted.
@ -172,7 +172,7 @@ properties:
type: int
description: |
Set over voltage error limit. This is a limit where part of the hardware
propably is malfunctional and damage prevention is requested Zero can be
probably is malfunctional and damage prevention is requested Zero can be
passed to disable error detection and value '1' indicates that detection
should be enabled but limit setting can be omitted. Limit is given as
microvolt offset from voltage set to regulator.
@ -200,7 +200,7 @@ properties:
type: int
description: |
Set under voltage error limit. This is a limit where part of the hardware
propably is malfunctional and damage prevention is requested Zero can be
probably is malfunctional and damage prevention is requested Zero can be
passed to disable error detection and value '1' indicates that detection
should be enabled but limit setting can be omitted. Limit is given as
microvolt offset from voltage set to regulator.
@ -227,7 +227,7 @@ properties:
type: int
description: |
Set over temperature error limit. This is a limit where part of the
hardware propably is malfunctional and damage prevention is requested Zero
hardware probably is malfunctional and damage prevention is requested Zero
can be passed to disable error detection and value '1' indicates that
detection should be enabled but limit setting can be omitted.