From: Jan Kiszka <jan.kiszka@siemens.com>
To: chaochao2021666 <chaochao2021666@163.com>,
"Marek Behún" <kabel@kernel.org>
Cc: pavel@ucw.cz, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
464759471@qq.com, chao zeng <chao.zeng@siemens.com>
Subject: Re: [PATCH 1/3] leds:triggers:Extend the kernel panic LED trigger
Date: Wed, 8 Sep 2021 07:29:52 +0200 [thread overview]
Message-ID: <69207a27-e66f-425b-861f-c2fb1c8ab65d@siemens.com> (raw)
In-Reply-To: <12734c2f.116c.17bc3147806.Coremail.chaochao2021666@163.com>
On 08.09.21 03:45, chaochao2021666 wrote:
> Dear Marek
>
>
> For other types of led could be set at the userspace level. But for the
> panic,
> maybe it would trigger at kernel space during the kernel boot up.
>
> And currently only blink to indicate the error. we need more kinds of
> type to indicate the error.
>
> we have two leds in the panic trigger group, all in the panic only one
> behavior-- blink.
> we need different panic led behavior, so extend the led behavior. I
> think add more types of
> LED behavior could be helpful.
>
To make it even clearer, there are three issues to solve for us:
One is that we have two LEDs mixing a color, red and green, and the
obviously desired panic color it red, not orange.
The other is that the desired state in an error case is non-blinking,
just on (in line with what our U-Boot will do in case the boot fails).
And as we need that behavior prior to userspace, it should be
configurable via DT. But that does not exclude extending the sysfs
interface as well with the new options.
Jan
> BRs
> Chao
>
>
> At 2021-09-07 20:20:18, "Marek Behún" <kabel@kernel.org> wrote:
>>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
>
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2021-09-08 5:30 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 ` [PATCH 1/3] leds:triggers:Extend the kernel panic LED trigger Marek Behún
[not found] ` <12734c2f.116c.17bc3147806.Coremail.chaochao2021666@163.com>
2021-09-08 5:29 ` Jan Kiszka [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=69207a27-e66f-425b-861f-c2fb1c8ab65d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=464759471@qq.com \
--cc=chao.zeng@siemens.com \
--cc=chaochao2021666@163.com \
--cc=devicetree@vger.kernel.org \
--cc=kabel@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).