public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] remoteproc: k3_system_controller: Increase rx timeout
Date: Fri, 10 May 2019 07:13:22 -0400	[thread overview]
Message-ID: <20190510111322.GC25571@bill-the-cat> (raw)
In-Reply-To: <20190502100552.31749-4-lokeshvutla@ti.com>

On Thu, May 02, 2019 at 03:35:52PM +0530, Lokesh Vutla wrote:

> There is one case where 400ms is not sufficient for loading the
> system firmware:
> - System firmware is not signed with rsa degenerate key.
> - ROM loading the sysfw directly from SPI flash which is in memory
>   mapped mode.
> 
> The above scenario is definitely not desired in production use cases
> as it effects boot time. But still keeping this support as this is
> a valid boot scenario.
> 
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190510/74dafd60/attachment.sig>

      reply	other threads:[~2019-05-10 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 10:05 [U-Boot] [PATCH 0/3] arm: k3: Update build support Lokesh Vutla
2019-05-02 10:05 ` [U-Boot] [PATCH 1/3] tools: k3_get_x509 cert: Add a script to generate x509 certificate for K3 devices Lokesh Vutla
2019-05-10 11:13   ` Tom Rini
2019-05-02 10:05 ` [U-Boot] [PATCH 2/3] arm: k3: config.mk: Use k3_gen_x509_cert.sh to generate boot images Lokesh Vutla
2019-05-10 11:13   ` Tom Rini
2019-05-02 10:05 ` [U-Boot] [PATCH 3/3] remoteproc: k3_system_controller: Increase rx timeout Lokesh Vutla
2019-05-10 11:13   ` Tom Rini [this message]

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=20190510111322.GC25571@bill-the-cat \
    --to=trini@konsulko.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox