public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] drivers: optee: rpmb: fix returning CID to TEE
Date: Thu, 5 Dec 2019 17:09:43 -0500	[thread overview]
Message-ID: <20191205220943.GZ9549@bill-the-cat> (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>
> Reviewed-by: Jens Wiklander <jens.wiklander@linaro.org>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191205/46b46695/attachment.sig>

  parent reply	other threads:[~2019-12-05 22:09 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
2019-12-05 22:09 ` Tom Rini [this message]
  -- 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=20191205220943.GZ9549@bill-the-cat \
    --to=trini@konsulko.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox