u-boot/arch/arm/dts/kirkwood-lschlv2-u-boot.dtsi

// SPDX-License-Identifier: GPL-2.0+

&eth0 {
	status = "disabled";
};

&hdd_power {
	/delete-property/ regulator-always-on;
};

&usb_power {
	/delete-property/ regulator-always-on;
};
board: lsxl: convert to DM_GPIO Use the new mvebu GPIO driver and convert all the function calls to the former kirkwood GPIO driver. This means that we are now using the LED uclass and the regulator uclass. Unfortunately, the GPIO LED doesn't offer a blinking method. Thus we are now stuck with solid on and off states, which makes debugging a bit harder. Also, there is no GPIO fan driver for now. Signed-off-by: Michael Walle <michael@walle.cc> Reviewed-by: Stefan Roese <sr@denx.de> 2022-08-17 19:38:04 +00:00			`// SPDX-License-Identifier: GPL-2.0+`

board: lsxl: disable eth0 The board has only one network interface. The linux kernel will gracefully skip a the ethernet interface if no connected PHY could be probed. u-boot on the other hand will throw an error message. The kernel device tree is about to be fixed. For now, just disable the ethernet interface in our -u-boot.dtsi. Signed-off-by: Michael Walle <michael@walle.cc> Reviewed-by: Stefan Roese <sr@denx.de> 2022-08-17 19:38:08 +00:00			`&eth0 {`
			`status = "disabled";`
			`};`

board: lsxl: convert to DM_GPIO Use the new mvebu GPIO driver and convert all the function calls to the former kirkwood GPIO driver. This means that we are now using the LED uclass and the regulator uclass. Unfortunately, the GPIO LED doesn't offer a blinking method. Thus we are now stuck with solid on and off states, which makes debugging a bit harder. Also, there is no GPIO fan driver for now. Signed-off-by: Michael Walle <michael@walle.cc> Reviewed-by: Stefan Roese <sr@denx.de> 2022-08-17 19:38:04 +00:00			`&hdd_power {`
			`/delete-property/ regulator-always-on;`
			`};`

			`&usb_power {`
			`/delete-property/ regulator-always-on;`
			`};`