aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/video4linux
diff options
context:
space:
mode:
authorLad, Prabhakar <prabhakar.lad@ti.com>2012-09-14 04:17:52 -0400
committerMauro Carvalho Chehab <mchehab@redhat.com>2012-09-25 07:41:30 -0400
commit83c735379b41a8c07af6a81140e071e87b95dd11 (patch)
tree6ede62a1f0d05623fc5170d860a3b4cb823ccb4e /Documentation/video4linux
parentf9040ef3fab8f6f5f6fced5583203695d08efde3 (diff)
[media] v4l: Documentation: change path of video drivers
due to structure change for video drivers, change the description with correct path. Signed-off-by: Lad, Prabhakar <prabhakar.lad@ti.com> Signed-off-by: Manjunath Hadli <manjunath.hadli@ti.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'Documentation/video4linux')
-rw-r--r--Documentation/video4linux/CQcam.txt2
-rw-r--r--Documentation/video4linux/README.davinci-vpbe20
-rw-r--r--Documentation/video4linux/fimc.txt16
-rw-r--r--Documentation/video4linux/omap3isp.txt2
-rw-r--r--Documentation/video4linux/v4l2-framework.txt2
-rw-r--r--Documentation/video4linux/videobuf2
6 files changed, 22 insertions, 22 deletions
diff --git a/Documentation/video4linux/CQcam.txt b/Documentation/video4linux/CQcam.txt
index 6e680fec1e9c..0b69e4ee8e31 100644
--- a/Documentation/video4linux/CQcam.txt
+++ b/Documentation/video4linux/CQcam.txt
@@ -18,7 +18,7 @@ Table of Contents
18 18
191.0 Introduction 191.0 Introduction
20 20
21 The file ../../drivers/media/video/c-qcam.c is a device driver for 21 The file ../../drivers/media/parport/c-qcam.c is a device driver for
22the Logitech (nee Connectix) parallel port interface color CCD camera. 22the Logitech (nee Connectix) parallel port interface color CCD camera.
23This is a fairly inexpensive device for capturing images. Logitech 23This is a fairly inexpensive device for capturing images. Logitech
24does not currently provide information for developers, but many people 24does not currently provide information for developers, but many people
diff --git a/Documentation/video4linux/README.davinci-vpbe b/Documentation/video4linux/README.davinci-vpbe
index 7a460b0685bb..dc9a297f49c3 100644
--- a/Documentation/video4linux/README.davinci-vpbe
+++ b/Documentation/video4linux/README.davinci-vpbe
@@ -5,22 +5,22 @@
5 File partitioning 5 File partitioning
6 ----------------- 6 -----------------
7 V4L2 display device driver 7 V4L2 display device driver
8 drivers/media/video/davinci/vpbe_display.c 8 drivers/media/platform/davinci/vpbe_display.c
9 drivers/media/video/davinci/vpbe_display.h 9 drivers/media/platform/davinci/vpbe_display.h
10 10
11 VPBE display controller 11 VPBE display controller
12 drivers/media/video/davinci/vpbe.c 12 drivers/media/platform/davinci/vpbe.c
13 drivers/media/video/davinci/vpbe.h 13 drivers/media/platform/davinci/vpbe.h
14 14
15 VPBE venc sub device driver 15 VPBE venc sub device driver
16 drivers/media/video/davinci/vpbe_venc.c 16 drivers/media/platform/davinci/vpbe_venc.c
17 drivers/media/video/davinci/vpbe_venc.h 17 drivers/media/platform/davinci/vpbe_venc.h
18 drivers/media/video/davinci/vpbe_venc_regs.h 18 drivers/media/platform/davinci/vpbe_venc_regs.h
19 19
20 VPBE osd driver 20 VPBE osd driver
21 drivers/media/video/davinci/vpbe_osd.c 21 drivers/media/platform/davinci/vpbe_osd.c
22 drivers/media/video/davinci/vpbe_osd.h 22 drivers/media/platform/davinci/vpbe_osd.h
23 drivers/media/video/davinci/vpbe_osd_regs.h 23 drivers/media/platform/davinci/vpbe_osd_regs.h
24 24
25 Functional partitioning 25 Functional partitioning
26 ----------------------- 26 -----------------------
diff --git a/Documentation/video4linux/fimc.txt b/Documentation/video4linux/fimc.txt
index eb049708f3e4..fd02d9a4930a 100644
--- a/Documentation/video4linux/fimc.txt
+++ b/Documentation/video4linux/fimc.txt
@@ -10,7 +10,7 @@ data from LCD controller (FIMD) through the SoC internal writeback data
10path. There are multiple FIMC instances in the SoCs (up to 4), having 10path. There are multiple FIMC instances in the SoCs (up to 4), having
11slightly different capabilities, like pixel alignment constraints, rotator 11slightly different capabilities, like pixel alignment constraints, rotator
12availability, LCD writeback support, etc. The driver is located at 12availability, LCD writeback support, etc. The driver is located at
13drivers/media/video/s5p-fimc directory. 13drivers/media/platform/s5p-fimc directory.
14 14
151. Supported SoCs 151. Supported SoCs
16================= 16=================
@@ -36,21 +36,21 @@ Not currently supported:
36===================== 36=====================
37 37
38- media device driver 38- media device driver
39 drivers/media/video/s5p-fimc/fimc-mdevice.[ch] 39 drivers/media/platform/s5p-fimc/fimc-mdevice.[ch]
40 40
41 - camera capture video device driver 41 - camera capture video device driver
42 drivers/media/video/s5p-fimc/fimc-capture.c 42 drivers/media/platform/s5p-fimc/fimc-capture.c
43 43
44 - MIPI-CSI2 receiver subdev 44 - MIPI-CSI2 receiver subdev
45 drivers/media/video/s5p-fimc/mipi-csis.[ch] 45 drivers/media/platform/s5p-fimc/mipi-csis.[ch]
46 46
47 - video post-processor (mem-to-mem) 47 - video post-processor (mem-to-mem)
48 drivers/media/video/s5p-fimc/fimc-core.c 48 drivers/media/platform/s5p-fimc/fimc-core.c
49 49
50 - common files 50 - common files
51 drivers/media/video/s5p-fimc/fimc-core.h 51 drivers/media/platform/s5p-fimc/fimc-core.h
52 drivers/media/video/s5p-fimc/fimc-reg.h 52 drivers/media/platform/s5p-fimc/fimc-reg.h
53 drivers/media/video/s5p-fimc/regs-fimc.h 53 drivers/media/platform/s5p-fimc/regs-fimc.h
54 54
554. User space interfaces 554. User space interfaces
56======================== 56========================
diff --git a/Documentation/video4linux/omap3isp.txt b/Documentation/video4linux/omap3isp.txt
index 5dd1439b61fd..b9a9f83b1587 100644
--- a/Documentation/video4linux/omap3isp.txt
+++ b/Documentation/video4linux/omap3isp.txt
@@ -12,7 +12,7 @@ Introduction
12============ 12============
13 13
14This file documents the Texas Instruments OMAP 3 Image Signal Processor (ISP) 14This file documents the Texas Instruments OMAP 3 Image Signal Processor (ISP)
15driver located under drivers/media/video/omap3isp. The original driver was 15driver located under drivers/media/platform/omap3isp. The original driver was
16written by Texas Instruments but since that it has been rewritten (twice) at 16written by Texas Instruments but since that it has been rewritten (twice) at
17Nokia. 17Nokia.
18 18
diff --git a/Documentation/video4linux/v4l2-framework.txt b/Documentation/video4linux/v4l2-framework.txt
index 89318be6c1d2..e7006cacc86b 100644
--- a/Documentation/video4linux/v4l2-framework.txt
+++ b/Documentation/video4linux/v4l2-framework.txt
@@ -1054,4 +1054,4 @@ The first event type in the class is reserved for future use, so the first
1054available event type is 'class base + 1'. 1054available event type is 'class base + 1'.
1055 1055
1056An example on how the V4L2 events may be used can be found in the OMAP 1056An example on how the V4L2 events may be used can be found in the OMAP
10573 ISP driver (drivers/media/video/omap3isp). 10573 ISP driver (drivers/media/platform/omap3isp).
diff --git a/Documentation/video4linux/videobuf b/Documentation/video4linux/videobuf
index 1d00d7f15b8f..3ffe9e960b6f 100644
--- a/Documentation/video4linux/videobuf
+++ b/Documentation/video4linux/videobuf
@@ -349,7 +349,7 @@ again.
349Developers who are interested in more information can go into the relevant 349Developers who are interested in more information can go into the relevant
350header files; there are a few low-level functions declared there which have 350header files; there are a few low-level functions declared there which have
351not been talked about here. Also worthwhile is the vivi driver 351not been talked about here. Also worthwhile is the vivi driver
352(drivers/media/video/vivi.c), which is maintained as an example of how V4L2 352(drivers/media/platform/vivi.c), which is maintained as an example of how V4L2
353drivers should be written. Vivi only uses the vmalloc() API, but it's good 353drivers should be written. Vivi only uses the vmalloc() API, but it's good
354enough to get started with. Note also that all of these calls are exported 354enough to get started with. Note also that all of these calls are exported
355GPL-only, so they will not be available to non-GPL kernel modules. 355GPL-only, so they will not be available to non-GPL kernel modules.