From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 13/19] arm: dts: mt7623: move node mt6323 leds to mt6323.dtsi
Date: Mon, 19 Mar 2018 00:46:41 +0100 [thread overview]
Message-ID: <457d4fb4-dd38-af89-208d-31477a2eb20e@gmail.com> (raw)
In-Reply-To: <1520030818.8089.190.camel@mtkswgap22>
On 03/02/2018 11:46 PM, Sean Wang wrote:
> On Fri, 2018-03-02 at 09:40 -0600, Rob Herring wrote:
>> On Fri, Feb 23, 2018 at 06:16:33PM +0800, sean.wang at mediatek.com wrote:
>>> From: Sean Wang <sean.wang@mediatek.com>
>>>
>>> Since those LEDs are parts of PMIC MT6323, it is reasonable to merge
>>> those LEDs node definition back into mt6323.dtsi. This way can improve
>>> the reusability of those nodes among different boards with the same PMIC.
>>>
>>> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
>>> Cc: Lee Jones <lee.jones@linaro.org>
>>> ---
>>> arch/arm/boot/dts/mt6323.dtsi | 26 ++++++++++++++++++++++++-
>>> arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts | 28 ---------------------------
>>> 2 files changed, 25 insertions(+), 29 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/mt6323.dtsi b/arch/arm/boot/dts/mt6323.dtsi
>>> index 7c783d6..44c5642 100644
>>> --- a/arch/arm/boot/dts/mt6323.dtsi
>>> +++ b/arch/arm/boot/dts/mt6323.dtsi
>>> @@ -1,5 +1,5 @@
>>> /*
>>> - * Copyright (c) 2017 MediaTek Inc.
>>> + * Copyright (c) 2017-2018 MediaTek Inc.
>>> * Author: John Crispin <john@phrozen.org>
>>> * Sean Wang <sean.wang@mediatek.com>
>>> * This program is free software; you can redistribute it and/or modify
>>> @@ -237,5 +237,29 @@
>>> regulator-enable-ramp-delay = <216>;
>>> };
>>> };
>>> +
>>> + leds {
>>> + compatible = "mediatek,mt6323-led";
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + led at 0 {
>>> + reg = <0>;
>>> + label = "mt6323:isink:green";
>>
>> Changing the label potentially breaks userspace. And the fact that it is
>> a green LED is very much board specific. So I think the old location was
>> correct. You could put the parent node here and leave these child nodes
>> in the board specific dts file.
>>
>
> yes, I really made a mistake on breaking userspace with a label change.
>
> I will keep the parent node here and then leave these child nodes into
> board specific dts files. thanks for your idea!
>
Sorry I didn't see your email when I wrote my first comment. Yes this sounds
like the proper way to do it.
Regards,
Matthias
>>
>>> + default-state = "off";
>>> + };
>>> +
>>> + led at 1 {
>>> + reg = <1>;
>>> + label = "mt6323:isink:red";
>>> + default-state = "off";
>>> + };
>>> +
>>> + led at 2 {
>>> + reg = <2>;
>>> + label = "mt6323:isink:blue";
>>> + default-state = "off";
>>> + };
>>> + };
>>> };
>>> };
>>> diff --git a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
>>> index 75e61c4..767b225 100644
>>> --- a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
>>> +++ b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
>>> @@ -483,34 +483,6 @@
>>> status = "okay";
>>> };
>>>
>>> -&pwrap {
>>> - mt6323 {
>>> - mt6323led: led {
>>> - compatible = "mediatek,mt6323-led";
>>> - #address-cells = <1>;
>>> - #size-cells = <0>;
>>> -
>>> - led at 0 {
>>> - reg = <0>;
>>> - label = "bpi-r2:isink:green";
>>> - default-state = "off";
>>> - };
>>> -
>>> - led at 1 {
>>> - reg = <1>;
>>> - label = "bpi-r2:isink:red";
>>> - default-state = "off";
>>> - };
>>> -
>>> - led at 2 {
>>> - reg = <2>;
>>> - label = "bpi-r2:isink:blue";
>>> - default-state = "off";
>>> - };
>>> - };
>>> - };
>>> -};
>>> -
>>> &spi0 {
>>> pinctrl-names = "default";
>>> pinctrl-0 = <&spi0_pins_a>;
>>> --
>>> 2.7.4
>>>
>
>
next prev parent reply other threads:[~2018-03-18 23:46 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 10:16 [PATCH v1 00/19] refactor dts and add support for more boards sean.wang at mediatek.com
2018-02-23 10:16 ` [PATCH v1 01/19] dt-bindings: pinctrl: mediatek: use - instead of _ in examples sean.wang at mediatek.com
2018-03-02 7:43 ` Linus Walleij
2018-02-23 10:16 ` [PATCH v1 02/19] dt-bindings: cpufreq: " sean.wang at mediatek.com
2018-02-26 4:13 ` Viresh Kumar
2018-03-19 2:51 ` Sean Wang
2018-03-19 10:35 ` Matthias Brugger
2018-03-02 15:53 ` Rob Herring
2018-02-23 10:16 ` [PATCH v1 03/19] dt-bindings: pinctrl: mediatek: add bindings for I2C2 and SPI2 on MT7623 sean.wang at mediatek.com
2018-03-02 7:44 ` Linus Walleij
2018-02-23 10:16 ` [PATCH v1 04/19] dt-bindings: arm: mediatek: add support for more mt7623 reference boards sean.wang at mediatek.com
2018-03-02 16:00 ` Rob Herring
2018-03-12 11:03 ` Matthias Brugger
2018-02-23 10:16 ` [PATCH v1 05/19] arm: dts: mt7623: add BTIF, HSDMA and SPI-NOR device nodes sean.wang at mediatek.com
2018-03-12 9:40 ` Matthias Brugger
2018-03-12 9:53 ` Sean Wang
2018-02-23 10:16 ` [PATCH v1 06/19] arm: dts: mt7623: fix USB initialization fails on bananapi-r2 sean.wang at mediatek.com
2018-03-12 11:03 ` Matthias Brugger
2018-02-23 10:16 ` [PATCH v1 07/19] arm: dts: mt7623: fix the regulators mmc should use " sean.wang at mediatek.com
2018-03-18 23:49 ` Matthias Brugger
2018-02-23 10:16 ` [PATCH v1 08/19] arm: dts: mt7623: enable three available UARTs " sean.wang at mediatek.com
2018-03-18 23:49 ` Matthias Brugger
2018-02-23 10:16 ` [PATCH v1 09/19] arm: dts: mt7623: add related clock properties to cpu[1-3] nodes sean.wang at mediatek.com
2018-02-26 4:13 ` Viresh Kumar
2018-03-18 23:49 ` Matthias Brugger
2018-02-23 10:16 ` [PATCH v1 10/19] arm: dts: mt7623: remove useless property pinctrl-names at node switch@0 sean.wang at mediatek.com
2018-03-18 23:50 ` Matthias Brugger
2018-02-23 10:16 ` [PATCH v1 11/19] arm: dts: mt7623: use - instead of _ in DT node name sean.wang at mediatek.com
2018-03-18 23:50 ` Matthias Brugger
2018-02-23 10:16 ` [PATCH v1 12/19] arm: dts: mt7623: fix all Warnings (unit_address_vs_reg) sean.wang at mediatek.com
2018-03-18 21:54 ` Matthias Brugger
2018-02-23 10:16 ` [PATCH v1 13/19] arm: dts: mt7623: move node mt6323 leds to mt6323.dtsi sean.wang at mediatek.com
2018-03-02 15:40 ` Rob Herring
2018-03-02 22:46 ` Sean Wang
2018-03-18 23:46 ` Matthias Brugger [this message]
2018-03-18 22:01 ` Matthias Brugger
2018-02-23 10:16 ` [PATCH v1 14/19] arm: dts: mt7623: extend common file to unify all boards with MT7623 SoCs sean.wang at mediatek.com
2018-02-23 10:16 ` [PATCH v1 15/19] arm: dts: mt7623: add SPI[1, 2], I2C2 and sound related nodes to reference board sean.wang at mediatek.com
2018-02-23 10:16 ` [PATCH v1 16/19] arm: dts: mt7623: fixup available memory size on bananapi-r2 sean.wang at mediatek.com
2018-03-02 15:42 ` Rob Herring
2018-03-02 23:27 ` Sean Wang
2018-03-05 14:16 ` Rob Herring
2018-03-05 15:46 ` Sean Wang
2018-02-23 10:16 ` [PATCH v1 17/19] arm: dts: mt7623: add MT7623N reference board with eMMC sean.wang at mediatek.com
2018-02-23 10:16 ` [PATCH v1 18/19] arm: dts: mt7623: add MT7623A reference boards sean.wang at mediatek.com
2018-03-02 15:45 ` Rob Herring
2018-03-03 2:15 ` Sean Wang
2018-03-05 14:10 ` Rob Herring
2018-03-05 15:10 ` Sean Wang
2018-02-23 10:16 ` [PATCH v1 19/19] arm: dts: mediatek: converted to using SPDX identifiers sean.wang at mediatek.com
2018-03-02 15:52 ` Rob Herring
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=457d4fb4-dd38-af89-208d-31477a2eb20e@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).