diff mbox series

ARM: dts: bcm2837-rpi-cm3: Avoid leds-gpio probing issue

Message ID 1570964003-20227-1-git-send-email-wahrenst@gmx.net (mailing list archive)
State New, archived
Headers show
Series ARM: dts: bcm2837-rpi-cm3: Avoid leds-gpio probing issue | expand

Commit Message

Stefan Wahren Oct. 13, 2019, 10:53 a.m. UTC
bcm2835-rpi.dtsi defines the behavior of the ACT LED, which is available
on all Raspberry Pi boards. But there is no driver for this particual
GPIO on CM3 in mainline yet, so this node was left incomplete without
the actual GPIO definition. Since commit 025bf37725f1 ("gpio: Fix return
value mismatch of function gpiod_get_from_of_node()") this causing probe
issues of the leds-gpio driver for users of the CM3 dtsi file.

  leds-gpio: probe of leds failed with error -2

Until we have the necessary GPIO driver hide the ACT node for CM3
to avoid this.

Reported-by: Fredrik Yhlen <fredrik.yhlen@endian.se>
Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
Fixes: a54fe8a6cf66 ("ARM: dts: add Raspberry Pi Compute Module 3 and IO board")
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>
---
 arch/arm/boot/dts/bcm2837-rpi-cm3.dtsi | 8 ++++++++
 1 file changed, 8 insertions(+)

Hi,

i'm not sure the behavior change in leds-gpio was intended.

Regards
Stefan

--
2.7.4

Comments

Florian Fainelli Oct. 18, 2019, 6:59 p.m. UTC | #1
On Sun, 13 Oct 2019 12:53:23 +0200, Stefan Wahren <wahrenst@gmx.net> wrote:
> bcm2835-rpi.dtsi defines the behavior of the ACT LED, which is available
> on all Raspberry Pi boards. But there is no driver for this particual
> GPIO on CM3 in mainline yet, so this node was left incomplete without
> the actual GPIO definition. Since commit 025bf37725f1 ("gpio: Fix return
> value mismatch of function gpiod_get_from_of_node()") this causing probe
> issues of the leds-gpio driver for users of the CM3 dtsi file.
> 
>   leds-gpio: probe of leds failed with error -2
> 
> Until we have the necessary GPIO driver hide the ACT node for CM3
> to avoid this.
> 
> Reported-by: Fredrik Yhlen <fredrik.yhlen@endian.se>
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
> Fixes: a54fe8a6cf66 ("ARM: dts: add Raspberry Pi Compute Module 3 and IO board")
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Krzysztof Kozlowski <krzk@kernel.org>
> ---

Applied to devicetree/fixes, thanks!
--
Florian
Pavel Machek Nov. 4, 2019, 9:09 a.m. UTC | #2
On Sun 2019-10-13 12:53:23, Stefan Wahren wrote:
> bcm2835-rpi.dtsi defines the behavior of the ACT LED, which is available
> on all Raspberry Pi boards. But there is no driver for this particual
> GPIO on CM3 in mainline yet, so this node was left incomplete without
> the actual GPIO definition. Since commit 025bf37725f1 ("gpio: Fix return
> value mismatch of function gpiod_get_from_of_node()") this causing probe
> issues of the leds-gpio driver for users of the CM3 dtsi file.
> 
>   leds-gpio: probe of leds failed with error -2
> 
> Until we have the necessary GPIO driver hide the ACT node for CM3
> to avoid this.
> 
> Reported-by: Fredrik Yhlen <fredrik.yhlen@endian.se>
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
> Fixes: a54fe8a6cf66 ("ARM: dts: add Raspberry Pi Compute Module 3 and IO board")
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Krzysztof Kozlowski <krzk@kernel.org>

Acked-by: Pavel Machek <pavel@ucw.cz>
Stefan Wahren Nov. 4, 2019, 5:03 p.m. UTC | #3
Hi Pavel,

Am 04.11.19 um 10:09 schrieb Pavel Machek:
> On Sun 2019-10-13 12:53:23, Stefan Wahren wrote:
>> bcm2835-rpi.dtsi defines the behavior of the ACT LED, which is available
>> on all Raspberry Pi boards. But there is no driver for this particual
>> GPIO on CM3 in mainline yet, so this node was left incomplete without
>> the actual GPIO definition. Since commit 025bf37725f1 ("gpio: Fix return
>> value mismatch of function gpiod_get_from_of_node()") this causing probe
>> issues of the leds-gpio driver for users of the CM3 dtsi file.
>>
>>   leds-gpio: probe of leds failed with error -2
>>
>> Until we have the necessary GPIO driver hide the ACT node for CM3
>> to avoid this.
>>
>> Reported-by: Fredrik Yhlen <fredrik.yhlen@endian.se>
>> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
>> Fixes: a54fe8a6cf66 ("ARM: dts: add Raspberry Pi Compute Module 3 and IO board")
>> Cc: Linus Walleij <linus.walleij@linaro.org>
>> Cc: Krzysztof Kozlowski <krzk@kernel.org>
> Acked-by: Pavel Machek <pavel@ucw.cz>

thanks but this patch has already been applied.

Can i consider this as a "yes" to my intended question ( Is the behavior
change in leds-gpio desired )?
diff mbox series

Patch

diff --git a/arch/arm/boot/dts/bcm2837-rpi-cm3.dtsi b/arch/arm/boot/dts/bcm2837-rpi-cm3.dtsi
index 7c3cb7e..925cb37 100644
--- a/arch/arm/boot/dts/bcm2837-rpi-cm3.dtsi
+++ b/arch/arm/boot/dts/bcm2837-rpi-cm3.dtsi
@@ -9,6 +9,14 @@ 
 		reg = <0 0x40000000>;
 	};

+	leds {
+		/*
+		 * Since there is no upstream GPIO driver yet,
+		 * remove the incomplete node.
+		 */
+		/delete-node/ act;
+	};
+
 	reg_3v3: fixed-regulator {
 		compatible = "regulator-fixed";
 		regulator-name = "3V3";