Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 42779C433FE for ; Thu, 20 Jan 2022 18:56:13 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 642CD838DA; Thu, 20 Jan 2022 19:56:11 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=fail (p=none dis=none) header.from=xs4all.nl Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Received: by phobos.denx.de (Postfix, from userid 109) id 13CAF838E0; Thu, 20 Jan 2022 19:56:10 +0100 (CET) Received: from sibelius.xs4all.nl (sibelius.xs4all.nl [83.163.83.176]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 8192D838A7 for ; Thu, 20 Jan 2022 19:56:06 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=fail (p=none dis=none) header.from=xs4all.nl Authentication-Results: phobos.denx.de; spf=fail smtp.mailfrom=mark.kettenis@xs4all.nl Received: from localhost (bloch.sibelius.xs4all.nl [local]) by bloch.sibelius.xs4all.nl (OpenSMTPD) with ESMTPA id 9ff41322; Thu, 20 Jan 2022 19:56:04 +0100 (CET) Date: Thu, 20 Jan 2022 19:56:04 +0100 (CET) From: Mark Kettenis To: Tom Rini Cc: sjg@chromium.org, michael@walle.cc, daniel.schwierzeck@gmail.com, dennis@ausil.us, ilias.apalodimas@linaro.org, jaeckel-floss@eyet-services.de, lukas.auer@aisec.fraunhofer.de, michal.simek@xilinx.com, u-boot@lists.denx.de, xypron.glpk@gmx.de In-Reply-To: <20220120183047.GJ7004@bill-the-cat> (message from Tom Rini on Thu, 20 Jan 2022 13:30:47 -0500) Subject: Re: [PATCH v3 31/31] RFC: Switch rpi over to use bootstd References: <20220120083544.2964521-1-michael@walle.cc> <20220120183047.GJ7004@bill-the-cat> Message-ID: X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean > Date: Thu, 20 Jan 2022 13:30:47 -0500 > From: Tom Rini > > On Thu, Jan 20, 2022 at 11:16:35AM -0700, Simon Glass wrote: > > Hi Mark, > > > > On Thu, 20 Jan 2022 at 03:29, Mark Kettenis wrote: > > > > > > > From: Michael Walle > > > > Date: Thu, 20 Jan 2022 09:35:44 +0100 > > > > > > > > > The bootdevs have a natural priority, based on the assumed speed of > > > > > the device, so the board would only need to intervene (with an env var > > > > > or a devicetree property) when that is wrong. > > > > > > > > Does this make sense in general? The default boot order for a > > > > board should depend on what is available on board (or on the > > > > carrier board) and what is pluggable. I doubt there can be a sane > > > > default, so almost all boards will have to define its own > > > > boot order anyway. > > > > Please can you be more specific about what you the problem is here? If > > the board does not have a device then it will not exist in driver > > model (or will not probe) and it won't have a bootdev (or it won't > > probe). That seems to be equivalent to me. > > So, I'm not sure how much of a problem it is, since the board can still > define the default probe order via environment. But pick any random SoC > with more than 1 SD/MMC set of lines on the chip. Youboard may put the > first as SD slot and second as eMMC and Myboard may do the opposite and > both are going to probe in the same order since it's the same chip. > > That's what I think Mark is getting at with it not really making sense > to just rely on probe order as what to try. Something like that. I remember a lot of issues when boards were switched over to DM_MMC and the boot order changed. I believe this ended up beging solved by having aliases in the device tree.