From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ahmad Fatoum Date: Fri, 12 Feb 2021 14:29:47 +0100 Subject: [Uboot-stm32] [PATCH] usb: dwc2: change compatible st, stm32mp1-hsotg to st, stm32mp15-hsotg In-Reply-To: <20210211130236.GR10169@bill-the-cat> References: <20210209111438.1.If6218391a7cf47afdeda5e5e6c79937b4e8ab085@changeid> <804006bd-a6bc-0352-374d-6d2b33e42db9@denx.de> <20210210195926.GJ10169@bill-the-cat> <20210211130236.GR10169@bill-the-cat> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 11.02.21 14:02, Tom Rini wrote: > On Thu, Feb 11, 2021 at 12:14:51PM +0100, Ahmad Fatoum wrote: >> I think platforms like the STM32MP1 should be handled specially, because >> they support having an external device tree passed from the FSBL at runtime. >> See https://github.com/trini/u-boot/blob/master/arch/arm/mach-stm32mp/boot_params.c#L32 >> >> @Patrick, wouldn't this change break booting newer U-Boot with older TF-A in >> some configurations? Or is this reusing-fsbl-fdt feature unused? > > The long stated policy of U-Boot is to allow non-final bindings to be > used until they're finalized in Linux in order to address the "chicken > and egg" problem, since it's already a terrible idea to go to production > with a Linux kernel that's using non-final bindings. Any older TF-A > that doesn't work with this newer binding should be on a developer board > and they can just upgrade. Linux says "DT is ABI" and allows the ABI to > break when there's a bug in the DT. We don't say "DT is ABI" we say "we > use the Linux kernel binding". I see. Thanks for the clarification. I am still curious what configurations use the TF-A-provided device tree for U-Boot. Patrick? -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |