Searched full:type (Results 1 – 25 of 1426) sorted by relevance
12345678910>>...58
| /Documentation/media/ |
| D | dmx.h.rst.exceptions | 10 replace enum dmx_ts_pes :c:type:`dmx_pes_type`
11 replace symbol DMX_PES_AUDIO0 :c:type:`dmx_pes_type`
12 replace symbol DMX_PES_VIDEO0 :c:type:`dmx_pes_type`
13 replace symbol DMX_PES_TELETEXT0 :c:type:`dmx_pes_type`
14 replace symbol DMX_PES_SUBTITLE0 :c:type:`dmx_pes_type`
15 replace symbol DMX_PES_PCR0 :c:type:`dmx_pes_type`
16 replace symbol DMX_PES_AUDIO1 :c:type:`dmx_pes_type`
17 replace symbol DMX_PES_VIDEO1 :c:type:`dmx_pes_type`
18 replace symbol DMX_PES_TELETEXT1 :c:type:`dmx_pes_type`
19 replace symbol DMX_PES_SUBTITLE1 :c:type:`dmx_pes_type`
[all …]
|
| D | conf_nitpick.py | 49 ("c:type", "atomic_t"),
50 ("c:type", "bool"),
51 ("c:type", "boolean"),
52 ("c:type", "buf_queue"),
53 ("c:type", "device"),
54 ("c:type", "device_driver"),
55 ("c:type", "device_node"),
56 ("c:type", "enum"),
57 ("c:type", "fd"),
58 ("c:type", "fd_set"),
[all …]
|
| D | videodev2.h.rst.exceptions | 20 replace symbol V4L2_FIELD_ALTERNATE :c:type:`v4l2_field`
21 replace symbol V4L2_FIELD_ANY :c:type:`v4l2_field`
22 replace symbol V4L2_FIELD_BOTTOM :c:type:`v4l2_field`
23 replace symbol V4L2_FIELD_INTERLACED :c:type:`v4l2_field`
24 replace symbol V4L2_FIELD_INTERLACED_BT :c:type:`v4l2_field`
25 replace symbol V4L2_FIELD_INTERLACED_TB :c:type:`v4l2_field`
26 replace symbol V4L2_FIELD_NONE :c:type:`v4l2_field`
27 replace symbol V4L2_FIELD_SEQ_BT :c:type:`v4l2_field`
28 replace symbol V4L2_FIELD_SEQ_TB :c:type:`v4l2_field`
29 replace symbol V4L2_FIELD_TOP :c:type:`v4l2_field`
[all …]
|
| D | ca.h.rst.exceptions | 7 replace define CA_CI :c:type:`ca_slot_info`
8 replace define CA_CI_LINK :c:type:`ca_slot_info`
9 replace define CA_CI_PHYS :c:type:`ca_slot_info`
10 replace define CA_DESCR :c:type:`ca_slot_info`
11 replace define CA_SC :c:type:`ca_slot_info`
12 replace define CA_CI_MODULE_PRESENT :c:type:`ca_slot_info`
13 replace define CA_CI_MODULE_READY :c:type:`ca_slot_info`
16 replace define CA_ECD :c:type:`ca_descr_info`
17 replace define CA_NDS :c:type:`ca_descr_info`
18 replace define CA_DSS :c:type:`ca_descr_info`
[all …]
|
| D | video.h.rst.exceptions | 33 replace typedef video_format_t :c:type:`video_format`
34 replace typedef video_system_t :c:type:`video_system`
35 replace typedef video_displayformat_t :c:type:`video_displayformat`
36 replace typedef video_size_t :c:type:`video_size`
37 replace typedef video_stream_source_t :c:type:`video_stream_source`
38 replace typedef video_play_state_t :c:type:`video_play_state`
39 replace typedef video_navi_pack_t :c:type:`video_navi_pack`
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-vfio-mdev | 7 <device>. Supported type attributes are defined by the
9 Each supported type is a directory whose name is created
13 What: /sys/.../<device>/mdev_supported_types/<type-id>/
17 This directory gives details of supported type, like name,
24 What: /sys/.../mdev_supported_types/<type-id>/create
29 type <type-id> for parent device <device>. This is a
35 What: /sys/.../mdev_supported_types/<type-id>/devices/
40 devices sysfs entries which are created of this <type-id>.
42 What: /sys/.../mdev_supported_types/<type-id>/available_instances
47 devices of type <type-id> that can be created. This is a
[all …]
|
| /Documentation/media/kapi/ |
| D | v4l2-event.rst | 7 The driver must use :c:type:`v4l2_fh` to be able to support V4L2 events.
10 ``type`` and is optionally associated with an object identified through the
12 identified by the ``(type, id)`` tuple.
14 The :c:type:`v4l2_fh` struct has a list of subscribed events on its
17 When the user subscribes to an event, a :c:type:`v4l2_subscribed_event`
18 struct is added to :c:type:`v4l2_fh`\ ``.subscribed``, one for every
21 Each :c:type:`v4l2_subscribed_event` struct ends with a
22 :c:type:`v4l2_kevent` ringbuffer, with the size given by the caller
26 So every ``(type, ID)`` event tuple will have its own
27 :c:type:`v4l2_kevent` ringbuffer. This guarantees that if a driver is
[all …]
|
| D | v4l2-fh.rst | 6 struct :c:type:`v4l2_fh` provides a way to easily keep file handle specific
10 New drivers must use struct :c:type:`v4l2_fh`
14 The users of :c:type:`v4l2_fh` (in the V4L2 framework, not the driver) know
15 whether a driver uses :c:type:`v4l2_fh` as its ``file->private_data`` pointer
16 by testing the ``V4L2_FL_USES_V4L2_FH`` bit in :c:type:`video_device`->flags.
19 struct :c:type:`v4l2_fh` is allocated as a part of the driver's own file handle
23 In many cases the struct :c:type:`v4l2_fh` will be embedded in a larger
76 Below is a short description of the :c:type:`v4l2_fh` functions used:
79 (:c:type:`fh <v4l2_fh>`, :c:type:`vdev <video_device>`)
83 :c:type:`v4l2_file_operations`->open() handler.
[all …]
|
| D | v4l2-dev.rst | 7 :c:type:`video_device` struct (``v4l2-dev.h``). This struct can either be
40 You should also set these fields of :c:type:`video_device`:
42 - :c:type:`video_device`->v4l2_dev: must be set to the :c:type:`v4l2_device`
45 - :c:type:`video_device`->name: set to something descriptive and unique.
47 - :c:type:`video_device`->vfl_dir: set this to ``VFL_DIR_RX`` for capture
51 - :c:type:`video_device`->fops: set to the :c:type:`v4l2_file_operations`
54 - :c:type:`video_device`->ioctl_ops: if you use the :c:type:`v4l2_ioctl_ops`
57 :c:type:`v4l2_ioctl_ops` struct. The :c:type:`video_device`->vfl_type and
58 :c:type:`video_device`->vfl_dir fields are used to disable ops that do not
59 match the type/dir combination. E.g. VBI ops are disabled for non-VBI nodes,
[all …]
|
| D | v4l2-subdev.rst | 13 :c:type:`v4l2_subdev` struct (v4l2-subdev.h) was created.
15 Each sub-device driver must have a :c:type:`v4l2_subdev` struct. This struct
20 data of :c:type:`v4l2_subdev` using :c:func:`v4l2_set_subdevdata`. That makes
21 it easy to go from a :c:type:`v4l2_subdev` to the actual low-level bus-specific
24 You also need a way to go from the low-level struct to :c:type:`v4l2_subdev`.
26 a :c:type:`v4l2_subdev` pointer, for other buses you may have to use other
30 bridge-specific per-subdev private data. The :c:type:`v4l2_subdev` structure
35 obtain the :c:type:`v4l2_subdev` pointer. For i2c devices this is easy: you call
40 Each :c:type:`v4l2_subdev` contains function pointers that sub-device drivers
90 A sub-device driver initializes the :c:type:`v4l2_subdev` struct using:
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,wcd9335.txt | 13 Value type: <stringlist>
23 Value type: <u32 u32>
28 Value type: <prop-encoded-array>
33 Value type: <String array>
39 Value type: <String Array>
44 Value type: <phandle>
49 Value type: <prop-encoded-array>
55 Value type: <string>
60 Value type: <phandle>
65 Value type: <phandle>
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-g-selection.rst | 40 Pointer to struct :c:type:`v4l2_selection`.
48 :c:type:`v4l2_selection` ``type`` field to the
49 respective buffer type. The next step is setting the
50 value of struct :c:type:`v4l2_selection` ``target``
54 :c:type:`v4l2_selection` are ignored and they must be
56 EINVAL error code if incorrect buffer type or target was used. If
59 struct :c:type:`v4l2_rect` ``r`` rectangle is filled with
66 :c:type:`v4l2_selection` ``type`` field to the
67 respective buffer type. The next step is setting the
68 value of struct :c:type:`v4l2_selection` ``target`` to
[all …]
|
| D | vidioc-g-frequency.rst | 39 Pointer to struct :c:type:`v4l2_frequency`.
47 :c:type:`v4l2_frequency` to the respective tuner or
54 initialize the ``tuner``, ``type`` and ``frequency`` fields, and the
55 ``reserved`` array of a struct :c:type:`v4l2_frequency`
64 .. c:type:: v4l2_frequency
74 the struct :c:type:`v4l2_input` ``tuner`` field and
75 the struct :c:type:`v4l2_tuner` ``index`` field, or
76 the struct :c:type:`v4l2_output` ``modulator`` field
77 and the struct :c:type:`v4l2_modulator` ``index``
80 - ``type``
[all …]
|
| D | vidioc-g-fmt.rst | 41 Pointer to struct :c:type:`v4l2_format`.
50 To query the current parameters applications set the ``type`` field of a
51 struct :c:type:`v4l2_format` to the respective buffer (stream)
52 type. For example video capture devices use
58 :c:type:`v4l2_pix_format` ``pix`` or the struct
59 :c:type:`v4l2_pix_format_mplane` ``pix_mp``
60 member. When the requested buffer type is not supported drivers return
64 ``type`` field and all fields of the respective ``fmt`` union member.
69 a pointer to a struct :c:type:`v4l2_format` structure the driver
71 should not return an error code unless the ``type`` field is invalid,
[all …]
|
| D | vidioc-s-hw-freq-seek.rst | 36 Pointer to struct :c:type:`v4l2_hw_freq_seek`.
43 applications initialize the ``tuner``, ``type``, ``seek_upward``,
46 :c:type:`v4l2_hw_freq_seek` and call the
51 :c:type:`v4l2_tuner` ``capability`` field has the
72 .. c:type:: v4l2_hw_freq_seek
82 :c:type:`v4l2_input` ``tuner`` field and the struct
83 :c:type:`v4l2_tuner` ``index`` field.
85 - ``type``
86 - The tuner type. This is the same value as in the struct
87 :c:type:`v4l2_tuner` ``type`` field. See
[all …]
|
| D | vidioc-g-crop.rst | 39 Pointer to struct :c:type:`v4l2_crop`.
46 ``type`` field of a struct :c:type:`v4l2_crop` structure to the
47 respective buffer (stream) type and call the :ref:`VIDIOC_G_CROP <VIDIOC_G_CROP>` ioctl
51 To change the cropping rectangle applications initialize the ``type``
52 and struct :c:type:`v4l2_rect` substructure named ``c`` of a
80 .. c:type:: v4l2_crop
90 - ``type``
91 - Type of the data stream, set by the application. Only these types
94 ``V4L2_BUF_TYPE_VIDEO_OVERLAY``. See :c:type:`v4l2_buf_type` and the note below.
95 * - struct :c:type:`v4l2_rect`
[all …]
|
| /Documentation/bpf/ |
| D | btf.rst | 2 BPF Type Format (BTF)
8 BTF (BPF Type Format) is the metadata format which encodes the debug info
26 The type and string sections are part of the BTF kernel API, describing the
32 2. BTF Type and String Encoding
47 __u32 type_off; /* offset of type section */
48 __u32 type_len; /* length of type section */
65 2.2 Type Encoding
68 The type id ``0`` is reserved for ``void`` type. The type section is parsed
69 sequentially and type id is assigned to each recognized type starting from id
88 Note that the type section encodes debug info, not just pure types.
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic.txt | 9 additional cells in the interrupt specifier defining interrupt type
16 Value type: <string>
24 Value type: <prop-encoded-array>
31 Value type: <empty>
37 Value type: <u32>
39 specifiers do not contain the interrupt-type or type-specific
44 Value type: <u32>
49 Value type: <empty>
62 Value type: <empty>
69 Value type: <empty>
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | qcom,pcie.txt | 5 Value type: <stringlist>
17 Value type: <prop-encoded-array>
22 Value type: <stringlist>
31 Value type: <string>
36 Value type: <u32>
41 Value type: <u32>
46 Value type: <prop-encoded-array>
51 Value type: <prop-encoded-array>
56 Value type: <stringlist>
61 Value type: <u32>
[all …]
|
| /Documentation/devicetree/bindings/soc/rockchip/ |
| D | power_domain.txt | 26 "include/dt-bindings/power/px30-power.h" - for PX30 type power domain.
27 "include/dt-bindings/power/rk3036-power.h" - for RK3036 type power domain.
28 "include/dt-bindings/power/rk3066-power.h" - for RK3066 type power domain.
29 "include/dt-bindings/power/rk3128-power.h" - for RK3128 type power domain.
30 "include/dt-bindings/power/rk3188-power.h" - for RK3188 type power domain.
31 "include/dt-bindings/power/rk3228-power.h" - for RK3228 type power domain.
32 "include/dt-bindings/power/rk3288-power.h" - for RK3288 type power domain.
33 "include/dt-bindings/power/rk3328-power.h" - for RK3328 type power domain.
34 "include/dt-bindings/power/rk3366-power.h" - for RK3366 type power domain.
35 "include/dt-bindings/power/rk3368-power.h" - for RK3368 type power domain.
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | qcom,venus.txt | 5 Value type: <stringlist>
12 Value type: <prop-encoded-array>
16 Value type: <prop-encoded-array>
20 Value type: <prop-encoded-array>
25 Value type: <stringlist>
32 Value type: <stringlist>
40 Value type: <prop-encoded-array>
46 Value type: <prop-encoded-array>
50 Value type: <phandle>
63 Value type: <stringlist>
[all …]
|
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec2.txt | 34 are available. It's a single 32-bit cell. Descriptor type information
38 bit 0 = set if SEC supports the aesu_ctr_nonsnoop desc. type
39 bit 1 = set if SEC supports the ipsec_esp descriptor type
40 bit 2 = set if SEC supports the common_nonsnoop desc. type
41 bit 3 = set if SEC supports the 802.11i AES ccmp desc. type
42 bit 4 = set if SEC supports the hmac_snoop_no_afeu desc. type
43 bit 5 = set if SEC supports the srtp descriptor type
44 bit 6 = set if SEC supports the non_hmac_snoop_no_afeu desc.type
45 bit 7 = set if SEC supports the pkeu_assemble descriptor type
46 bit 8 = set if SEC supports the aesu_key_expand_output desc.type
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-dump | 14 0xXX-0xYYYY: A directory for dump of type 0xXX and
18 among all dumps. For determining the type
19 and ID of the dump, use the id and type files.
21 type or dump id.
26 type: An ASCII representation of the type of
28 in hex and a description of the dump type
30 Type '0xffffffff unknown' is used when
31 we could not get the type from firmware.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | qcom-pm8xxx.txt | 10 Value type: <string>
18 Value type: <u32>
23 Value type: <u32>
28 Value type: <prop-encoded-array>
36 Value type : <u32>
39 number. The 2nd cell is the trigger type and level flags
49 Value type: <empty>
61 Value type: <string>
70 Value type: <prop-encoded-array>
75 Value type: <prop-encoded-array>
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | qcom,usb-8x16-phy.txt | 5 Value type: <string>
10 Value type: <prop-encoded-array>
15 Value type: <prop-encoded-array>
22 Value type: <string>
27 Value type: <phandle>
32 Value type: <phandle>
37 Value type: <phandle>
42 Value type: <prop-encoded-array>
47 Value type: <string>
52 Value type: <prop-encoded-array>
|
12345678910>>...58