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@xxxxxxxxxxxx> wrote:
>
> Hi,
>
> Le mercredi 03 avril 2024 à 18:26 +0800, Shawn Sung a écrit :
> > From: "Jason-JH.Lin" <jason-jh.lin@xxxxxxxxxxxx>
> >
> > 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@xxxxxxxxxxxx>
> > Signed-off-by: Hsiao Chien Sung <shawn.sung@xxxxxxxxxxxx>
> > ---
> > 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
> >
> > #define DRM_IOCTL_MTK_GEM_CREATE DRM_IOWR(DRM_COMMAND_BASE + \
> > DRM_MTK_GEM_CREATE, struct drm_mtk_gem_create)
>
>
