From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.19.y-cip 1/6] arm64: dts: renesas: r8a774c0-cat874: Add LEDs support
Date: Wed, 17 Jul 2019 11:39:30 +0200 [thread overview]
Message-ID: <20190717093930.GA5105@amd> (raw)
In-Reply-To: <OSBPR01MB2103E19170D82D9CC3B651D7B8C90@OSBPR01MB2103.jpnprd01.prod.outlook.com>
Hi!
> > > + led3 {
> > > + gpios = <&gpio6 4 GPIO_ACTIVE_HIGH>;
> > > + label = "LED3";
> > > + };
> > > + };
> >
> > With my LED maintainer hat on... these are not exactly useful LED names. Do
> > they have any fixed meaning? Are they labeled on the board?
> > What color are they?
>
> It is labelled as LED0 label on the board and green colour.
>
> Basically this board is as per 96boards CE specification
> System and User LEDs
> The following LEDs shall be present on the board.
> The LEDs shall be of the specified size, color and location.
> The User LEDs shall be directly programmable from the SoC.
> 1. WiFi activity LED Yellow Type: 0603 SMD
> 2. Bluetooth activity LED Blue Type: 0603 SMD
> 3. User LEDs x4 Green Type: 0603 SMD
> Other LEDs and UI interfaces are optional.
>
> As a LED maintainer, What is your recommendation for mainline?
>
> 1) label = "LED0"; --> based on the label on the board
>
> 2) label = " gren:LED0 "; --> based on the colour and label on the board.
>
> 3) label = " green:user1";--> based on the colour and label as per 96 boards CE specification.
Lets make it "green:user1".
Thank you,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190717/cdaad348/attachment-0001.sig>
next prev parent reply other threads:[~2019-07-17 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 14:28 [cip-dev] [PATCH 4.19.y-cip 0/6] Add LED/WDT support Biju Das
2019-07-15 14:28 ` [cip-dev] [PATCH 4.19.y-cip 1/6] arm64: dts: renesas: r8a774c0-cat874: Add LEDs support Biju Das
2019-07-16 20:26 ` Pavel Machek
2019-07-17 6:59 ` Biju Das
2019-07-17 9:39 ` Pavel Machek [this message]
2019-07-15 14:28 ` [cip-dev] [PATCH 4.19.y-cip 2/6] arm64: dts: renesas: r8a774c0-cat874: Add RWDT support Biju Das
2019-07-16 20:27 ` Pavel Machek
2019-07-17 7:40 ` Biju Das
2019-07-17 9:41 ` Pavel Machek
2019-07-15 14:28 ` [cip-dev] [PATCH 4.19.y-cip 3/6] arm64: dts: renesas: r8a774c0: Enable DMA for SCIF2 Biju Das
2019-07-15 14:28 ` [cip-dev] [PATCH 4.19.y-cip 4/6] arm64: dts: renesas: r8a774c0: Fix SCIF5 DMA channels Biju Das
2019-07-15 14:28 ` [cip-dev] [PATCH 4.19.y-cip 5/6] arm64: dts: renesas: r8a774c0: Remove invalid compatible value for CSI40 Biju Das
2019-07-15 14:28 ` [cip-dev] [PATCH 4.19.y-cip 6/6] arm64: dts: renesas: r8a774c0: sort subnodes of the soc node Biju Das
2019-07-17 9:47 ` [cip-dev] [PATCH 4.19.y-cip 0/6] Add LED/WDT support Pavel Machek
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=20190717093930.GA5105@amd \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.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