From: Jorge Ramirez-Ortiz, Foundries <jorge@foundries.io>
To: u-boot@lists.denx.de
Subject: [PATCH] drivers: tee: i2c trampoline driver
Date: Tue, 29 Dec 2020 09:30:05 +0100 [thread overview]
Message-ID: <20201229083005.GA15607@trex> (raw)
In-Reply-To: <CAPnjgZ2mbCsiFH6jJkWASbAnXycVNDXkqpKszdD4wa+zUGoLLQ@mail.gmail.com>
On 28/12/20, Simon Glass wrote:
> Hi Jorge,
>
> On Mon, 21 Dec 2020 at 11:15, Jorge Ramirez-Ortiz <jorge@foundries.io> wrote:
> >
> > This commit gives the secure world access to the I2C bus so it can
> > communicate with I2C slaves (tipically those would be secure elements
>
> typically
ok
>
> > like the NXP SE050).
> >
> > Tested on imx8mmevk.
>
> We don't seem to have any optee tests in U-Boot at present. I vaguely
> recall they were coming at some point. I think we need:
>
> - a sandbox fake drive for optee, that understands and responds to the
> 6 uclass calls at a basic level
> - an update to get_invoke_func() that provides a sandbox function too
>
> Then we should be able to run optee tests in CI.
>
> It is not a lot of work, but I don't think we should add to optee
> until this is resolved.
um, ok but shouldnt this infrastructure better rest on a maintainer's
roadmap rather than on an off-the-blue request? I mean, had I known I
could have done it in parallel but now I'll need to find the time to
do this.
also notice that Linux's equivalent patchset was merged back in the
summer (ie, this is not untested code).
https://lkml.org/lkml/2020/8/12/276
>
> Regards,
> Simon
> [.]
next prev parent reply other threads:[~2020-12-29 8:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 18:15 [PATCH] drivers: tee: i2c trampoline driver Jorge Ramirez-Ortiz
2020-12-23 8:12 ` Jens Wiklander
2020-12-27 17:06 ` Jorge
2020-12-28 12:35 ` Jens Wiklander
2020-12-29 3:32 ` Simon Glass
2020-12-29 8:30 ` Jorge [this message]
2020-12-29 14:56 ` Simon Glass
2021-01-06 17:23 ` Jorge
2021-01-07 12:36 ` Simon Glass
2021-01-06 13:32 ` Igor Opaniuk
2020-12-29 15:32 ` Simon Glass
2021-01-04 7:19 ` Jens Wiklander
2021-01-06 10:24 ` Jorge
2021-01-06 10:48 ` 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=20201229083005.GA15607@trex \
--to=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.