Now that we have a HSIO blk ctrl driver, there is no need to generally
assume that TF-A or BootROM have left them enabled for us.
Boards that want to continue making use of this assumption can reinstate
the barebox,allow-dummy property, but everyone else should just enable
CONFIG_IMX8M_BLK_CTRL.
While barebox,allow-dummy only has an effect if the driver doesn't
exist (as determined by deep probe), we remove the property for improved
user experience when the TF-A doesn't enable the HSIO power domain.
In that case, barebox,allow-dummy would cause barebox to continue
probe of USB controller and PHY resulting in a bus hang instead of
an error message that tells what's up:
imx8mq-usb-phy 381f0040.usb-phy@xxxxxxxxxxx: error No such device: power domain attach failed
dwc3-of-simple 32f10100.usb@xxxxxxxxxxx: error No such device: power domain attach failed
imx8mq-usb-phy 382f0040.usb-phy@xxxxxxxxxxx: error No such device: power domain attach failed
dwc3-of-simple 32f10108.usb@xxxxxxxxxxx: error No such device: power domain attach failed
Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx>
---
arch/arm/dts/imx8mp.dtsi | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/arm/dts/imx8mp.dtsi b/arch/arm/dts/imx8mp.dtsi
index 04767ad382c8..7a038217c468 100644
--- a/arch/arm/dts/imx8mp.dtsi
+++ b/arch/arm/dts/imx8mp.dtsi
@@ -73,7 +73,3 @@ &gpu3d {
&gpu2d {
barebox,feature-gates = <&feat IMX8M_FEAT_GPU>;
};
-
-&hsio_blk_ctrl {
- barebox,allow-dummy;
-};
--
2.39.2
