U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Judith Mendez <jm@ti.com>
To: Tom Rini <trini@konsulko.com>, <u-boot@lists.denx.de>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Hari Nagalla <hnagalla@ti.com>, Andrew Davis <afd@ti.com>,
	Daniel Schultz <d.schultz@phytec.de>
Subject: Re: [PATCH v3 0/4] Introduce K3 remoteproc driver for M4 subsystem
Date: Tue, 4 Feb 2025 13:11:52 -0600	[thread overview]
Message-ID: <7d568824-8829-4eba-ba97-70bdae0e1ed3@ti.com> (raw)
In-Reply-To: <20250130223256.1944522-1-jm@ti.com>

Hi all,

On 1/30/25 4:32 PM, Judith Mendez wrote:
> Some K3 devices like am62x and am64x have a M4 processor in the MCU
> voltage domain. This patch series introduces remoteproc M4 driver which
> will be used to load firmware into and start the M4 remote core.
> 
> This series also adds support for R5F cores on am64x SoCs in patch 2/4,
> sets up environment to load FW in remote cores in patch 3/4, and enables
> config options for R5F and M4 remoteproc support in patch 4/4.
> 
> This patch series was tested on am64x EVM using commands:
> 
> => setenv dorprocboot 1
> => run boot_rprocs
> 

I have missed one warning introduced by the driver in this patch series,
so will respin one more time to add the fix.

~ Judith


      parent reply	other threads:[~2025-02-04 19:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30 22:32 [PATCH v3 0/4] Introduce K3 remoteproc driver for M4 subsystem Judith Mendez
2025-01-30 22:32 ` [PATCH v3 1/4] remoteproc: k3-m4: Introduce K3 remote proc " Judith Mendez
2025-01-30 22:32 ` [PATCH v3 2/4] remoteproc: k3-r5: Add support for R5F cores on AM64x SoCs Judith Mendez
2025-01-30 22:32 ` [PATCH v3 3/4] env: ti: am64x: set rproc_fw_binaries Judith Mendez
2025-01-30 22:32 ` [PATCH v3 4/4] configs: am64x_evm_a53_defconfig: Enable R5F and M4 remote proc support Judith Mendez
2025-02-04 19:11 ` Judith Mendez [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=7d568824-8829-4eba-ba97-70bdae0e1ed3@ti.com \
    --to=jm@ti.com \
    --cc=afd@ti.com \
    --cc=d.schultz@phytec.de \
    --cc=hnagalla@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.com \
    /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