From: amit.kucheria@linaro.org (Amit Kucheria)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] arm64: defconfig: enable additional led triggers
Date: Mon, 6 Nov 2017 12:38:12 +0530 [thread overview]
Message-ID: <cover.1509951550.git.amit.kucheria@linaro.org> (raw)
This patchset enables the kernel panic and disk-activity trigger for LEDs
and then enables the panic trigger for three 96Boards - DB410c, Hikey and
Hikey960.
DB410c and Hikey panic behaviour has been tested by triggering a panic
through /proc/sysrq-trigger, while Hikey960 is only compile-tested.
Amit Kucheria (4):
arm64: defconfig: enable new trigger modes for leds
arm64: dts: qcom: apq8016-sbc: Allow USR4 LED to notify kernel panic
arm64: dts: hisilicon: hi6220-hikey: Allow USR1 LED to notify kernel
panic
arm64: dts: hisilicon: hi3660-hikey960: Allow USR4 LED to notify
kernel panic
arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 1 +
arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 +
arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 1 +
arch/arm64/configs/defconfig | 2 ++
4 files changed, 5 insertions(+)
--
2.7.4
next reply other threads:[~2017-11-06 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 7:08 Amit Kucheria [this message]
2017-11-06 7:08 ` [PATCH v2 1/4] arm64: defconfig: enable new trigger modes for leds Amit Kucheria
2017-11-06 7:08 ` [PATCH v2 2/4] arm64: dts: qcom: apq8016-sbc: Allow USR4 LED to notify kernel panic Amit Kucheria
2017-11-06 7:08 ` [PATCH v2 3/4] arm64: dts: hisilicon: hi6220-hikey: Allow USR1 " Amit Kucheria
2017-11-06 7:08 ` [PATCH v2 4/4] arm64: dts: hisilicon: hi3660-hikey960: Allow USR4 " Amit Kucheria
2017-12-06 8:57 ` [PATCH v2 0/4] arm64: defconfig: enable additional led triggers Amit Kucheria
2017-12-21 15:16 ` Arnd Bergmann
2018-01-02 7:19 ` Amit Kucheria
2018-01-04 16:54 ` Arnd Bergmann
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=cover.1509951550.git.amit.kucheria@linaro.org \
--to=amit.kucheria@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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