All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] drivers: optee: rpmb: fix returning CID to TEE
Date: Wed, 27 Nov 2019 08:53:59 +0100	[thread overview]
Message-ID: <20191127075358.GA13420@jax> (raw)
In-Reply-To: <20191126161934.7826-1-jorge@foundries.io>

On Tue, Nov 26, 2019 at 05:19:34PM +0100, Jorge Ramirez-Ortiz wrote:
> The mmc CID value is one of the input parameters used to provision the
> RPMB key. The trusted execution environment expects this value to be
> specified in big endian format.
> 
> Before this fix, on little endian systems, the value returned by the
> linux kernel mmc driver differed from the one returned by u-boot.
> This meant that if linux provisioned the RPMB key, u-boot would not
> have access to the partition (and the other way around).
> 
> Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io>

Looks good to me:
Reviewed-by: Jens Wiklander <jens.wiklander@linaro.org>

Thanks,
Jens

> ---
>  drivers/tee/optee/rpmb.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/tee/optee/rpmb.c b/drivers/tee/optee/rpmb.c
> index 955155b3f8..cf1ce77e6e 100644
> --- a/drivers/tee/optee/rpmb.c
> +++ b/drivers/tee/optee/rpmb.c
> @@ -98,6 +98,7 @@ static struct mmc *get_mmc(struct optee_private *priv, int dev_id)
>  static u32 rpmb_get_dev_info(u16 dev_id, struct rpmb_dev_info *info)
>  {
>  	struct mmc *mmc = find_mmc_device(dev_id);
> +	int i;
>  
>  	if (!mmc)
>  		return TEE_ERROR_ITEM_NOT_FOUND;
> @@ -105,7 +106,9 @@ static u32 rpmb_get_dev_info(u16 dev_id, struct rpmb_dev_info *info)
>  	if (!mmc->ext_csd)
>  		return TEE_ERROR_GENERIC;
>  
> -	memcpy(info->cid, mmc->cid, sizeof(info->cid));
> +	for (i = 0; i < ARRAY_SIZE(mmc->cid); i++)
> +		((u32 *) info->cid)[i] = cpu_to_be32(mmc->cid[i]);
> +
>  	info->rel_wr_sec_c = mmc->ext_csd[222];
>  	info->rpmb_size_mult = mmc->ext_csd[168];
>  	info->ret_code = RPMB_CMD_GET_DEV_INFO_RET_OK;
> -- 
> 2.17.1
> 

  reply	other threads:[~2019-11-27  7:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 16:19 [U-Boot] [PATCH] drivers: optee: rpmb: fix returning CID to TEE Jorge Ramirez-Ortiz
2019-11-27  7:53 ` Jens Wiklander [this message]
2019-12-05 22:09 ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2019-11-15 21:37 Jorge Ramirez-Ortiz
2019-11-18  9:36 ` Jens Wiklander
2019-11-18 11:18   ` Jorge Ramirez-Ortiz
2019-11-18 12:42     ` Jens Wiklander
2019-11-18 13:18       ` Jorge Ramirez-Ortiz
2019-11-19  9:02         ` Jens Wiklander
2019-11-19 11:53           ` Jorge Ramirez-Ortiz
2019-11-19 17:21             ` Jorge Ramirez-Ortiz
2019-11-20  7:20               ` Jens Wiklander
2019-11-20  8:21                 ` Jorge Ramirez-Ortiz
2019-11-20 10:33                   ` Jens Wiklander
2019-11-26  8:22                     ` Jorge
2019-11-26 11:46                       ` Jens Wiklander
2019-11-26 15:41                         ` Jorge

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=20191127075358.GA13420@jax \
    --to=jens.wiklander@linaro.org \
    --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.