lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160327055012.GD8929@tuxbot>
Date:	Sat, 26 Mar 2016 22:50:12 -0700
From:	Bjorn Andersson <bjorn.andersson@...aro.org>
To:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:	Andy Gross <andy.gross@...aro.org>, linux-arm-msm@...r.kernel.org,
	devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, linux-soc@...r.kernel.org
Subject: Re: [PATCH 10/12] ARM: dts: dragonboard-600c: Add on board leds
 support

On Wed 23 Mar 12:48 PDT 2016, Srinivas Kandagatla wrote:

> This patch adds support to 4 user leds, wlan and bt led on board.
> 
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>

I'm not fond of the overly complicated names; and I think it should at
least be shortened to "db600c:...".

Tested this on my DB600c, seems to work, except the WiFi/BT triggers,
see comments below.

> +		leds {
> +			pinctrl-names = "default";
> +			pinctrl-0 = <&user_leds>, <&mpp_leds>;
> +
> +			compatible = "gpio-leds";
> +
> +			led@1 {
> +				label = "dragonboard-600c:green:user1";
> +				gpios = <&tlmm_pinmux 3 GPIO_ACTIVE_HIGH>;
> +				linux,default-trigger = "heartbeat";
> +				default-state = "off";
> +			};
> +
> +			led@2 {
> +				label = "dragonboard-600c:green:user2";
> +				gpios = <&tlmm_pinmux 7 GPIO_ACTIVE_HIGH>;
> +				linux,default-trigger = "mmc0";
> +				default-state = "off";
> +			};
> +
> +			led@3 {
> +				label = "dragonboard-600c:green:user3";
> +				gpios = <&tlmm_pinmux 10 GPIO_ACTIVE_HIGH>;
> +				linux,default-trigger = "mmc1";
> +				default-state = "off";
> +			};
> +
> +			led@4 {
> +				label = "apq8016-sbc:green:user4";
> +				gpios = <&tlmm_pinmux 11 GPIO_ACTIVE_HIGH>;
> +				linux,default-trigger = "none";
> +				default-state = "off";
> +			};
> +
> +			led@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.

> +				default-state = "off";
> +			};
> +
> +			led@6 {
> +				label = "dragonboard-600c:blue:bt";
> +				gpios = <&pm8921_mpps 8 GPIO_ACTIVE_HIGH>;
> +				linux,default-trigger = "bt";

This should be "hci0-power".

> +				default-state = "off";
> +			};
> +		};
> +

Regards,
Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ