Confirming that target/linux/mvebu/patches-4.14/533-arm64-add-leds-configure-for-mv1000.patch
does not apply cleanly.
--- drivers/pinctrl/mvebu/pinctrl-armada-37xx.c 2019-06-05 20:11:44.098047406 -0700
+++ drivers/pinctrl/mvebu/pinctrl-armada-37xx.c 2019-06-05 20:14:39.122050335 -0700
@@ -170,10 +170,10 @@
PIN_GRP_EXTRA("uart2", 9, 2, BIT(1) | BIT(13) | BIT(14) | BIT(19),
BIT(1) | BIT(13) | BIT(14), BIT(1) | BIT(19),
18, 2, "gpio", "uart"),
- PIN_GRP_GPIO("led0_od", 11, 1, BIT(20), "led"),
- PIN_GRP_GPIO("led1_od", 12, 1, BIT(21), "led"),
- PIN_GRP_GPIO("led2_od", 13, 1, BIT(22), "led"),
- PIN_GRP_GPIO("led3_od", 14, 1, BIT(23), "led"),
+ //PIN_GRP_GPIO("led0_od", 11, 1, BIT(20), "led"),
+ //PIN_GRP_GPIO("led1_od", 12, 1, BIT(21), "led"),
+ //PIN_GRP_GPIO("led2_od", 13, 1, BIT(22), "led"),
+ //PIN_GRP_GPIO("led3_od", 14, 1, BIT(23), "led"),
Now on PIN_GRP_GPIO2
, so there is the possibility that there is more needed than just a re-reference to the removal, although the introduction of drivers/leds/leds-glmv1000.c
may be independent of the default pin controller.