linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
	Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: leds: common: Add mmc0 as default trigger
Date: Mon, 14 Sep 2020 12:20:10 -0600	[thread overview]
Message-ID: <20200914182010.GA4172388@bogus> (raw)
In-Reply-To: <20200830111115.32623-1-krzk@kernel.org>

On Sun, Aug 30, 2020 at 01:11:15PM +0200, Krzysztof Kozlowski wrote:
> MMC could be a default trigger so add a pattern to match it and fix
> dtbs_check warnings like:
> 
>   arch/arm/boot/dts/exynos4412-odroidx.dt.yaml: leds: led2:linux,default-trigger:0:
>     'mmc0' is not one of ['backlight', 'default-on', 'heartbeat', 'disk-activity', 'ide-disk', 'timer', 'pattern']
>     From schema: Documentation/devicetree/bindings/leds/leds-gpio.yaml

The preference is to move from 'linux,default-trigger' to 'function' 
with some standardization of the names or use the trigger-source binding.

> 
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
>  .../devicetree/bindings/leds/common.yaml      | 39 ++++++++++---------
>  1 file changed, 20 insertions(+), 19 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/leds/common.yaml b/Documentation/devicetree/bindings/leds/common.yaml
> index a2a541bca73c..6b38f9f3792c 100644
> --- a/Documentation/devicetree/bindings/leds/common.yaml
> +++ b/Documentation/devicetree/bindings/leds/common.yaml
> @@ -78,25 +78,26 @@ properties:
>        This parameter, if present, is a string defining the trigger assigned to
>        the LED.
>      $ref: /schemas/types.yaml#definitions/string
> -
> -    enum:
> -        # LED will act as a back-light, controlled by the framebuffer system
> -      - backlight
> -        # LED will turn on (but for leds-gpio see "default-state" property in
> -        # Documentation/devicetree/bindings/leds/leds-gpio.yaml)
> -      - default-on
> -        # LED "double" flashes at a load average based rate
> -      - heartbeat
> -        # LED indicates disk activity
> -      - disk-activity
> -        # LED indicates IDE disk activity (deprecated), in new implementations
> -        # use "disk-activity"
> -      - ide-disk
> -        # LED flashes at a fixed, configurable rate
> -      - timer
> -        # LED alters the brightness for the specified duration with one software
> -        # timer (requires "led-pattern" property)
> -      - pattern
> +    oneOf:
> +      - enum:
> +            # LED will act as a back-light, controlled by the framebuffer system
> +          - backlight
> +            # LED will turn on (but for leds-gpio see "default-state" property in
> +            # Documentation/devicetree/bindings/leds/leds-gpio.yaml)
> +          - default-on
> +            # LED "double" flashes at a load average based rate
> +          - heartbeat
> +            # LED indicates disk activity
> +          - disk-activity
> +            # LED indicates IDE disk activity (deprecated), in new implementations
> +            # use "disk-activity"
> +          - ide-disk
> +            # LED flashes at a fixed, configurable rate
> +          - timer
> +            # LED alters the brightness for the specified duration with one software
> +            # timer (requires "led-pattern" property)
> +          - pattern
> +      - pattern: "^mmc[0-9]+$"
>  
>    led-pattern:
>      description: |
> -- 
> 2.17.1
> 

      reply	other threads:[~2020-09-14 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 11:11 [PATCH] dt-bindings: leds: common: Add mmc0 as default trigger Krzysztof Kozlowski
2020-09-14 18:20 ` Rob Herring [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200914182010.GA4172388@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).