public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: sbabic at denx.de <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot]  [PATCH] Revert "drivers/crypto/fsl: assign job-rings to
Date: Mon, 10 Jun 2019 09:40:41 +0000 (UTC)	[thread overview]
Message-ID: <20190610095256.4FD93C21FDA@lists.denx.de> (raw)

> Commit 22191ac35344 ("drivers/crypto/fsl: assign job-rings to
>  non-TrustZone") breaks HABv4 encrypted boot support in the
> following i.MX devices:
> - i.MX6UL
> - i.MX7S
> - i.MX7D
> - i.MX7ULP
> For preparing a HABv4 encrypted boot image it's necessary to
> encapsulate the generated DEK in a blob. In devices listed
> above the blob generation function takes into consideration
> the Job Ring TrustZone ownership configuration (JROWN_NS)
> and can be only decapsulated by the same configuration.
> The ROM code expects DEK blobs encapsulated by the Secure World
> environments which commonly have JROWN_NS = 0.
> As U-Boot is running in Secure World we must have JROWN_NS = 0
> so the blobs generated by dek_blob tool can be decapsulated
> by the ROM code.
> Job-rings assignment is now handled in OP-TEE OS, this commit can
> be safely reverted.
> https://github.com/OP-TEE/optee_os/pull/2986
> This reverts commit 22191ac353445ad8fafc5a78aefcd94e78963041.
> Signed-off-by: Breno Lima <breno.lima@nxp.com>
> Reviewed-by: Fabio Estevam <festevam@gmail.com>
> Acked-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>

Applied to u-boot-imx, master, thanks !

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

                 reply	other threads:[~2019-06-10  9:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190610095256.4FD93C21FDA@lists.denx.de \
    --to=sbabic@denx.de \
    --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