linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
	linux-arm-kernel@lists.infradead.org
Cc: Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	kernel@dh-electronics.com
Subject: Re: [PATCH V2 06/15] ARM: dts: imx6q-dhcom: Add keys and leds to the PDK2 board
Date: Tue, 22 Jun 2021 12:42:42 +0200	[thread overview]
Message-ID: <3ef5a286-d596-fd11-17ba-ba7f78f003a1@denx.de> (raw)
In-Reply-To: <20210622095948.99047-6-cniedermaier@dh-electronics.com>

On 6/22/21 11:59 AM, Christoph Niedermaier wrote:
> On the PDK2 there are 4 keys and 4 leds. DHCOM GPIOs are
> used for that, but one led isn't useable, because the GPIO
> is already use as touch interrupt.

...used...

[...]

> +		led-0 {
> +			label = "green:led5";

Documentation/devicetree/bindings/leds/common.yaml says this is deprecated:

   label:
     description:
       The label for this LED. If omitted, the label is taken from the 
node name
       (excluding the unit address). It has to uniquely identify a 
device, i.e.
       no other LED class device can be assigned the same label. This 
property is
       deprecated - use 'function' and 'color' properties instead.


> +			gpios = <&gpio4 5 GPIO_ACTIVE_HIGH>; /* GPIO E */
> +			default-state = "off";
> +			status = "disabled";
> +		};

[...]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-22 10:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  9:59 [PATCH V2 01/15] ARM: dts: imx6q-dhcom: Add the parallel system bus Christoph Niedermaier
2021-06-22  9:59 ` [PATCH V2 02/15] ARM: dts: imx6q-dhcom: Add interrupt and compatible to the ethernet PHY Christoph Niedermaier
2021-06-22 10:12   ` Marek Vasut
2021-06-22  9:59 ` [PATCH V2 03/15] ARM: dts: imx6q-dhcom: Fill GPIO line names on DHCOM SoM Christoph Niedermaier
2021-06-22 10:25   ` Marek Vasut
2021-06-22  9:59 ` [PATCH V2 04/15] ARM: dts: imx6q-dhcom: Adding Wake pin to the PCIe pinctrl Christoph Niedermaier
2021-06-22 10:26   ` Marek Vasut
2021-06-22  9:59 ` [PATCH V2 05/15] ARM: dts: imx6q-dhcom: Align stdout-path with other DHCOM SoMs Christoph Niedermaier
2021-06-22 10:39   ` Marek Vasut
2021-06-22  9:59 ` [PATCH V2 06/15] ARM: dts: imx6q-dhcom: Add keys and leds to the PDK2 board Christoph Niedermaier
2021-06-22 10:42   ` Marek Vasut [this message]
2021-06-22  9:59 ` [PATCH V2 07/15] ARM: dts: imx6q-dhcom: Use 1G ethernet on " Christoph Niedermaier
2021-06-22 10:51   ` Marek Vasut
2021-06-22  9:59 ` [PATCH V2 08/15] ARM: dts: imx6q-dhcom: Rework of the DHCOM GPIO pinctrls Christoph Niedermaier
2021-06-22  9:59 ` [PATCH V2 09/15] ARM: dts: imx6q-dhcom: Remove ddc-i2c-bus property Christoph Niedermaier
2021-06-22 11:25   ` Marek Vasut
2021-06-22  9:59 ` [PATCH V2 10/15] ARM: dts: imx6q-dhcom: Set minimum memory size of all DHCOM i.MX6 variants Christoph Niedermaier
2021-06-22 11:27   ` Marek Vasut
2021-06-25 16:15     ` Christoph Niedermaier
2021-06-25 19:57       ` Marek Vasut
2021-06-22  9:59 ` [PATCH V2 11/15] ARM: dts: imx6q-dhcom: Rearrange of iomux Christoph Niedermaier
2021-06-22 11:27   ` Marek Vasut
2021-06-22  9:59 ` [PATCH V2 12/15] ARM: dts: imx6q-dhcom: Cleanup of the devicetrees Christoph Niedermaier
2021-06-22 11:31   ` Marek Vasut
2021-06-22  9:59 ` [PATCH V2 13/15] ARM: dts: imx6qdl-dhcom: Split SoC-independent parts of DHCOM SOM and PDK2 Christoph Niedermaier
2021-06-22  9:59 ` [PATCH V2 14/15] ARM: dts: imx6qdl-dhcom: Add DHCOM based PicoITX board Christoph Niedermaier
2021-06-22  9:59 ` [PATCH V2 15/15] ARM: dts: imx6qdl-dhcom: Add DHSOM based DRC02 board Christoph Niedermaier
2021-06-22 10:10 ` [PATCH V2 01/15] ARM: dts: imx6q-dhcom: Add the parallel system bus Marek Vasut

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=3ef5a286-d596-fd11-17ba-ba7f78f003a1@denx.de \
    --to=marex@denx.de \
    --cc=cniedermaier@dh-electronics.com \
    --cc=festevam@gmail.com \
    --cc=kernel@dh-electronics.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).