All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fdt: allow bootdelay to be specified via device tree
Date: Mon, 03 Jun 2013 09:05:34 -0600	[thread overview]
Message-ID: <51ACB0BE.6060009@wwwdotorg.org> (raw)
In-Reply-To: <51AB3E2E.1060004@cideas.com>

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 <swarren@nvidia.com>
>>>
>>> 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 <vanbaren@cideas.com>

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?

  reply	other threads:[~2013-06-03 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 18:02 [U-Boot] [PATCH] fdt: allow bootdelay to be specified via device tree Stephen Warren
2013-05-14 19:08 ` Simon Glass
2013-06-02  5:24 ` Stephen Warren
2013-06-02 12:44   ` Gerald Van Baren
2013-06-03 15:05     ` Stephen Warren [this message]
2013-06-03 16:34       ` Jerry Van Baren
2013-06-05 12:34 ` [U-Boot] " Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51ACB0BE.6060009@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.