All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/3] MCU R5F branch-only boot on J7200 SoCs
Date: Tue, 15 Sep 2020 19:18:20 +0530	[thread overview]
Message-ID: <d14371a0-69f8-c4e2-55b1-f152f1d8fa71@ti.com> (raw)
In-Reply-To: <20200818190945.8966-1-s-anna@ti.com>



On 19/08/20 12:39 am, Suman Anna wrote:
> Hi Lokesh,
> 
> The following series adds the support for the branch-only boot of an
> application firmware on MCU R5F from R5 SPL after it has finished
> launching the A72.
> 
> Most of the changes are just related to updating J7200 defconfigs or
> dts nodes, as the core logic for R5 SPL branch-only boot is already
> present. The boot media supported is _only_ SDCard just like with
> J721E SoCs. Firmware images to be used are the non-ATCM images.
> 
> The series is on top of the previous "Early-boot support of R5FSS from
> A72 U-Boot for J7200 SoCs" [1].
> 
> Following is the patch summary:
>  - Patch #1 updates the R5 SPL rproc env variables for J7200 SoCs given
>    the different firmware names used between J721E & J7200 SoCs. The
>    Main R5FSS variables are also left out, until the support for the
>    same is added to code.
>  - Patches #2 and #3 add and enable the FS_LOADER node and Kconfigs

Applied to u-boot-ti next branch.

Thanks and regards,
Lokesh

      parent reply	other threads:[~2020-09-15 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 19:09 [PATCH 0/3] MCU R5F branch-only boot on J7200 SoCs Suman Anna
2020-08-18 19:09 ` [PATCH 1/3] env: ti: j721e-evm: Update R5 SPL rproc env variables for J7200 Suman Anna
2020-08-18 19:09 ` [PATCH 2/3] arm: dts: k3-j7200-r5: Add fs_loader node Suman Anna
2020-08-19 22:45   ` Suman Anna
2020-08-18 19:09 ` [PATCH 3/3] configs: j7200_evm_r5: Enable FS_LOADER Suman Anna
2020-09-15 13:48 ` Lokesh Vutla [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=d14371a0-69f8-c4e2-55b1-f152f1d8fa71@ti.com \
    --to=lokeshvutla@ti.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 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.