From: Amit Kucheria <amit.kucheria@linaro.org>
To: linux-kernel@vger.kernel.org, manivannan.sadhasivam@linaro.org
Subject: [PATCH 0/4] arm64 defconfig: enable additional led triggers
Date: Thu, 19 Oct 2017 02:27:20 +0530 [thread overview]
Message-ID: <cover.1508360121.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-10-18 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 20:57 Amit Kucheria [this message]
2017-10-18 20:57 ` [PATCH 1/4] arm64: defconfig: enable new trigger modes for leds Amit Kucheria
2017-10-19 15:24 ` Timur Tabi
2017-10-23 4:56 ` Amit Kucheria
2017-10-23 15:24 ` Timur Tabi
2017-10-23 23:11 ` Amit Kucheria
2017-10-24 2:30 ` Timur Tabi
2017-10-24 11:48 ` Manivannan Sadhasivam
2017-10-18 20:57 ` [PATCH 2/4] arm64: dts: qcom: apq8016-sbc: Allow USR4 LED to notify kernel panic Amit Kucheria
2017-10-18 20:57 ` [PATCH 3/4] arm64: dts: hisilicon: hi6220-hikey: Allow USR1 " Amit Kucheria
2017-10-18 20:57 ` [PATCH 4/4] arm64: dts: hisilicon: hi3660-hikey960: Allow USR4 " Amit Kucheria
[not found] ` <CAFGCpxy3v6Z5kTqDEF=mqEpSm2+7pn6jSrotx=sHVBmC=VH3Bw@mail.gmail.com>
2017-10-23 4:43 ` Amit Kucheria
2017-10-24 11:32 ` Guodong Xu
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.1508360121.git.amit.kucheria@linaro.org \
--to=amit.kucheria@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.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
Powered by JetHome