public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sumit Garg <sumit.garg@kernel.org>
To: u-boot-qcom@groups.io, u-boot@lists.denx.de
Cc: trini@konsulko.com, casey.connolly@linaro.org,
	neil.armstrong@linaro.org, jens.wiklander@linaro.org,
	ilias.apalodimas@linaro.org, jorge.ramirez@oss.qualcomm.com,
	varadarajan.narayanan@oss.qualcomm.com, tonyh@qti.qualcomm.com,
	Sumit Garg <sumit.garg@oss.qualcomm.com>
Subject: Re: [PATCH v3 0/3] mach-snapdragon: Enable OP-TEE support
Date: Tue, 24 Mar 2026 17:17:08 +0530	[thread overview]
Message-ID: <acJ5vEZ2F46NS_xV@sumit-xelite> (raw)
In-Reply-To: <20260127062341.723966-1-sumit.garg@kernel.org>

Hey Casey,

On Tue, Jan 27, 2026 at 11:53:38AM +0530, Sumit Garg wrote:
> From: Sumit Garg <sumit.garg@oss.qualcomm.com>
> 
> Introduce TF-A and OP-TEE config fragment
> 
> Recently upstream TF-A/OP-TEE has started gaining support for Qcom
> platforms. RB3Gen2 being the first one and more to come. U-Boot in
> corresponding boot flow is packaged as a position independent executable.
> 
> So, lets add a generic U-Boot config fragment for Qcom platforms to
> support TF-A/OP-TEE based TrustZone stack. Build command:
> 
> $ ./scripts/kconfig/merge_config.sh \
>        configs/qcom_defconfig \
>        board/qualcomm/tfa-optee.config
> $ make -j`nproc` DEVICE_TREE=qcom/qcs6490-rb3gen2
> 
> ---
> Changes in v3:
> - Incorporated misc. comments on patch #2.
> 

Can we get this patch-set applied as well? Have been waiting on the list
for approx. 2 months.

-Sumit

> Changes in v2:
> - Add new patch #1 to export OP-TEE message UID check API
> - Use OP-TEE message UID check API in order to perform the DT fixup for
>   OP-TEE.
> - Switch from new defconfig to a config fragment instead.
> 
> Sumit Garg (3):
>   tee: optee: Export OP-TEE message UID check API
>   mach-snapdragon: of_fixup: Add OP-TEE DT fixup support
>   board/qualcomm: Introduce TF-A and OP-TEE config fragment
> 
>  arch/arm/mach-snapdragon/of_fixup.c | 35 +++++++++++++++++++++++++++++
>  board/qualcomm/tfa-optee.config     |  4 ++++
>  drivers/tee/optee/core.c            |  5 +++++
>  include/tee/optee.h                 |  9 ++++++++
>  4 files changed, 53 insertions(+)
>  create mode 100644 board/qualcomm/tfa-optee.config
> 
> -- 
> 2.51.0
> 

  parent reply	other threads:[~2026-03-24 11:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  6:23 [PATCH v3 0/3] mach-snapdragon: Enable OP-TEE support Sumit Garg
2026-01-27  6:23 ` [PATCH v3 1/3] tee: optee: Export OP-TEE message UID check API Sumit Garg
2026-02-09 18:53   ` Casey Connolly
2026-01-27  6:23 ` [PATCH v3 2/3] mach-snapdragon: of_fixup: Add OP-TEE DT fixup support Sumit Garg
2026-02-09 18:49   ` Casey Connolly
2026-02-10  5:20     ` Sumit Garg
2026-01-27  6:23 ` [PATCH v3 3/3] board/qualcomm: Introduce TF-A and OP-TEE config fragment Sumit Garg
2026-02-09 18:53   ` Casey Connolly
2026-03-24 11:47 ` Sumit Garg [this message]
2026-03-24 11:50   ` [PATCH v3 0/3] mach-snapdragon: Enable OP-TEE support Casey Connolly
2026-04-06 12:40     ` Sumit Garg

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=acJ5vEZ2F46NS_xV@sumit-xelite \
    --to=sumit.garg@kernel.org \
    --cc=casey.connolly@linaro.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jens.wiklander@linaro.org \
    --cc=jorge.ramirez@oss.qualcomm.com \
    --cc=neil.armstrong@linaro.org \
    --cc=sumit.garg@oss.qualcomm.com \
    --cc=tonyh@qti.qualcomm.com \
    --cc=trini@konsulko.com \
    --cc=u-boot-qcom@groups.io \
    --cc=u-boot@lists.denx.de \
    --cc=varadarajan.narayanan@oss.qualcomm.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