path: root/Documentation/DocBook/media/v4l
diff options
authorSakari Ailus <sakari.ailus@iki.fi>2012-10-21 15:30:02 -0300
committerMauro Carvalho Chehab <mchehab@redhat.com>2012-10-28 17:49:20 -0200
commite7d993550167ef810b6658fc7b0a73517c2ed957 (patch)
tree0dbb172e36d38d89fee273fab7b6d62afb7c09f8 /Documentation/DocBook/media/v4l
parent8e216e50ddca0550ffd477ce27e843a506b3ae2e (diff)
[media] v4l: Correct definition of v4l2_buffer.flags related to cache management
V4L2_BUF_FLAG_NO_CACHE_INVALIDATE and V4L2_BUF_FLAG_NO_CACHE_CLEAN were define incorrectly in the documentation. Fix this by changing the documentation to match reality. Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'Documentation/DocBook/media/v4l')
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/DocBook/media/v4l/io.xml b/Documentation/DocBook/media/v4l/io.xml
index b5d1cbdc558..7e2f3d7d78a 100644
--- a/Documentation/DocBook/media/v4l/io.xml
+++ b/Documentation/DocBook/media/v4l/io.xml
@@ -923,7 +923,7 @@ application. Drivers set or clear this flag when the
- <entry>0x0400</entry>
+ <entry>0x0800</entry>
<entry>Caches do not have to be invalidated for this buffer.
Typically applications shall use this flag if the data captured in the buffer
is not going to be touched by the CPU, instead the buffer will, probably, be
@@ -932,7 +932,7 @@ passed on to a DMA-capable hardware unit for further processing or output.
- <entry>0x0800</entry>
+ <entry>0x1000</entry>
<entry>Caches do not have to be cleaned for this buffer.
Typically applications shall use this flag for output buffers if the data
in this buffer has not been created by the CPU but by some DMA-capable unit,