lkml.org 
[lkml]   [2019]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v4 1/4] dt-bindings: net: phy: Add subnode for LED configuration
    Date
    The LED behavior of some Ethernet PHYs is configurable. Add an
    optional 'leds' subnode with a child node for each LED to be
    configured. The binding aims to be compatible with the common
    LED binding (see devicetree/bindings/leds/common.txt).

    A LED can be configured to be 'on' when a link with a certain speed
    is active, or to blink on RX/TX activity. For the configuration to
    be effective it needs to be supported by the hardware and the
    corresponding PHY driver.

    Suggested-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
    ---
    Changes in v4:
    - patch added to the series
    ---
    .../devicetree/bindings/net/ethernet-phy.yaml | 47 +++++++++++++++++++
    1 file changed, 47 insertions(+)

    diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
    index f70f18ff821f..81c5aacc89a5 100644
    --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
    +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
    @@ -153,6 +153,38 @@ properties:
    Delay after the reset was deasserted in microseconds. If
    this property is missing the delay will be skipped.

    +patternProperties:
    + "^leds$":
    + type: object
    + description:
    + Subnode with configuration of the PHY LEDs.
    +
    + patternProperties:
    + "^led@[0-9]+$":
    + type: object
    + description:
    + Subnode with the configuration of a single PHY LED.
    +
    + properties:
    + reg:
    + description:
    + The ID number of the LED, typically corresponds to a hardware ID.
    + $ref: "/schemas/types.yaml#/definitions/uint32"
    +
    + linux,default-trigger:
    + description:
    + This parameter, if present, is a string specifying the trigger
    + assigned to the LED. Supported triggers are:
    + "phy_link_10m_active" - LED will be on when a 10Mb/s link is active
    + "phy_link_100m_active" - LED will be on when a 100Mb/s link is active
    + "phy_link_1g_active" - LED will be on when a 1Gb/s link is active
    + "phy_link_10g_active" - LED will be on when a 10Gb/s link is active
    + "phy_activity" - LED will blink when data is received or transmitted
    + $ref: "/schemas/types.yaml#/definitions/string"
    +
    + required:
    + - reg
    +
    required:
    - reg

    @@ -173,5 +205,20 @@ examples:
    reset-gpios = <&gpio1 4 1>;
    reset-assert-us = <1000>;
    reset-deassert-us = <2000>;
    +
    + leds {
    + #address-cells = <1>;
    + #size-cells = <0>;
    +
    + led@0 {
    + reg = <0>;
    + linux,default-trigger = "phy_link_1g_active";
    + };
    +
    + led@1 {
    + reg = <1>;
    + linux,default-trigger = "phy_activity";
    + };
    + };
    };
    };
    --
    2.22.0.770.g0f2c4a37fd-goog
    \
     
     \ /
      Last update: 2019-08-01 21:08    [W:4.465 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site