linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 10/12] ARM: dts: dragonboard-600c: Add on board leds support
Date: Tue, 29 Mar 2016 07:51:15 -0700	[thread overview]
Message-ID: <20160329145115.GO8929@tuxbot> (raw)
In-Reply-To: <56FA8F47.7070200@linaro.org>

On Tue 29 Mar 07:20 PDT 2016, Srinivas Kandagatla wrote:

> Thanks Bjorn,
> 
> On 27/03/16 06:50, Bjorn Andersson wrote:
> >On Wed 23 Mar 12:48 PDT 2016, Srinivas Kandagatla wrote:
[..]
> >>+
> >>+			led at 5 {
> >>+				label = "dragonboard-600c:yellow:wlan";
> >>+				gpios = <&pm8921_mpps 7 GPIO_ACTIVE_HIGH>;
> >>+				linux,default-trigger = "wlan";
> >
> >This should either be "phy0rx", "phy0tx", "phy0assoc" or "phy0radio". TX
> >does not seem to work, so this should be debugged; "assoc" is probably
> >the one that makes most sense.
> 
> 
> Am ok, to change, did you get activity leds works with any of these strings
> with WLAN or BT?
> 

I did test them; rx, assoc and radio seems to work. Tx does not tickle
the led, but should probably.

I didn't find the spec for the baord, so I'm not sure what the LEDs
should indicate. But it feels like radio or assoc makes most sense, and
follows what we can do with the BT led.

> phy0rx/tx seems to be bit more generic and atleast the name looks bit
> non-specific to wlan.
> 
> These names should be documented somewhere, Its very difficult to find which
> names to use unless you read the code.
> 
> It would be nice to just provide a phandle to the device which led-trigger
> should use, which makes it clear and explicit.
> 

I agree, I was surprised by their naming. The phandle solution would
have been nice, except that you have no way from sysfs to pick which
node to follow.

> 
> 
> >
> >>+				default-state = "off";
> >>+			};
> >>+
> >>+			led at 6 {
> >>+				label = "dragonboard-600c:blue:bt";
> >>+				gpios = <&pm8921_mpps 8 GPIO_ACTIVE_HIGH>;
> >>+				linux,default-trigger = "bt";
> >
> >This should be "hci0-power".
> 
> Does this trigger work for you?
> Name is bit misleading though.
> 

I don't think I tested it, but it is the only bt led trigger exposed by
the bluetooth framework. I don't think we have any other hci devices on
this board, so it should be fine.

Regards,
Bjorn

  reply	other threads:[~2016-03-29 14:51 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 19:46 [PATCH 00/12] ARM: dts: Add dragonboard-600c support Srinivas Kandagatla
2016-03-23 19:47 ` [PATCH 01/12] ARM: dts: apq8064: fix the pinctrls for i2c and spi Srinivas Kandagatla
2016-03-29 14:28   ` Bjorn Andersson
2016-03-29 15:02     ` Srinivas Kandagatla
2016-03-29 16:10       ` Bjorn Andersson
2016-03-23 19:47 ` [PATCH 02/12] ARM: dts: apq8064: add support to gsbi1 uart Srinivas Kandagatla
2016-03-29 14:29   ` Bjorn Andersson
2016-03-23 19:47 ` [PATCH 03/12] ARM: dts: apq8064: add gsbi7 i2c support Srinivas Kandagatla
2016-03-29 14:34   ` Bjorn Andersson
2016-03-23 19:47 ` [PATCH 04/12] ARM: dts: dragonboard-600c: add board support with serial Srinivas Kandagatla
2016-03-23 20:07   ` Stephen Boyd
2016-03-23 20:30     ` Srinivas Kandagatla
2016-03-24  1:04       ` Bjorn Andersson
2016-03-24  1:48         ` Stephen Boyd
2016-03-24 12:49           ` Arnd Bergmann
2016-03-24 20:50           ` Nicolas Dechesne
2016-03-29 19:00             ` Stephen Boyd
2016-03-29 14:21           ` Bjorn Andersson
2016-03-23 19:47 ` [PATCH 05/12] ARM: dts: dragonboard-600c: add pmic regulator supplies Srinivas Kandagatla
2016-03-29 14:37   ` Bjorn Andersson
2016-03-29 15:02     ` Srinivas Kandagatla
2016-03-23 19:47 ` [PATCH 06/12] ARM: dts: dragonboard-600c: Add eMMC and SD card support Srinivas Kandagatla
2016-03-29 14:38   ` Bjorn Andersson
2016-03-29 15:02     ` Srinivas Kandagatla
2016-03-23 19:47 ` [PATCH 07/12] ARM: dts: dragonboard-600c: add usb support Srinivas Kandagatla
2016-03-29 14:39   ` Bjorn Andersson
2016-03-23 19:47 ` [PATCH 08/12] ARM: dts: dragonboard-600c: add pcie support Srinivas Kandagatla
2016-03-29 14:39   ` Bjorn Andersson
2016-03-23 19:47 ` [PATCH 09/12] ARM: dts: dragonboard-600c: add on board sata support Srinivas Kandagatla
2016-03-29 14:40   ` Bjorn Andersson
2016-03-23 19:48 ` [PATCH 10/12] ARM: dts: dragonboard-600c: Add on board leds support Srinivas Kandagatla
2016-03-24 16:51   ` Nicolas Dechesne
2016-03-29 13:30     ` Srinivas Kandagatla
2016-03-27  5:50   ` Bjorn Andersson
2016-03-29 14:20     ` Srinivas Kandagatla
2016-03-29 14:51       ` Bjorn Andersson [this message]
2016-03-29 18:32         ` Nicolas Dechesne
2016-03-29 21:10           ` Bjorn Andersson
2016-03-30 12:54     ` Rob Herring
2016-03-23 19:48 ` [PATCH 11/12] ARM: dts: dragonboard-600c: add i2c support Srinivas Kandagatla
2016-03-29 14:44   ` Bjorn Andersson
2016-03-29 15:02     ` Srinivas Kandagatla
2016-03-23 19:48 ` [PATCH 12/12] ARM: dts: dragonboard-600c: add spi support Srinivas Kandagatla
2016-03-29 14:54 ` [PATCH 00/12] ARM: dts: Add dragonboard-600c support Bjorn Andersson
2016-03-29 15:02   ` Srinivas Kandagatla

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=20160329145115.GO8929@tuxbot \
    --to=bjorn.andersson@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;
as well as URLs for NNTP newsgroup(s).