Hi! > From: Jeffrey Kardatzke <jkardatzke@xxxxxxxxxx> > > Adds documentation for V4L2_MEMORY_FLAG_SECURE. > --- a/Documentation/userspace-api/media/v4l/buffer.rst > +++ b/Documentation/userspace-api/media/v4l/buffer.rst > @@ -696,7 +696,7 @@ enum v4l2_memory > > .. _memory-flags: > > -Memory Consistency Flags > +Memory Flags > ------------------------ > > .. raw:: latex > @@ -728,6 +728,12 @@ Memory Consistency Flags > only if the buffer is used for :ref:`memory mapping <mmap>` I/O and the > queue reports the :ref:`V4L2_BUF_CAP_SUPPORTS_MMAP_CACHE_HINTS > <V4L2-BUF-CAP-SUPPORTS-MMAP-CACHE-HINTS>` capability. > + * .. _`V4L2-MEMORY-FLAG-SECURE`: > + > + - ``V4L2_MEMORY_FLAG_SECURE`` > + - 0x00000002 > + - DMA bufs passed into the queue will be validated to ensure they were > + allocated from a secure dma-heap. Could we get some more information somewhere? Why would userspace want to work with "secure" DMA heaps? How exactly are they different from others? What attacks are these secure against? What is goal of all this? DRM? BR, Pavel -- People of Russia, stop Putin before his war on Ukraine escalates.
Attachment:
signature.asc
Description: PGP signature
