On Mon, 2020-05-18 at 09:08 +0200, Sascha Hauer wrote: > There's only one correct setting for each board or SoC. Instead of > letting the user choose between right and wrong, can't we add a hook > to be called from the board/SoC code? A device tree property might be > an option as well, something like barebox,enable-boot-ack. > > There are also bits to change the bus width after power up which > might need adjustments which would mean another parameter with the > current approach. If I remember the i.MX6 eMMC boot process correctly, there is no single correct configuration, even for a fixed HW layout. The eFUSE and eMMC EXT-CDS configuration just needs to match. Instead of trying to handle all the corner cases correctly (which is hard to test without permanently fusing HW), I'd prefer to just make it straight-forward to set and inspect these values (via a command or device parameters). Then these would be set once during board manufacturing/bring-up. After bring-up, the value in DT would be redundant configuration and could lead to confusion if it conflicts with the FUSEs. Regards, Jan -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
