From: ilias.apalodimas@linaro.org
To: Sughosh Ganu <sughosh.ganu@linaro.org>
Cc: devel@edk2.groups.io, Ard Biesheuvel <ard.biesheuvel@arm.com>,
Leif Lindholm <leif@nuviainc.com>
Subject: Re: [PATCH edk2-platforms v1 1/2] Drivers/OpTeeRpmb: Add an OP-TEE backed RPMB driver
Date: Wed, 21 Oct 2020 18:30:07 +0300 [thread overview]
Message-ID: <20201021153007.GA1921694@apalos.home> (raw)
In-Reply-To: <20201021113534.25671-2-sughosh.ganu@linaro.org>
Hi Sughosh
On Wed, Oct 21, 2020 at 05:05:33PM +0530, Sughosh Ganu wrote:
> +
[...]
> +#ifndef __OPTEE_RPMB_FV_
> +#define __OPTEE_RPMB_FV_
> +
> +/* SVC Args */
> +#define SP_SVC_RPMB_READ 0xC4000066
> +#define SP_SVC_RPMB_WRITE 0xC4000067
> +#define SP_SVC_GET_UART 0xC4000068
> +
> +#define FILENAME "EFI_VARS"
> +
> +#define NBLOCKS (3 * 16) // EFI Vars, FTW working, FTW spare
> +#define BLOCK_SIZE SIZE_4KB
> +#define FLASH_SIGNATURE SIGNATURE_32('r', 'p', 'm', 'b')
> +#define INSTANCE_FROM_FVB_THIS(a) CR(a, MEM_INSTANCE, FvbProtocol, \
> + FLASH_SIGNATURE)
> +enum _RPMB_FILE_MAP {
> + EFI_VARS,
> + FTW_WORK,
> + FTW_SPARE,
> +};
> +
> +typedef enum _RPMB_FILE_MAP RPMB_FILE_MAP;
> +
> +struct _MAP_VAL_TO_FILE {
> + CHAR8 *Filename;
> + RPMB_FILE_MAP Map;
> +};
> +
> +typedef struct _MAP_VAL_TO_FILE MAP_VAL_TO_FILE;
_RPMB_FILE_MAP and friends was a left over from the first version of the driver,
and somehow slipped in.
They don't affect the code at all, but we should remove them on v2.
[...]
Regards
/Ilias
next prev parent reply other threads:[~2020-10-21 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 11:35 [PATCH edk2-platforms v1 0/2] Add support for running StandaloneMm as OP-TEE TA Sughosh Ganu
2020-10-21 11:35 ` [PATCH edk2-platforms v1 1/2] Drivers/OpTeeRpmb: Add an OP-TEE backed RPMB driver Sughosh Ganu
2020-10-21 15:30 ` ilias.apalodimas [this message]
2020-10-21 11:35 ` [PATCH edk2-platforms v1 2/2] StMMRpmb: Add support for building StandaloneMm image for OP-TEE Sughosh Ganu
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-list 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=20201021153007.GA1921694@apalos.home \
--to=devel@edk2.groups.io \
/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