Explorar el Código

[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>
Lad, Prabhakar hace 13 años
padre
commit
83c735379b

+ 1 - 1
Documentation/video4linux/CQcam.txt

@@ -18,7 +18,7 @@ Table of Contents
 
 
 1.0 Introduction
 1.0 Introduction
 
 
-  The file ../../drivers/media/video/c-qcam.c is a device driver for
+  The file ../../drivers/media/parport/c-qcam.c is a device driver for
 the Logitech (nee Connectix) parallel port interface color CCD camera.
 the Logitech (nee Connectix) parallel port interface color CCD camera.
 This is a fairly inexpensive device for capturing images.  Logitech
 This is a fairly inexpensive device for capturing images.  Logitech
 does not currently provide information for developers, but many people
 does not currently provide information for developers, but many people

+ 10 - 10
Documentation/video4linux/README.davinci-vpbe

@@ -5,22 +5,22 @@
  File partitioning
  File partitioning
  -----------------
  -----------------
  V4L2 display device driver
  V4L2 display device driver
-         drivers/media/video/davinci/vpbe_display.c
-         drivers/media/video/davinci/vpbe_display.h
+         drivers/media/platform/davinci/vpbe_display.c
+         drivers/media/platform/davinci/vpbe_display.h
 
 
  VPBE display controller
  VPBE display controller
-         drivers/media/video/davinci/vpbe.c
-         drivers/media/video/davinci/vpbe.h
+         drivers/media/platform/davinci/vpbe.c
+         drivers/media/platform/davinci/vpbe.h
 
 
  VPBE venc sub device driver
  VPBE venc sub device driver
-         drivers/media/video/davinci/vpbe_venc.c
-         drivers/media/video/davinci/vpbe_venc.h
-         drivers/media/video/davinci/vpbe_venc_regs.h
+         drivers/media/platform/davinci/vpbe_venc.c
+         drivers/media/platform/davinci/vpbe_venc.h
+         drivers/media/platform/davinci/vpbe_venc_regs.h
 
 
  VPBE osd driver
  VPBE osd driver
-         drivers/media/video/davinci/vpbe_osd.c
-         drivers/media/video/davinci/vpbe_osd.h
-         drivers/media/video/davinci/vpbe_osd_regs.h
+         drivers/media/platform/davinci/vpbe_osd.c
+         drivers/media/platform/davinci/vpbe_osd.h
+         drivers/media/platform/davinci/vpbe_osd_regs.h
 
 
  Functional partitioning
  Functional partitioning
  -----------------------
  -----------------------

+ 8 - 8
Documentation/video4linux/fimc.txt

@@ -10,7 +10,7 @@ data from LCD controller (FIMD) through the SoC internal writeback data
 path.  There are multiple FIMC instances in the SoCs (up to 4), having
 path.  There are multiple FIMC instances in the SoCs (up to 4), having
 slightly different capabilities, like pixel alignment constraints, rotator
 slightly different capabilities, like pixel alignment constraints, rotator
 availability, LCD writeback support, etc. The driver is located at
 availability, LCD writeback support, etc. The driver is located at
-drivers/media/video/s5p-fimc directory.
+drivers/media/platform/s5p-fimc directory.
 
 
 1. Supported SoCs
 1. Supported SoCs
 =================
 =================
@@ -36,21 +36,21 @@ Not currently supported:
 =====================
 =====================
 
 
 - media device driver
 - media device driver
-  drivers/media/video/s5p-fimc/fimc-mdevice.[ch]
+  drivers/media/platform/s5p-fimc/fimc-mdevice.[ch]
 
 
  - camera capture video device driver
  - camera capture video device driver
-  drivers/media/video/s5p-fimc/fimc-capture.c
+  drivers/media/platform/s5p-fimc/fimc-capture.c
 
 
  - MIPI-CSI2 receiver subdev
  - MIPI-CSI2 receiver subdev
-  drivers/media/video/s5p-fimc/mipi-csis.[ch]
+  drivers/media/platform/s5p-fimc/mipi-csis.[ch]
 
 
  - video post-processor (mem-to-mem)
  - video post-processor (mem-to-mem)
-  drivers/media/video/s5p-fimc/fimc-core.c
+  drivers/media/platform/s5p-fimc/fimc-core.c
 
 
  - common files
  - common files
-  drivers/media/video/s5p-fimc/fimc-core.h
-  drivers/media/video/s5p-fimc/fimc-reg.h
-  drivers/media/video/s5p-fimc/regs-fimc.h
+  drivers/media/platform/s5p-fimc/fimc-core.h
+  drivers/media/platform/s5p-fimc/fimc-reg.h
+  drivers/media/platform/s5p-fimc/regs-fimc.h
 
 
 4. User space interfaces
 4. User space interfaces
 ========================
 ========================

+ 1 - 1
Documentation/video4linux/omap3isp.txt

@@ -12,7 +12,7 @@ Introduction
 ============
 ============
 
 
 This file documents the Texas Instruments OMAP 3 Image Signal Processor (ISP)
 This file documents the Texas Instruments OMAP 3 Image Signal Processor (ISP)
-driver located under drivers/media/video/omap3isp. The original driver was
+driver located under drivers/media/platform/omap3isp. The original driver was
 written by Texas Instruments but since that it has been rewritten (twice) at
 written by Texas Instruments but since that it has been rewritten (twice) at
 Nokia.
 Nokia.
 
 

+ 1 - 1
Documentation/video4linux/v4l2-framework.txt

@@ -1054,4 +1054,4 @@ The first event type in the class is reserved for future use, so the first
 available event type is 'class base + 1'.
 available event type is 'class base + 1'.
 
 
 An example on how the V4L2 events may be used can be found in the OMAP
 An example on how the V4L2 events may be used can be found in the OMAP
-3 ISP driver (drivers/media/video/omap3isp).
+3 ISP driver (drivers/media/platform/omap3isp).

+ 1 - 1
Documentation/video4linux/videobuf

@@ -349,7 +349,7 @@ again.
 Developers who are interested in more information can go into the relevant
 Developers who are interested in more information can go into the relevant
 header files; there are a few low-level functions declared there which have
 header files; there are a few low-level functions declared there which have
 not been talked about here.  Also worthwhile is the vivi driver
 not been talked about here.  Also worthwhile is the vivi driver
-(drivers/media/video/vivi.c), which is maintained as an example of how V4L2
+(drivers/media/platform/vivi.c), which is maintained as an example of how V4L2
 drivers should be written.  Vivi only uses the vmalloc() API, but it's good
 drivers should be written.  Vivi only uses the vmalloc() API, but it's good
 enough to get started with.  Note also that all of these calls are exported
 enough to get started with.  Note also that all of these calls are exported
 GPL-only, so they will not be available to non-GPL kernel modules.
 GPL-only, so they will not be available to non-GPL kernel modules.