[PATCH] ARM: dts: stm32mp: stm32mp135-dk: disable button on PA13

[Ahmad Fatoum <a.fatoum@pengutronix.de>]

After update to the v7.0-rc1 device trees, boot up on the board
reports following error:

  ERROR: gpiolib: _gpio_request: gpio-13 (led-red) status -16

This is caused by the combination of following two upstream kernel commits:

57012d79fefd ("ARM: dts: stm32: add UserPA13 button on stm32mp135f-dk")
31f0d9a486a8 ("ARM: dts: stm32: Add red LED for stm32mp135f-dk board")

Both reference the same &gpioa 13. Linux didn't seem to mind, but
barebox fails the LED driver probe, because the GPIO had already been
requested.

Assuming it is correct that they share the same GPIO physically,
Blinking the LED would register a button press, so it sounds not so
useful to have both enabled by default.

Thus disable the button in barebox.

This has been reported upstream at [1].

[1]: https://lore.kernel.org/all/382d28eb-557c-4cae-898c-8ed5c8cd7843@pengutronix.de/

Fixes: fe223ba39321 ("dts: update to v7.0-rc1")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 arch/arm/dts/stm32mp135f-dk.dts | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/arch/arm/dts/stm32mp135f-dk.dts b/arch/arm/dts/stm32mp135f-dk.dts
index bf45276c864f..2887d153bc2d 100644
--- a/arch/arm/dts/stm32mp135f-dk.dts
+++ b/arch/arm/dts/stm32mp135f-dk.dts
@@ -16,3 +16,8 @@ environment {
 		};
 	};
 };
+
+&{/gpio-keys/button-user} {
+	/* The button shared the same GPIO as led-red */
+	barebox,status = "disabled";
+};
-- 
2.47.3