lkml.org 
[lkml]   [2022]   [Jun]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.17 117/772] regulator: mt6315: Enforce regulator-compatible, not name
    Date
    From: Nícolas F. R. A. Prado <nfraprado@collabora.com>

    [ Upstream commit 6d435a94ba5bb4f2ad381c0828fbae89c66b50fe ]

    The MT6315 PMIC dt-binding should enforce that one of the valid
    regulator-compatible is set in each regulator node. However it was
    mistakenly matching against regulator-name instead.

    Fix the typo. This not only fixes the compatible verification, but also
    lifts the regulator-name restriction, so that more meaningful names can
    be set for each platform.

    Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
    Link: https://lore.kernel.org/r/20220429201325.2205799-1-nfraprado@collabora.com
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>
    ---
    .../devicetree/bindings/regulator/mt6315-regulator.yaml | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    diff --git a/Documentation/devicetree/bindings/regulator/mt6315-regulator.yaml b/Documentation/devicetree/bindings/regulator/mt6315-regulator.yaml
    index 61dd5af80db6..5d2d989de893 100644
    --- a/Documentation/devicetree/bindings/regulator/mt6315-regulator.yaml
    +++ b/Documentation/devicetree/bindings/regulator/mt6315-regulator.yaml
    @@ -31,7 +31,7 @@ properties:
    $ref: "regulator.yaml#"

    properties:
    - regulator-name:
    + regulator-compatible:
    pattern: "^vbuck[1-4]$"

    additionalProperties: false
    --
    2.35.1


    \
     
     \ /
      Last update: 2022-06-07 22:39    [W:3.990 / U:0.852 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site