[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a4211070f1c895d776e3d9dee9ae3113de8c976.camel@mediatek.com>
Date: Wed, 17 Apr 2024 08:41:44 +0000
From: Jason-JH Lin (林睿祥) <Jason-JH.Lin@...iatek.com>
To: "jkardatzke@...gle.com" <jkardatzke@...gle.com>, "nicolas@...fresne.ca"
<nicolas@...fresne.ca>
CC: "sumit.semwal@...aro.org" <sumit.semwal@...aro.org>,
"linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linaro-mm-sig@...ts.linaro.org" <linaro-mm-sig@...ts.linaro.org>,
"christian.koenig@....com" <christian.koenig@....com>,
"chunkuang.hu@...nel.org" <chunkuang.hu@...nel.org>, "tzimmermann@...e.de"
<tzimmermann@...e.de>, Shawn Sung (宋孝謙)
<Shawn.Sung@...iatek.com>, "mripard@...nel.org" <mripard@...nel.org>,
"daniel@...ll.ch" <daniel@...ll.ch>, "p.zabel@...gutronix.de"
<p.zabel@...gutronix.de>, "maarten.lankhorst@...ux.intel.com"
<maarten.lankhorst@...ux.intel.com>, "dri-devel@...ts.freedesktop.org"
<dri-devel@...ts.freedesktop.org>, "linux-media@...r.kernel.org"
<linux-media@...r.kernel.org>, "airlied@...il.com" <airlied@...il.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "matthias.bgg@...il.com"
<matthias.bgg@...il.com>, "angelogioacchino.delregno@...labora.com"
<angelogioacchino.delregno@...labora.com>
Subject: Re: [PATCH v5 1/9] drm/mediatek/uapi: Add
DRM_MTK_GEM_CREATE_ENCRYPTED flag
On Tue, 2024-04-16 at 10:19 -0700, Jeffrey Kardatzke wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> I would argue 'restricted' is the proper name since that was what
> was
> settled on for the dma-buf code. :) But you are definitely right
> that this memory is not encrypted.
>
>
> On Tue, Apr 16, 2024 at 7:09 AM Nicolas Dufresne <
> nicolas@...fresne.ca> wrote:
> >
> > Hi,
> >
> > Le mercredi 03 avril 2024 à 18:26 +0800, Shawn Sung a écrit :
> > > From: "Jason-JH.Lin" <jason-jh.lin@...iatek.com>
> > >
> > > Add DRM_MTK_GEM_CREATE_ENCRYPTED flag to allow user to allocate
> >
> > Is "ENCRYPTED" a proper naming ? My expectation is that this would
> hold data in
> > a PROTECTED memory region but that no cryptographic algorithm will
> be involved.
> >
> > Nicolas
> >
> > > a secure buffer to support secure video path feature.
> > >
> > > Signed-off-by: Jason-JH.Lin <jason-jh.lin@...iatek.com>
> > > Signed-off-by: Hsiao Chien Sung <shawn.sung@...iatek.com>
> > > ---
> > > include/uapi/drm/mediatek_drm.h | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/include/uapi/drm/mediatek_drm.h
> b/include/uapi/drm/mediatek_drm.h
> > > index b0dea00bacbc4..e9125de3a24ad 100644
> > > --- a/include/uapi/drm/mediatek_drm.h
> > > +++ b/include/uapi/drm/mediatek_drm.h
> > > @@ -54,6 +54,7 @@ struct drm_mtk_gem_map_off {
> > >
> > > #define DRM_MTK_GEM_CREATE 0x00
> > > #define DRM_MTK_GEM_MAP_OFFSET 0x01
> > > +#define DRM_MTK_GEM_CREATE_ENCRYPTED 0x02
OK, I'll change this to DRM_MTK_GEM_CREATE_RESTRICTED at the next
version.
Regards,
Jason-JH.Lin
> > >
> > > #define DRM_IOCTL_MTK_GEM_CREATE DRM_IOWR(DRM_COMMAND_BASE +
> \
> > > DRM_MTK_GEM_CREATE, struct drm_mtk_gem_create)
> >
> >
Powered by blists - more mailing lists