mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 1/2] optee: Explicitly ignore OPTEE_RPC_CMD_RPMB_*
Date: Thu, 19 Mar 2026 08:03:03 +0100	[thread overview]
Message-ID: <20260319070304.1965024-1-s.hauer@pengutronix.de> (raw)

We do not implement OPTEE_RPC_CMD_RPMB_* which are needed for the new
in-kernel RPMB handling which we don't implement. For now we emulate a
tee-supplicant for RPMB handling, so there's no need to warn about these
not being implemented.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
 drivers/tee/optee/rpc.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/drivers/tee/optee/rpc.c b/drivers/tee/optee/rpc.c
index bc398a625b..b91833d53a 100644
--- a/drivers/tee/optee/rpc.c
+++ b/drivers/tee/optee/rpc.c
@@ -69,7 +69,12 @@ void optee_rpc_cmd(struct tee_context *ctx, struct optee *optee,
 		break;
 	default:
 		pr_notice_once("optee: No supplicant or RPC handler for command 0x%x\n", arg->cmd);
+		fallthrough;
+	case OPTEE_RPC_CMD_RPMB_PROBE_RESET:
+	case OPTEE_RPC_CMD_RPMB_PROBE_NEXT:
+	case OPTEE_RPC_CMD_RPMB_FRAMES:
 		arg->ret = TEEC_ERROR_NOT_IMPLEMENTED;
+		break;
 	}
 
 	arg->ret_origin = TEEC_ORIGIN_COMMS;
-- 
2.47.3




             reply	other threads:[~2026-03-19  7:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19  7:03 Sascha Hauer [this message]
2026-03-19  7:03 ` [PATCH 2/2] optee: skip registration of already known TEE bus devices Sascha Hauer
2026-03-20  9:09   ` [PATCH] fixup! " Sascha Hauer
2026-03-20  6:35 ` [PATCH 1/2] optee: Explicitly ignore OPTEE_RPC_CMD_RPMB_* Sascha Hauer

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=20260319070304.1965024-1-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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