| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-enum-links.rst | 13 MEDIA_IOC_ENUM_LINKS - Enumerate all pads and links for a given entity
34 To enumerate pads and/or links for a given entity, applications set the
39 the ``pads`` and ``links`` fields. They then call the
42 If the ``pads`` field is not NULL, the driver fills the ``pads`` array
43 with information about the entity's pads. The array must have enough
44 room to store all the entity's pads. The number of pads can be retrieved
52 Only forward links that originate at one of the entity's source pads are
69 - \*\ ``pads``
70 - Pointer to a pads array allocated by the application. Ignored if
|
| D | media-controller-model.rst | 27 inputs. Pads should not be confused with physical pins at chip
31 pads, either on the same entity or on different entities. Data flows
|
| D | media-ioc-g-topology.rst | 38 ``topology_version`` and the total number of entities, interfaces, pads
96 - Total number of pads in the graph
104 - A pointer to a memory area where the pads array will be stored,
106 won't store the pads. It will just update ``num_pads``
|
| D | media-ioc-enum-entities.rst | 96 - ``pads``
98 - Number of pads
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-subdev.rst | 18 and discover the hardware topology using the media entities, pads and
30 - negotiate image formats on individual pads
32 - inspect and modify internal data routing between pads of the same entity
133 whole pipeline and making sure that connected pads have compatible
147 Acceptable formats on pads can (and usually do) depend on a number of
148 external parameters, such as formats on other pads, active links, or
149 even controls. Finding a combination of formats on all pads in a video
182 (as long as external parameters, such as formats on other pads or links'
186 or active format is set on a pad, corresponding formats on other pads of
191 - Formats should be propagated from sink pads to source pads. Modifying
[all …]
|
| D | ext-ctrls-dv.rst | 19 Note that these devices can have multiple input or output pads which are
21 receive or transmit video from/to only one of those pads, the other pads
28 These pads appear in several of the controls in this section as
30 1, etc. The maximum value of the control is the set of valid pads.
|
| D | vidioc-subdev-g-routing.rst | 13 …ING - VIDIOC_SUBDEV_S_ROUTING - Get or set routing between streams of media pads in a media entity.
54 Only subdevices which have both sink and source pads can support routing.
159 pads of different types (ie. the sink_pad identifiers refers to a source
|
| D | vidioc-subdev-enum-frame-interval.rst | 54 other pads of the sub-device, as well as on the current active links.
60 multiple pads of the same sub-device is not defined.
|
| /Documentation/driver-api/media/ |
| D | mc-core.rst | 19 through pads.
29 flows from the entity's output to one or more entity inputs. Pads should
32 A link is a point-to-point oriented connection between two pads, either
65 Drivers initialize entity pads by calling
87 Pads chapter
89 Pads are represented by a struct media_pad instance,
90 defined in ``include/media/media-entity.h``. Each entity stores its pads in
91 a pads array managed by the entity driver. Drivers usually embed the array in
94 Pads are identified by their entity and their 0-based index in the pads
101 Pads have flags that describe the pad capabilities and state.
[all …]
|
| /Documentation/devicetree/bindings/display/ |
| D | arm,pl11x.yaml | 94 arm,pl11x,tft-r0g0b0-pads:
103 CLD[23:0] pads are wired up.
111 arm,pl11x,tft-r0g0b0-pads = <4 15 20>;
113 arm,pl11x,tft-r0g0b0-pads = <1 7 13>;
115 arm,pl11x,tft-r0g0b0-pads = <3 11 19>;
117 arm,pl11x,tft-r0g0b0-pads = <3 10 19>;
119 arm,pl11x,tft-r0g0b0-pads = <0 8 16>;
121 arm,pl11x,tft-r0g0b0-pads = <16 8 0>;
|
| /Documentation/devicetree/bindings/phy/ |
| D | nvidia,tegra20-usb-phy.yaml | 50 - description: UTMI pads control registers clock
56 - description: UTMI pads control registers clock
72 - const: utmi-pads
78 - const: utmi-pads
90 - description: UTMI pads reset
98 - const: utmi-pads
271 - const: utmi-pads
288 - const: utmi-pads
340 clock-names = "reg", "pll_u", "utmi-pads";
342 reset-names = "usb", "utmi-pads";
[all …]
|
| D | nvidia,tegra186-xusb-padctl.yaml | 15 signals) which connect directly to pins/pads on the SoC package. Each lane
30 Pads will be represented as children of the top-level XUSB pad controller
83 pads:
84 description: A required child node named "pads" contains a list of
85 subnodes, one for each of the pads exposed by the XUSB pad controller.
447 pads {
|
| /Documentation/devicetree/bindings/ata/ |
| D | cortina,gemini-sata-bridge.yaml | 58 ata0 slave interface brought out on IDE pads
61 ata1 slave interface brought out on IDE pads
64 ata0 master and slave interfaces brought out on IDE pads
67 ata1 master and slave interfaces brought out on IDE pads
|
| /Documentation/devicetree/bindings/pci/ |
| D | nvidia,tegra20-pcie.txt | 17 "pads": PADS registers
171 reg = <0x80003000 0x00000800 /* PADS registers */
174 reg-names = "pads", "afi", "cs";
272 reg = <0x00003000 0x00000800 /* PADS registers */
275 reg-names = "pads", "afi", "cs";
377 reg = <0x0 0x01003000 0x0 0x00000800 /* PADS registers */
380 reg-names = "pads", "afi", "cs";
452 phys = <&{/padctl@7009f000/pads/pcie/lanes/pcie-4}>;
459 phys = <&{/padctl@7009f000/pads/pcie/lanes/pcie-2}>;
473 reg = <0x0 0x01003000 0x0 0x00000800 /* PADS registers */
[all …]
|
| /Documentation/admin-guide/media/ |
| D | imx7.rst | 47 This is the video multiplexer. It has two sink pads to select from either camera
88 # Configure pads for pipeline
113 - entity 1: csi (2 pads, 2 links)
129 - entity 10: csi-mux (3 pads, 2 links)
141 - entity 14: imx7-mipi-csis.0 (2 pads, 2 links)
171 # Configure pads for pipeline
195 - entity 1: csi (2 pads, 2 links)
|
| D | imx.rst | 142 four source pads, corresponding to the four MIPI CSI-2 demuxed virtual
143 channel outputs. Multiple source pads can be enabled to independently
165 These are the video multiplexers. They have two or more sink pads to
172 the four MIPI CSI-2 virtual channels (a total of five sink pads). The
173 other mux sits in front of IPU1-CSI1, and again has five sink pads to
179 channel 0 (two sink pads). The other mux sits in front of IPU2-CSI1 to
181 sink pads).
190 This entity has two source pads. The first source pad can link directly
257 sink and source pads. The ipuX_csiY entity then applies the best
280 has two sink pads and a single source pad.
[all …]
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra124-dpaux.yaml | 84 DPAUX pads. Furthermore, given that the pad functions are only
85 applicable to a single set of pads, the child nodes only need
87 rather than the individual pads.
|
| D | nvidia,tegra114-mipi.yaml | 39 Should be 1. The single cell specifies a bitmask of the pads that
73 nvidia,mipi-calibrate = <&mipi 0x060>; /* DSIA & DSIB pads */
|
| /Documentation/input/devices/ |
| D | xpad.rst | 29 pads" (module option dpad_to_buttons)
36 dpad_to_buttons has no effect for known pads. A erroneous commit message
63 Xbox Dance Pads
68 For dance style pads (like the redoctane pad) several changes
73 Known dance pads automatically map the d-pad to buttons and will work
231 - added stuff for dance pads, new d-pad->axes mappings
|
| D | joystick-parport.rst | 59 for your pads, use either keyboard or joystick port, and make a pass-through
71 Unfortunately, there are pads that need a lot more of power, and parallel
92 NES and SNES pads have two input bits, Clock and Latch, which drive the
278 want to use them on one parallel port together with NES/SNES/PSX pads. This is
305 for the NES / SNES pads in section 2.1 of this file - that is, one data pin
387 The Sega Genesis (in Europe sold as Sega MegaDrive) pads are an extension
388 to the Sega Master System pads. They use more buttons (3+1, 5+1, 6+1). Use
417 Genesis 6 pads use, it needs one more select pin. Anyway, it is still
487 described above, allows to connect a different group of joysticks and pads.
528 work but you can try lowering it for better performance. If your pads don't
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | amlogic,meson-gpio-intc.yaml | 14 pads and generate an interrupt on edge or level. The controller is essentially
15 a 256 pads to 8 or 12 GIC interrupt multiplexer, with a filter block to select
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra186-pmc.yaml | 103 The following pads are present on Tegra186:
111 The following pads are present on Tegra194:
147 The power state can be configured on all of the above pads
148 except for ao-hv. Following pads have software configurable
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra124-xusb-padctl.txt | 11 assigned to one out of a set of different pads. Some of these pads have an
40 Each subnode describes groups of lanes along with parameters and pads that
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | ti,nspire.yaml | 33 remote-endpoint = <&pads>;
|
| /Documentation/devicetree/bindings/soc/tegra/ |
| D | nvidia,tegra20-pmc.yaml | 270 The following pads are present on Tegra124 and Tegra132:
277 The following pads are present on Tegra210:
306 Power state can be configured on all Tegra124 and Tegra132 pads.
307 None of the Tegra124 or Tegra132 pads support signaling voltage
308 switching. All of the listed Tegra210 pads except pex-cntrl support
310 on the following Tegra210 pads:
|