From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Igor Opaniuk <igor.opaniuk@foundries.io>, u-boot@lists.denx.de
Cc: Igor Opaniuk <igor.opaniuk@gmail.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>,
Bin Meng <bmeng@tinylab.org>,
Francis Laniel <francis.laniel@amarulasolutions.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Roger Knecht <rknecht@pm.me>,
Sean Edmond <seanedmond@microsoft.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v1 3/5] cmd: optee_rpmb: build cmd for sandbox
Date: Thu, 15 Feb 2024 10:52:37 +0100 [thread overview]
Message-ID: <87y1bmxdei.fsf@baylibre.com> (raw)
In-Reply-To: <20240214183444.493629-4-igor.opaniuk@gmail.com>
Hi Igor,
Thank you for the patch.
On mer., févr. 14, 2024 at 19:34, Igor Opaniuk <igor.opaniuk@foundries.io> wrote:
> Support CMD_OPTEE_RPMB for SANDBOX configurations.
> Test:
>
> $ ./u-boot -d arch/sandbox/dts/test.dtb
> ...
> => optee_rpmb write_pvalue test_variable test_value
> Wrote 11 bytes
> => optee_rpmb read_pvalue test_variable 11
> Read 11 bytes, value = test_value
>
> Signed-off-by: Igor Opaniuk <igor.opaniuk@gmail.com>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Tested-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> # on sandbox
> ---
>
> cmd/Kconfig | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/cmd/Kconfig b/cmd/Kconfig
> index a86b5705174..8ad8c0c542c 100644
> --- a/cmd/Kconfig
> +++ b/cmd/Kconfig
> @@ -1370,7 +1370,9 @@ config CMD_CLONE
>
> config CMD_OPTEE_RPMB
> bool "Enable read/write support on RPMB via OPTEE"
> - depends on SUPPORT_EMMC_RPMB && OPTEE
> + depends on (SUPPORT_EMMC_RPMB && OPTEE) || SANDBOX_TEE
> + default y if SANDBOX_TEE
> + select OPTEE_TA_AVB if SANDBOX_TEE
> help
> Enable the commands for reading, writing persistent named values
> in the Replay Protection Memory Block partition in eMMC by
> --
> 2.34.1
next prev parent reply other threads:[~2024-02-15 9:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 18:34 [PATCH v1 0/5] TEE: minor cleanup Igor Opaniuk
2024-02-14 18:34 ` [PATCH v1 1/5] tee: optee: fix description in Kconfig Igor Opaniuk
2024-02-14 21:40 ` Heinrich Schuchardt
2024-03-01 6:53 ` Ilias Apalodimas
2024-02-14 18:34 ` [PATCH v1 2/5] tee: sandbox: fix spelling errors Igor Opaniuk
2024-02-14 21:41 ` Heinrich Schuchardt
2024-03-01 6:55 ` Ilias Apalodimas
2024-02-14 18:34 ` [PATCH v1 3/5] cmd: optee_rpmb: build cmd for sandbox Igor Opaniuk
2024-02-15 9:52 ` Mattijs Korpershoek [this message]
2024-02-14 18:34 ` [PATCH v1 4/5] test: py: add optee_rpmb tests Igor Opaniuk
2024-02-14 18:34 ` [PATCH v1 5/5] tee: remove common.h inclusion Igor Opaniuk
2024-02-29 19:11 ` [PATCH v1 0/5] TEE: minor cleanup Igor Opaniuk
2024-02-29 19:25 ` Peter Robinson
2024-02-29 19:38 ` Tom Rini
2024-03-01 9:40 ` Ilias Apalodimas
2024-03-02 22:02 ` Igor Opaniuk
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=87y1bmxdei.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=abdellatif.elkhlifi@arm.com \
--cc=bmeng@tinylab.org \
--cc=francis.laniel@amarulasolutions.com \
--cc=igor.opaniuk@foundries.io \
--cc=igor.opaniuk@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=rknecht@pm.me \
--cc=seanedmond@microsoft.com \
--cc=sjg@chromium.org \
--cc=takahiro.akashi@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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.