From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Mon, 03 Jun 2013 09:05:34 -0600 Subject: [U-Boot] [PATCH] fdt: allow bootdelay to be specified via device tree In-Reply-To: <51AB3E2E.1060004@cideas.com> References: <1368554576-19733-1-git-send-email-swarren@wwwdotorg.org> <51AAD707.3040009@nvidia.com> <51AB3E2E.1060004@cideas.com> Message-ID: <51ACB0BE.6060009@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 06/02/2013 06:44 AM, Gerald Van Baren wrote: > Hi Stephen, > > On 06/02/2013 01:24 AM, Stephen Warren wrote: >> On 05/14/2013 12:02 PM, Stephen Warren wrote: >>> From: Stephen Warren >>> >>> This can be useful to force bootcmd to execute as soon as U-Boot has >>> started. >>> >>> My use-case is: An SoC-specific tool pushes U-Boot into RAM, along with >>> an image to be written to device boot flash, with the DT config property >>> "bootcmd" set to contain a command to write that image to flash. In this >>> scenario, we don't want to allow any stale bootdelay value taken from >>> the current flash content to affect how long it takes before the >>> flashing process starts. >> >> Jerry, does this patch look OK, or do you have comments on it? Thanks. > > I'm good with the patch. > > Acked-by: Gerald Van Baren Oh, I'm not sure who you're expecting to apply this then; I assume since it was a DT-related feature it'd be applied to your DT tree. Are you expecting Tom Rini to apply it to the main U-Boot repo?