From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Wed, 15 May 2019 11:16:43 -0400 Subject: [U-Boot] [PATCH 00/13] System Firmware Loader for TI K3 family SoCs In-Reply-To: <20190507172542.31359-1-dannenberg@ti.com> References: <20190507172542.31359-1-dannenberg@ti.com> Message-ID: <20190515151643.GD22232@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, May 07, 2019 at 12:25:29PM -0500, Andreas Dannenberg wrote: > TI K3 SoCs like the AM654x devices are fundamentally dependent on a > firmware called SYSFW (System Firmware) being loaded into the dedicated > DMSC (Device Management and Security Controller) processor to provide > various services via TISCI (Texas Instruments System Control Interface) > to manage device aspects such as core bringup, power, clocks, security, > and so on across the entire SoC. [snip] > While I also have a working solution based on the existing FS loader > framework this has its own challenges, namely by its very nature only > addressing a subset of our use cases (no eMMC/SD RAW boot support for > example), being heavier on resource usage (needing to use ENV to pass > parameters), and not addressing the need to probe the boot peripheral. > This particular framework works well for use cases requiring to load > firmware from FS-based media once DDR is up and U-Boot is in a more > "initialized" state but it is not a one-fits all solution for very > early use in SPL board_init_f() accross different boot modes. I think one thing that might help here is to post this alternative solution and provide the 'size' information for both series. In addition, build something like am335x_evm and socfpga_stratix10 for both series and include their before/after 'size' info too. Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: