From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.19.y-cip 2/3] arm64: dts: renesas: hihope-common: Add BT support
Date: Thu, 10 Oct 2019 09:38:10 +0200 [thread overview]
Message-ID: <20191010073809.GA23033@amd> (raw)
In-Reply-To: <1570689915-14149-3-git-send-email-biju.das@bp.renesas.com>
Hi!
> commit d112c20925443b4a8876b101e5b7b13ef105057e upstream.
>
> This patch enables BT support for the HiHope RZ/G2[MN] boards.
> +++ b/arch/arm64/boot/dts/renesas/hihope-common.dtsi
> @@ -31,6 +32,13 @@
> leds {
> compatible = "gpio-leds";
>
> + bt_active_led {
> + label = "blue:bt";
It would be good to change this to "blue:bluetooth", for consistency
with include/dt-bindings/leds/common.h . It will change names in the
sysfs.
Best regards,
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/20191010/0b1bbd64/attachment.sig>
next prev parent reply other threads:[~2019-10-10 7:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 6:45 [cip-dev] [PATCH 4.19.y-cip 0/3] Add WLAN/BT support Biju Das
2019-10-10 6:45 ` [cip-dev] [PATCH 4.19.y-cip 1/3] arm64: dts: renesas: hihope-common: Add PCA9654 I/O expander Biju Das
2019-10-10 6:45 ` [cip-dev] [PATCH 4.19.y-cip 2/3] arm64: dts: renesas: hihope-common: Add BT support Biju Das
2019-10-10 7:38 ` Pavel Machek [this message]
2019-10-10 7:45 ` Biju Das
2019-10-10 10:38 ` Biju Das
2019-10-10 6:45 ` [cip-dev] [PATCH 4.19.y-cip 3/3] arm64: dts: renesas: hihope-common: Add WLAN support Biju Das
2019-10-10 7:43 ` [cip-dev] [PATCH 4.19.y-cip 0/3] Add WLAN/BT support Pavel Machek
2019-10-10 8:15 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-10-13 20:23 ` 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=20191010073809.GA23033@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.