devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: chaochao2021666@163.com
Cc: pavel@ucw.cz, linux-leds@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	jan.kiszk@siemens.com, 464759471@qq.com,
	chao zeng <chao.zeng@siemens.com>
Subject: Re: [PATCH 1/3] leds:triggers:Extend the kernel panic LED trigger
Date: Tue, 7 Sep 2021 14:20:18 +0200	[thread overview]
Message-ID: <20210907142018.45b2d114@dellmb> (raw)
In-Reply-To: <20210906135320.23134-1-chaochao2021666@163.com>

On Mon,  6 Sep 2021 21:53:18 +0800
chaochao2021666@163.com wrote:

> From: chao zeng <chao.zeng@siemens.com>
> 
> This commit extend panic trigger, add two new panic trigger
> "panic_on" and "panic_off" and keep the "panic" compatible with
> "panic_blink".
> 
> All the led on the "panic_on" would light and on
> the "panic_off" would turn off

We don't wont gazillion triggers, each for every possible setting.

Instead extend the existing panic trigger to have another sysfs setting
where you can set this behavior.
  echo panic >trigger
  echo blink >on_panic
So the on_panic file can accept "on", "off" or "blink".

Alternatively a pattern could be set as in the ledtrig-pattern trigger.

Also your patches do not use correct spacing in commit titles:
  leds:triggers:Extend the kernel panic LED trigger
should instead be
  leds: triggers: Extend the kernel panic LED trigger

Marek

  parent reply	other threads:[~2021-09-07 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 13:53 [PATCH 1/3] leds:triggers:Extend the kernel panic LED trigger chaochao2021666
2021-09-06 13:53 ` [PATCH 2/3] leds:gpio:Add the support for "panic-indicator-on" and "panic-indicator-off" chaochao2021666
2021-09-06 13:53 ` [PATCH 3/3] dt-bindings:leds:Extend panic led state chaochao2021666
2021-09-07 12:20 ` Marek Behún [this message]
     [not found]   ` <12734c2f.116c.17bc3147806.Coremail.chaochao2021666@163.com>
2021-09-08  5:29     ` [PATCH 1/3] leds:triggers:Extend the kernel panic LED trigger Jan Kiszka

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=20210907142018.45b2d114@dellmb \
    --to=kabel@kernel.org \
    --cc=464759471@qq.com \
    --cc=chao.zeng@siemens.com \
    --cc=chaochao2021666@163.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jan.kiszk@siemens.com \
    --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).