All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Schenker <dev@pschenker.ch>
To: u-boot@lists.denx.de
Cc: stefan@embear.ch,
	Philippe Schenker <philippe.schenker@impulsing.ch>,
	Andrew Davis <afd@ti.com>,
	Andrew Goodbody <andrew.goodbody@linaro.org>,
	Beleswar Padhi <b-padhi@ti.com>,
	Daniel Schultz <d.schultz@phytec.de>,
	Hari Nagalla <hnagalla@ti.com>, Judith Mendez <jm@ti.com>,
	Neha Malcom Francis <n-francis@ti.com>,
	Tom Rini <trini@konsulko.com>
Subject: [PATCH v1 0/6] remoteproc: k3-r5: Build fixes and security improvements
Date: Thu, 23 Oct 2025 11:46:18 +0200	[thread overview]
Message-ID: <20251023094631.16742-1-dev@pschenker.ch> (raw)

From: Philippe Schenker <philippe.schenker@impulsing.ch>


This series fixes compilation errors when building for R5 cores and
addresses a security issue where authenticated images were not being
used correctly.

Patch 1: Cosmetic removal of duplicate code

Patches 2-3: Fix build errors caused by type mismatches between
function signatures and the types used in R5 builds.

Patches 4-5: fix a bug where ti_secure_image_post_process() relocates
images during authentication, but callers were still using the original
unverified addresses.

Patch 6: Implements is_running operation to allow querying R5F core status.

Note: If preferred, I can split this series.


Philippe Schenker (6):
  arm: dts: k3-am642-evm: Remove duplicate node
  remoteproc: k3-r5: cast size to size_t
  soc: ti: pruss: Fix size ptr type in probe
  mach-k3: security: Propagate verified image addr
  remoteproc: k3-r5: Use verified image address
  remoteproc: k3-r5: Implement is_running operation

 arch/arm/dts/k3-am642-evm-u-boot.dtsi |  4 ----
 arch/arm/mach-k3/security.c           |  2 ++
 drivers/remoteproc/ti_k3_r5f_rproc.c  | 23 ++++++++++++++++++++---
 drivers/soc/ti/pruss.c                |  2 +-
 4 files changed, 23 insertions(+), 8 deletions(-)

-- 
2.51.1

base-commit: 813a0df27a8af587bd25a6a4719f68066b370091
branch: am64x-various-fixes__master

             reply	other threads:[~2025-10-23  9:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-23  9:46 Philippe Schenker [this message]
2025-10-23  9:46 ` [PATCH v1 1/6] arm: dts: k3-am642-evm: Remove duplicate node Philippe Schenker
2025-10-23  9:46 ` [PATCH v1 2/6] remoteproc: k3-r5: cast size to size_t Philippe Schenker
2025-10-23 14:22   ` Andrew Davis
2025-10-23  9:46 ` [PATCH v1 3/6] soc: ti: pruss: Fix size ptr type in probe Philippe Schenker
2025-10-23  9:46 ` [PATCH v1 4/6] mach-k3: security: Propagate verified image addr Philippe Schenker
2025-10-23 14:24   ` Andrew Davis
2025-11-06 12:33     ` Philippe Schenker
2025-10-23  9:46 ` [PATCH v1 5/6] remoteproc: k3-r5: Use verified image address Philippe Schenker
2025-10-23  9:46 ` [PATCH v1 6/6] remoteproc: k3-r5: Implement is_running operation Philippe Schenker
2025-11-06 19:35 ` [PATCH v1 0/6] remoteproc: k3-r5: Build fixes and security improvements Tom Rini
2025-11-07  8:21   ` Philippe Schenker

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=20251023094631.16742-1-dev@pschenker.ch \
    --to=dev@pschenker.ch \
    --cc=afd@ti.com \
    --cc=andrew.goodbody@linaro.org \
    --cc=b-padhi@ti.com \
    --cc=d.schultz@phytec.de \
    --cc=hnagalla@ti.com \
    --cc=jm@ti.com \
    --cc=n-francis@ti.com \
    --cc=philippe.schenker@impulsing.ch \
    --cc=stefan@embear.ch \
    --cc=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 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.