public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Behun <marek.behun@nic.cz>
To: Luka Kovacic <luka.kovacic@sartura.hr>
Cc: linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-leds@vger.kernel.org,
	lee.jones@linaro.org, pavel@ucw.cz, dmurphy@ti.com,
	robh+dt@kernel.org, jdelvare@suse.com, linux@roeck-us.net,
	andrew@lunn.ch, jason@lakedaemon.net,
	gregory.clement@bootlin.com, luka.perkov@sartura.hr,
	robert.marko@sartura.hr
Subject: Re: [PATCH v2 7/7] arm64: dts: marvell: Add a device tree for the iEi Puzzle-M801 board
Date: Sat, 26 Sep 2020 19:50:08 +0200	[thread overview]
Message-ID: <20200926195008.6bd84dd3@nic.cz> (raw)
In-Reply-To: <20200926135514.26189-8-luka.kovacic@sartura.hr>

On Sat, 26 Sep 2020 15:55:14 +0200
Luka Kovacic <luka.kovacic@sartura.hr> wrote:

> +	leds {
> +		compatible = "gpio-leds";
> +		status = "okay";
> +		pinctrl-0 = <&cp0_sfpplus_led_pins &cp1_sfpplus_led_pins>;
> +		pinctrl-names = "default";
> +
> +		led0 {
> +			function = LED_FUNCTION_STATUS;
> +			label = "p2_act";
> +			gpios = <&cp1_gpio1 6 GPIO_ACTIVE_LOW>;
> +		};

There should be a dash in LED node name, please pass this dts via
dt_binding_check
  led-0 {
    ...
  };

Also why not add the `color` property to the LED? This is DTS for a
specific device, right?
`label` is obsolete. The LED subsystem creates a name in form
  [device:]color:function
If this LED should blink for activity on port 2 (is this an ethernet
port?), the function should be LED_FUNCTION_LAN and function-enumerator
should be <2> (or function should be LED_FUNCTION_ACTIVITY, depending
on how the LED subsystem goes forward with this, but certainly not
LED_FUNCTION_STATUS), and trigger-sources should be set to point to the
ethernet port.

Luka, are you willing to change this once we solve this API properly
in LED subsystem?



> +		led6 {
> +			function = LED_FUNCTION_STATUS;
> +			linux,default-trigger = "disk-activity";
> +			label = "front-hdd-led";
> +			gpios = <&cp0_gpio2 22 GPIO_ACTIVE_HIGH>;
> +		};

led-6. LED_FUNCTION_DISK. `label` deprecated.

> +		leds {
> +			compatible = "iei,wt61p803-puzzle-leds";
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +
> +			led@0 {
> +				reg = <0>;
> +				color = <LED_COLOR_ID_BLUE>;
> +				label = "front-power-led";
> +			};

Again, `label` is deprecated. Rather use function =
<LED_FUNCTION_POWER>;

Marek

  parent reply	other threads:[~2020-09-26 17:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-26 13:55 [PATCH v2 0/7] Add support for the iEi Puzzle-M801 board Luka Kovacic
2020-09-26 13:55 ` [PATCH v2 1/7] dt-bindings: Add iEi vendor prefix and iEi WT61P803 PUZZLE driver bindings Luka Kovacic
2020-09-26 17:56   ` Marek Behun
2020-09-26 13:55 ` [PATCH v2 2/7] drivers: mfd: Add a driver for iEi WT61P803 PUZZLE MCU Luka Kovacic
2020-09-26 19:16   ` [RFC PATCH] drivers: mfd: iei_wt61p803_puzzle_checksum() can be static kernel test robot
2020-09-26 19:28   ` [PATCH v2 2/7] drivers: mfd: Add a driver for iEi WT61P803 PUZZLE MCU Marek Behun
2020-09-27 16:09     ` Luka Kovacic
2020-09-26 13:55 ` [PATCH v2 3/7] drivers: hwmon: Add the iEi WT61P803 PUZZLE HWMON driver Luka Kovacic
2020-09-26 22:50   ` kernel test robot
2020-09-26 13:55 ` [PATCH v2 4/7] drivers: leds: Add the iEi WT61P803 PUZZLE LED driver Luka Kovacic
2020-09-26 18:09   ` Marek Behun
2020-09-27 15:44     ` Luka Kovacic
2020-09-26 13:55 ` [PATCH v2 5/7] Documentation/ABI: Add iei-wt61p803-puzzle driver sysfs interface documentation Luka Kovacic
2020-09-26 18:25   ` Marek Behun
2020-09-27 15:49     ` Luka Kovacic
2020-09-26 13:55 ` [PATCH v2 6/7] MAINTAINERS: Add an entry for the iEi WT61P803 PUZZLE driver Luka Kovacic
2020-09-26 13:55 ` [PATCH v2 7/7] arm64: dts: marvell: Add a device tree for the iEi Puzzle-M801 board Luka Kovacic
2020-09-26 15:05   ` Andrew Lunn
2020-09-26 17:50   ` Marek Behun [this message]
2020-09-27 15:01     ` Luka Kovacic

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=20200926195008.6bd84dd3@nic.cz \
    --to=marek.behun@nic.cz \
    --cc=andrew@lunn.ch \
    --cc=dmurphy@ti.com \
    --cc=gregory.clement@bootlin.com \
    --cc=jason@lakedaemon.net \
    --cc=jdelvare@suse.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=luka.kovacic@sartura.hr \
    --cc=luka.perkov@sartura.hr \
    --cc=pavel@ucw.cz \
    --cc=robert.marko@sartura.hr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox