On 05/10/2024 18:24, Daniel Golle wrote:
> Other than described in commit c94d1783136 ("dt-bindings: net: phy: Make
> LED active-low property common") the absence of the 'active-low'
> property means not to touch the polarity settings which are inherited
> from reset defaults, the bootloader or bootstrap configuration.
> Hence, in order to override a LED pin being active-high in case of the
> default, bootloader or bootstrap setting being active-low an additional
> property 'active-high' is required.
> Document that property and make it mutually exclusive to the existing
> 'active-low' property.
>
> Signed-off-by: Daniel Golle <daniel@xxxxxxxxxxxxxx>
> ---
> Documentation/devicetree/bindings/leds/common.yaml | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml
> index bf9a101e4d42..7c3cd7b7412e 100644
> --- a/Documentation/devicetree/bindings/leds/common.yaml
> +++ b/Documentation/devicetree/bindings/leds/common.yaml
> @@ -202,6 +202,12 @@ properties:
> #trigger-source-cells property in the source node.
> $ref: /schemas/types.yaml#/definitions/phandle-array
>
> + active-high:
> + type: boolean
> + description:
> + Makes LED active high. To turn the LED ON, line needs to be
> + set to high voltage instead of low.
> +
> active-low:
> type: boolean
> description:
> @@ -225,6 +231,14 @@ properties:
> Maximum timeout in microseconds after which the flash LED is turned off.
> Required for flash LED nodes with configurable timeout.
>
> +allOf:
> + - if:
> + required:
> + - active-low
> + then:
> + properties:
> + active-high: false
I read prior discussion, so indeed that is safest bet.
With the commit SHA fixed:
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx>
Best regards,
Krzysztof
