Home
last modified time | relevance | path

Searched refs:v4l2 (Results 1 – 25 of 138) sorted by relevance

123456

/Linux-v5.4/Documentation/media/kapi/
Dv4l2-core.rst9 v4l2-intro
10 v4l2-dev
11 v4l2-device
12 v4l2-fh
13 v4l2-subdev
14 v4l2-event
15 v4l2-controls
16 v4l2-videobuf
17 v4l2-videobuf2
18 v4l2-clocks
[all …]
Dv4l2-common.rst6 .. kernel-doc:: include/media/v4l2-common.h
8 .. kernel-doc:: include/media/v4l2-ioctl.h
/Linux-v5.4/drivers/media/usb/em28xx/
Dem28xx-video.c138 struct em28xx_v4l2 *v4l2 = dev->v4l2; in norm_maxw() local
141 return v4l2->sensor_xres; in norm_maxw()
151 struct em28xx_v4l2 *v4l2 = dev->v4l2; in norm_maxh() local
154 return v4l2->sensor_yres; in norm_maxh()
159 return (v4l2->norm & V4L2_STD_625_50) ? 576 : 480; in norm_maxh()
187 struct v4l2_device *v4l2_dev = &dev->v4l2->v4l2_dev; in em28xx_wake_i2c()
216 struct em28xx_v4l2 *v4l2 = dev->v4l2; in em28xx_set_outfmt() local
218 fmt = v4l2->format->reg; in em28xx_set_outfmt()
234 ret = em28xx_write_reg(dev, EM28XX_R10_VINMODE, v4l2->vinmode); in em28xx_set_outfmt()
238 vinctrl = v4l2->vinctl; in em28xx_set_outfmt()
[all …]
Dem28xx-camera.c314 struct em28xx_v4l2 *v4l2 = dev->v4l2; in em28xx_init_camera() local
326 v4l2->sensor_xres = 640; in em28xx_init_camera()
327 v4l2->sensor_yres = 480; in em28xx_init_camera()
340 v4l2->sensor_xtal = 4300000; in em28xx_init_camera()
341 pdata.xtal = v4l2->sensor_xtal; in em28xx_init_camera()
343 v4l2_i2c_new_subdev_board(&v4l2->v4l2_dev, adap, in em28xx_init_camera()
346 v4l2->vinmode = EM28XX_VINMODE_RGB8_GRBG; in em28xx_init_camera()
347 v4l2->vinctl = 0x00; in em28xx_init_camera()
352 v4l2->sensor_xres = 1280; in em28xx_init_camera()
353 v4l2->sensor_yres = 1024; in em28xx_init_camera()
[all …]
Dem28xx-vbi.c36 struct em28xx_v4l2 *v4l2 = dev->v4l2; in vbi_queue_setup() local
37 unsigned long size = v4l2->vbi_width * v4l2->vbi_height * 2; in vbi_queue_setup()
57 struct em28xx_v4l2 *v4l2 = dev->v4l2; in vbi_buffer_prepare() local
60 size = v4l2->vbi_width * v4l2->vbi_height * 2; in vbi_buffer_prepare()
/Linux-v5.4/drivers/media/v4l2-core/
DMakefile8 videodev-objs := v4l2-dev.o v4l2-ioctl.o v4l2-device.o v4l2-fh.o \
9 v4l2-event.o v4l2-ctrls.o v4l2-subdev.o v4l2-clk.o \
10 v4l2-async.o v4l2-common.o
11 videodev-$(CONFIG_COMPAT) += v4l2-compat-ioctl32.o
12 videodev-$(CONFIG_TRACEPOINTS) += v4l2-trace.o
13 videodev-$(CONFIG_MEDIA_CONTROLLER) += v4l2-mc.o
14 videodev-$(CONFIG_SPI) += v4l2-spi.o
15 videodev-$(CONFIG_VIDEO_V4L2_I2C) += v4l2-i2c.o
17 obj-$(CONFIG_V4L2_FWNODE) += v4l2-fwnode.o
19 obj-$(CONFIG_VIDEO_V4L2) += v4l2-dv-timings.o
[all …]
/Linux-v5.4/drivers/gpu/drm/rcar-du/
Drcar_du_kms.c38 .v4l2 = V4L2_PIX_FMT_RGB565,
45 .v4l2 = V4L2_PIX_FMT_ARGB555,
52 .v4l2 = V4L2_PIX_FMT_XRGB555,
59 .v4l2 = V4L2_PIX_FMT_XBGR32,
66 .v4l2 = V4L2_PIX_FMT_ABGR32,
73 .v4l2 = V4L2_PIX_FMT_UYVY,
80 .v4l2 = V4L2_PIX_FMT_YUYV,
87 .v4l2 = V4L2_PIX_FMT_NV12M,
94 .v4l2 = V4L2_PIX_FMT_NV21M,
101 .v4l2 = V4L2_PIX_FMT_NV16M,
[all …]
/Linux-v5.4/Documentation/media/
Dvideodev2.h.rst.exceptions233 replace define V4L2_STD_PAL_B v4l2-std-id
234 replace define V4L2_STD_PAL_B1 v4l2-std-id
235 replace define V4L2_STD_PAL_G v4l2-std-id
236 replace define V4L2_STD_PAL_H v4l2-std-id
237 replace define V4L2_STD_PAL_I v4l2-std-id
238 replace define V4L2_STD_PAL_D v4l2-std-id
239 replace define V4L2_STD_PAL_D1 v4l2-std-id
240 replace define V4L2_STD_PAL_K v4l2-std-id
241 replace define V4L2_STD_PAL_M v4l2-std-id
242 replace define V4L2_STD_PAL_N v4l2-std-id
[all …]
/Linux-v5.4/drivers/media/common/v4l2-tpg/
DMakefile2 v4l2-tpg-objs := v4l2-tpg-core.o v4l2-tpg-colors.o
4 obj-$(CONFIG_VIDEO_V4L2_TPG) += v4l2-tpg.o
/Linux-v5.4/Documentation/media/uapi/v4l/
Dlibv4l-introduction.rst80 applications work with v4l2 devices. These functions work exactly like
82 the v4l1 api on top of v4l2 drivers, in case of v4l1 drivers it will
100 v4l2 driver, intercepting the calls to
125 :c:func:`open() <v4l2-open>`, :c:func:`close() <v4l2-close>`,
126 :c:func:`ioctl() <v4l2-ioctl>`, :c:func:`read() <v4l2-read>`,
127 :c:func:`mmap() <v4l2-mmap>` and :c:func:`munmap() <v4l2-munmap>`:
131 operates like the :c:func:`open() <v4l2-open>` function.
135 operates like the :c:func:`close() <v4l2-close>` function.
143 operates like the :c:func:`ioctl() <v4l2-ioctl>` function.
147 operates like the :c:func:`read() <v4l2-read>` function.
[all …]
Dselections-common.rst16 :ref:`V4L2 subdev selection APIs <v4l2-subdev-selections>` are very
29 v4l2-selection-targets
30 v4l2-selection-flags
Dvidioc-subdev-g-selection.rst73 :ref:`v4l2-selections-common`.
88 :ref:`v4l2_subdev_format_whence <v4l2-subdev-format-whence>`.
94 - Target selection rectangle. See :ref:`v4l2-selections-common`.
97 - Flags. See :ref:`v4l2-selection-flags`.
Dfunc-close.rst19 v4l2-close - Close a V4L2 device
31 :name: v4l2-close
Dpixfmt.rst29 pixfmt-v4l2
30 pixfmt-v4l2-mplane
Dfunc-munmap.rst19 v4l2-munmap - Unmap device memory
32 :name: v4l2-munmap
Dvidioc-g-selection.rst52 to table :ref:`v4l2-selections-common` or :ref:`selection-api` for
70 :ref:`v4l2-selections-common` or :ref:`selection-api` for additional
123 :ref:`v4l2-selections-common`.
155 :ref:`cropping and composing rectangles <v4l2-selections-common>`.
159 :ref:`selection flags <v4l2-selection-flags>`.
/Linux-v5.4/Documentation/media/v4l-drivers/
Dsi4713.rst34 The I2C device driver exports a v4l2-subdev interface to the kernel.
35 All properties can also be accessed by v4l2 extended controls interface, by
36 using the v4l2-subdev calls (g_ext_ctrls, s_ext_ctrls).
38 The platform device driver exports a v4l2 radio device interface to user land.
42 Applications can use v4l2 radio API to specify frequency of operation, mute state,
45 When the v4l2 mute property is set to 1 (true), the driver will turn the chip off.
50 The properties can be accessed using v4l2 extended controls.
51 Here is an output from v4l2-ctl util:
55 / # v4l2-ctl -d /dev/radio0 --all -L
184 Testing is usually done with v4l2-ctl utility for managing FM tuner cards.
[all …]
Dvimc.rst31 ``v4l2-ctl`` that can be used to configure the vimc configuration. This sequence
40 v4l2-ctl -z platform:vimc -d "RGB/YUV Capture" -v width=1920,height=1440
41 v4l2-ctl -z platform:vimc -d "Raw Capture 0" -v pixelformat=BA81
42 v4l2-ctl -z platform:vimc -d "Raw Capture 1" -v pixelformat=BA81
/Linux-v5.4/drivers/staging/vc04_services/bcm2835-camera/
DMakefile2 bcm2835-v4l2-$(CONFIG_VIDEO_BCM2835) := \
7 obj-$(CONFIG_VIDEO_BCM2835) += bcm2835-v4l2.o
/Linux-v5.4/drivers/media/pci/solo6x10/
DMakefile2 solo6x10-y := solo6x10-core.o solo6x10-i2c.o solo6x10-p2m.o solo6x10-v4l2.o \
4 solo6x10-v4l2-enc.o solo6x10-g723.o solo6x10-eeprom.o
/Linux-v5.4/Documentation/translations/zh_CN/video4linux/
Dv4l2-framework.txt96 每个设备实例都通过 v4l2_device (v4l2-device.h)结构体来表示。
216 统一接口，v4l2_subdev 结构体（v4l2-subdev.h）产生了。
379 控制。这个区别仅在配置设备时有关系，一旦子设备注册完成，对于 v4l2
435 由于这些驱动很常见，所以内特提供了特定的辅助函数(v4l2-common.h)让这些
528 在 /dev 目录下的实际设备节点根据 video_device 结构体(v4l2-dev.h)
668 通常你可以传入-1，让 v4l2 框架自己选择第一个空闲的编号。但是有时用户
677 而 v4l2 框架会试图选择第一个的空闲编号（等于或大于你提供的编号）。
774 v4l2 核心 API 提供了一个处理视频缓冲的标准方法(称为“videobuf”)。
780 请参阅 Documentation/media/kapi/v4l2-videobuf.rst，以获得更多关于 videobuf
923 关于 replace/merge 回调的一个不错的例子在 v4l2-event.c 中：用于
/Linux-v5.4/drivers/media/platform/atmel/
DKconfig11 as a v4l2 device.
21 as a v4l2 device.
/Linux-v5.4/drivers/input/rmi4/
Drmi_f54.c114 struct v4l2_device v4l2; member
685 strlcpy(f54->v4l2.name, F54_NAME, sizeof(f54->v4l2.name)); in rmi_f54_probe()
686 ret = v4l2_device_register(&fn->dev, &f54->v4l2); in rmi_f54_probe()
704 f54->vdev.v4l2_dev = &f54->v4l2; in rmi_f54_probe()
719 v4l2_device_unregister(&f54->v4l2); in rmi_f54_probe()
732 v4l2_device_unregister(&f54->v4l2); in rmi_f54_remove()
/Linux-v5.4/drivers/media/usb/au0828/
DKconfig23 bool "Auvitek AU0828 v4l2 analog video support"
32 Choose Y here to include support for v4l2 analog video
/Linux-v5.4/samples/v4l/
DMakefile2 obj-$(CONFIG_VIDEO_PCI_SKELETON) := v4l2-pci-skeleton.o

123456