[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f4f05cb-f326-a4e3-e306-cfbf64b629b4@xilinx.com>
Date: Fri, 21 Dec 2018 07:50:29 +0100
From: Michal Simek <michal.simek@...inx.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
<michal.simek@...inx.com>, Rob Herring <robh+dt@...nel.org>
CC: <linux-leds@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
<linux-rockchip@...ts.infradead.org>,
<linux-arm-msm@...r.kernel.org>, <linux-soc@...r.kernel.org>,
<daniel.thompson@...aro.org>, <amit.kucheria@...aro.org>,
<linus.walleij@...aro.org>, <koen.kooi@...aro.org>,
<nicolas.dechesne@...aro.org>
Subject: Re: [PATCH v3 6/7] arm64: dts: xilinx: ultra96: Standardize LED
labels and triggers
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
Powered by blists - more mailing lists