From: Tom Rini Date: Thu, 6 Aug 2020 22:16:12 -0400 Subject: [PATCH v4 17/17] common/board_r: Move blkcache_init call earlier in the boot sequence In-Reply-To: <20200724111225.12513-17-ovidiu.panait@windriver.com> References: <20200724111225.12513-1-ovidiu.panait@windriver.com> <20200724111225.12513-17-ovidiu.panait@windriver.com> Message-ID: <20200807021612.GJ6965@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 Fri, Jul 24, 2020 at 02:12:25PM +0300, Ovidiu Panait wrote: > blkcache_init manually relocates blkcache list pointers when > CONFIG_NEEDS_MANUAL_RELOC is enabled. However, it is called very late in > the boot sequence, which could be a problem if previous boot calls execute > blkcache operations with the non-relocated pointers. For example, mmc is > initialized earlier and might call blkcache_invalidate (in > mmc_select_hwpart()) when trying to load the environment from mmc via > env_load(). > > To fix this issue, move blkcache_init boot call earlier, before mmc gets > initialized. > > Acked-by: Angelo Dureghello > Tested-by: Angelo Dureghello > Reviewed-by: Simon Glass > Signed-off-by: Ovidiu Panait Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: