From: Michal Simek <michal.simek@xilinx.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
michal.simek@xilinx.com, Rob Herring <robh+dt@kernel.org>
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
daniel.thompson@linaro.org, amit.kucheria@linaro.org,
linus.walleij@linaro.org, koen.kooi@linaro.org,
nicolas.dechesne@linaro.org
Subject: Re: [PATCH v3 6/7] arm64: dts: xilinx: ultra96: Standardize LED labels and triggers
Date: Fri, 21 Dec 2018 07:50:29 +0100 [thread overview]
Message-ID: <9f4f05cb-f326-a4e3-e306-cfbf64b629b4@xilinx.com> (raw)
In-Reply-To: <20181221023708.GC3233@Mani-XPS-13-9360>
On 21. 12. 18 3:37, Manivannan Sadhasivam wrote:
> On Mon, Oct 29, 2018 at 03:12:44PM +0530, Manivannan Sadhasivam wrote:
>> For all 96Boards, the following standard is used for onboard LEDs.
>>
>> green:user1 default-trigger: heartbeat
>> green:user2 default-trigger: mmc0/disk-activity(onboard-storage)
>> green:user3 default-trigger: mmc1 (SD-card)
>> green:user4 default-trigger: none, panic-indicator
>> yellow:wlan default-trigger: phy0tx
>> blue:bt default-trigger: hci0-power
>>
>> So lets adopt the same for Ultra96, which is one of the 96Boards
>> CE and AI platform. Since the WLAN and BT LEDs are hardwired onboard,
>> consolidate only User LEDs.
>>
>
> Hello,
>
> Any update on this patch?
I am still waiting for reaction from Rob.
We are keep trying to keep backward compatibility and this patch is
breaking it that's why I want to know DT guys reaction on this change.
Thanks,
Michal
WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <michal.simek@xilinx.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
<michal.simek@xilinx.com>, Rob Herring <robh+dt@kernel.org>
Cc: <linux-leds@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-rockchip@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>, <linux-soc@vger.kernel.org>,
<daniel.thompson@linaro.org>, <amit.kucheria@linaro.org>,
<linus.walleij@linaro.org>, <koen.kooi@linaro.org>,
<nicolas.dechesne@linaro.org>
Subject: Re: [PATCH v3 6/7] arm64: dts: xilinx: ultra96: Standardize LED labels and triggers
Date: Fri, 21 Dec 2018 07:50:29 +0100 [thread overview]
Message-ID: <9f4f05cb-f326-a4e3-e306-cfbf64b629b4@xilinx.com> (raw)
In-Reply-To: <20181221023708.GC3233@Mani-XPS-13-9360>
On 21. 12. 18 3:37, Manivannan Sadhasivam wrote:
> On Mon, Oct 29, 2018 at 03:12:44PM +0530, Manivannan Sadhasivam wrote:
>> For all 96Boards, the following standard is used for onboard LEDs.
>>
>> green:user1 default-trigger: heartbeat
>> green:user2 default-trigger: mmc0/disk-activity(onboard-storage)
>> green:user3 default-trigger: mmc1 (SD-card)
>> green:user4 default-trigger: none, panic-indicator
>> yellow:wlan default-trigger: phy0tx
>> blue:bt default-trigger: hci0-power
>>
>> So lets adopt the same for Ultra96, which is one of the 96Boards
>> CE and AI platform. Since the WLAN and BT LEDs are hardwired onboard,
>> consolidate only User LEDs.
>>
>
> Hello,
>
> Any update on this patch?
I am still waiting for reaction from Rob.
We are keep trying to keep backward compatibility and this patch is
breaking it that's why I want to know DT guys reaction on this change.
Thanks,
Michal
WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <michal.simek@xilinx.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
<michal.simek@xilinx.com>, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, daniel.thompson@linaro.org,
linux-arm-msm@vger.kernel.org, linus.walleij@linaro.org,
linux-kernel@vger.kernel.org, amit.kucheria@linaro.org,
linux-rockchip@lists.infradead.org, koen.kooi@linaro.org,
linux-leds@vger.kernel.org, nicolas.dechesne@linaro.org,
linux-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 6/7] arm64: dts: xilinx: ultra96: Standardize LED labels and triggers
Date: Fri, 21 Dec 2018 07:50:29 +0100 [thread overview]
Message-ID: <9f4f05cb-f326-a4e3-e306-cfbf64b629b4@xilinx.com> (raw)
In-Reply-To: <20181221023708.GC3233@Mani-XPS-13-9360>
On 21. 12. 18 3:37, Manivannan Sadhasivam wrote:
> On Mon, Oct 29, 2018 at 03:12:44PM +0530, Manivannan Sadhasivam wrote:
>> For all 96Boards, the following standard is used for onboard LEDs.
>>
>> green:user1 default-trigger: heartbeat
>> green:user2 default-trigger: mmc0/disk-activity(onboard-storage)
>> green:user3 default-trigger: mmc1 (SD-card)
>> green:user4 default-trigger: none, panic-indicator
>> yellow:wlan default-trigger: phy0tx
>> blue:bt default-trigger: hci0-power
>>
>> So lets adopt the same for Ultra96, which is one of the 96Boards
>> CE and AI platform. Since the WLAN and BT LEDs are hardwired onboard,
>> consolidate only User LEDs.
>>
>
> Hello,
>
> Any update on this patch?
I am still waiting for reaction from Rob.
We are keep trying to keep backward compatibility and this patch is
breaking it that's why I want to know DT guys reaction on this change.
Thanks,
Michal
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-21 6:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 9:42 [PATCH v3 0/7] Standardize onboard LED support for 96Boards Manivannan Sadhasivam
2018-10-29 9:42 ` Manivannan Sadhasivam
2018-10-29 9:42 ` [PATCH v3 1/7] arm64: dts: rockchip: ficus: Add on-board LED support Manivannan Sadhasivam
2018-10-29 9:42 ` Manivannan Sadhasivam
2018-12-11 19:11 ` Heiko Stuebner
2018-12-11 19:11 ` Heiko Stuebner
2018-10-29 9:42 ` [PATCH v3 2/7] arm64: dts: rockchip: rock960: " Manivannan Sadhasivam
2018-10-29 9:42 ` Manivannan Sadhasivam
2018-12-11 19:11 ` Heiko Stuebner
2018-12-11 19:11 ` Heiko Stuebner
2018-10-29 9:42 ` [PATCH v3 3/7] arm64: dts: hisilicon: hikey: Standardize LED labels and triggers Manivannan Sadhasivam
2018-10-29 9:42 ` Manivannan Sadhasivam
2018-10-29 9:42 ` [PATCH v3 4/7] arm64: dts: hisilicon: hikey960: " Manivannan Sadhasivam
2018-10-29 9:42 ` Manivannan Sadhasivam
2018-10-29 9:42 ` [PATCH v3 5/7] arm64: dts: hisilicon: poplar: " Manivannan Sadhasivam
2018-10-29 9:42 ` Manivannan Sadhasivam
2018-10-29 9:42 ` [PATCH v3 6/7] arm64: dts: xilinx: ultra96: " Manivannan Sadhasivam
2018-10-29 9:42 ` Manivannan Sadhasivam
2018-12-21 2:37 ` Manivannan Sadhasivam
2018-12-21 2:37 ` Manivannan Sadhasivam
2018-12-21 6:50 ` Michal Simek [this message]
2018-12-21 6:50 ` Michal Simek
2018-12-21 6:50 ` Michal Simek
2019-01-24 16:49 ` Rob Herring
2019-01-24 16:49 ` Rob Herring
2019-01-24 16:49 ` Rob Herring
2019-01-29 13:17 ` Michal Simek
2019-01-29 13:17 ` Michal Simek
2019-01-29 13:17 ` Michal Simek
2018-10-29 9:42 ` [PATCH v3 7/7] arm64: dts: qcom: apq8016-sbc: Standardize LED labels Manivannan Sadhasivam
2018-10-29 9:42 ` Manivannan Sadhasivam
2018-12-21 2:35 ` Manivannan Sadhasivam
2018-12-21 2:35 ` Manivannan Sadhasivam
2019-02-05 19:00 ` Nicolas Dechesne
2019-02-05 19:00 ` Nicolas Dechesne
2019-02-05 19:24 ` Bjorn Andersson
2019-02-05 19:24 ` Bjorn Andersson
2018-10-31 13:38 ` [PATCH v3 0/7] Standardize onboard LED support for 96Boards Linus Walleij
2018-10-31 13:38 ` Linus Walleij
2018-10-31 13:38 ` Linus Walleij
2018-10-31 15:46 ` Michal Simek
2018-10-31 21:17 ` Linus Walleij
2018-10-31 21:17 ` Linus Walleij
2018-10-31 21:17 ` Linus Walleij
2018-11-01 10:49 ` Heiko Stübner
2018-11-01 10:49 ` Heiko Stübner
2018-11-01 10:49 ` Heiko Stübner
2018-11-29 15:42 ` Wei Xu
2018-11-29 15:42 ` Wei Xu
2018-11-29 15:42 ` Wei 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=9f4f05cb-f326-a4e3-e306-cfbf64b629b4@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=amit.kucheria@linaro.org \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=koen.kooi@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-soc@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=nicolas.dechesne@linaro.org \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.