From: Olivier Masse <olivier.masse@nxp.com>
To: "sumit.garg@linaro.org" <sumit.garg@linaro.org>
Cc: "sumit.semwal@linaro.org" <sumit.semwal@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"christian.koenig@amd.com" <christian.koenig@amd.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Clément Faure" <clement.faure@nxp.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"jens.wiklander@linaro.org" <jens.wiklander@linaro.org>,
"op-tee@lists.trustedfirmware.org"
<op-tee@lists.trustedfirmware.org>,
"etienne.carriere@linaro.org" <etienne.carriere@linaro.org>
Subject: Re: [EXT] Re: [PATCH v2 0/1] tee: Add tee_shm_register_fd
Date: Thu, 8 Sep 2022 09:18:43 +0000 [thread overview]
Message-ID: <fb641c168a6b9fc041785a0baa8ee4b2d3ff8ed4.camel@nxp.com> (raw)
In-Reply-To: <CAFA6WYM89+SrW2Br-fnFke4djt4GgGHXn7JS3=rxvAa7dAAY7w@mail.gmail.com>
Hi Sumit
On ven., 2022-08-19 at 13:54 +0530, Sumit Garg wrote:
> Caution: EXT Email
>
> Hi Olivier,
>
> On Fri, 12 Aug 2022 at 20:01, Olivier Masse <olivier.masse@nxp.com>
> wrote:
> >
> > Add a new ioctl called TEE_IOC_SHM_REGISTER_FD to register a
> > shared memory from a dmabuf file descriptor.
> > This new ioctl will allow the Linux Kernel to register a buffer
> > to be used by the Secure Data Path OPTEE OS feature.
> >
> > Please find more information here:
> >
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstatic.linaro.org%2Fconnect%2Fsan19%2Fpresentations%2Fsan19-107.pdf&data=05%7C01%7Colivier.masse%40nxp.com%7C05071ff1c28044ab740908da81bc44e2%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637964942860947359%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nYLb2iMoJExdKEg4CL4eW5%2FQ%2Bqqj4Iw1TxFsd1UqWW0%3D&reserved=0
> >
> > Patch tested on Hikey 6220.
> >
>
> AFAIU, for the OP-TEE SDP feature to work you need to have a DMA-BUF
> heap driver for allocating secure buffers through exposed chardev:
> "/dev/dma_heap/sdp". Have you tested it with some out-of-tree driver
> as I can't find it upstream? Also, do you plan to push that upstream
> as well?
It has been tested with linaro,secure-heap reserved dma heap memory
which is also in review for upstream.
>
> BTW, please add a changelog while sending newer patch-set versions.
>
> -Sumit
>
> > Etienne Carriere (1):
> > tee: new ioctl to a register tee_shm from a dmabuf file
> > descriptor
> >
> > drivers/tee/tee_core.c | 38 +++++++++++++++
> > drivers/tee/tee_shm.c | 99
> > +++++++++++++++++++++++++++++++++++++++-
> > include/linux/tee_drv.h | 11 +++++
> > include/uapi/linux/tee.h | 29 ++++++++++++
> > 4 files changed, 175 insertions(+), 2 deletions(-)
> >
> > --
> > 2.25.0
> >
next prev parent reply other threads:[~2022-09-08 9:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 14:30 Olivier Masse
2022-08-12 14:30 ` [PATCH 1/1] tee: new ioctl to a register tee_shm from a dmabuf file descriptor Olivier Masse
2022-08-14 1:13 ` kernel test robot
2023-01-27 10:54 ` [PATCH v2 " Olivier Masse
2023-01-27 11:19 ` Christian König
2023-01-30 13:04 ` Etienne Carriere
2023-02-01 5:33 ` Sumit Garg
2023-02-02 7:56 ` [EXT] " Cyrille Fleury
2023-02-02 8:35 ` Sumit Garg
2023-02-02 9:58 ` Etienne Carriere
2023-02-03 11:01 ` Olivier Masse
2023-02-03 11:37 ` Etienne Carriere
2023-02-03 12:31 ` Jerome Forissier
2023-02-03 14:13 ` Cyrille Fleury
2023-02-13 11:02 ` Jens Wiklander
2023-02-13 12:41 ` Cyrille Fleury
2023-02-13 15:22 ` Jens Wiklander
2023-02-03 11:52 ` Sumit Garg
2022-08-16 8:17 ` [PATCH v2 0/1] tee: Add tee_shm_register_fd Jens Wiklander
2022-08-16 9:06 ` [EXT] " Olivier Masse
2022-08-19 8:24 ` Sumit Garg
2022-09-06 19:59 ` Daniel Vetter
2022-09-08 10:26 ` Sumit Garg
2022-09-08 9:18 ` Olivier Masse [this message]
2022-09-08 10:28 ` [EXT] " Sumit Garg
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=fb641c168a6b9fc041785a0baa8ee4b2d3ff8ed4.camel@nxp.com \
--to=olivier.masse@nxp.com \
--cc=christian.koenig@amd.com \
--cc=clement.faure@nxp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etienne.carriere@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@linaro.org \
--cc=sumit.semwal@linaro.org \
/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
Powered by JetHome