| /Documentation/fb/ |
| D | viafb.modes | 16 # 12 chars 2 lines
18 # 2 chars 10 lines
20 # 6 chars 33 lines
22 # 80 chars 480 lines
24 # 20 chars 45 lines
41 # 8 chars 3 lines
43 # 2 chars 1 lines
45 # 15 chars 16 lines
47 # 80 chars 480 lines
49 # 25 chars 20 lines
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | gpio-matrix-keypad.txt | 4 The matrix keypad supports multiple row and column lines, a key can be
6 keypad can sense a key-press and key-release by means of GPIO lines and
11 - row-gpios: List of gpios used as row lines. The gpio specifier
13 which these row lines are connected.
14 - col-gpios: List of gpios used as column lines. The gpio specifier
16 which these column lines are connected.
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,q6afe.txt | 48 - qcom,sd-lines
51 Definition: Must be list of serial data lines used by this dai.
52 should be one or more of the 0-3 sd lines.
158 qcom,sd-lines = <0 2>;
163 qcom,sd-lines = <1>;
168 qcom,sd-lines = <0 3>;
173 qcom,sd-lines = <1>;
178 qcom,sd-lines = <1 3>;
183 qcom,sd-lines = <0>;
188 qcom,sd-lines = <0>;
[all …]
|
| D | qcom,lpass-cpu.yaml | 80 qcom,playback-sd-lines:
82 description: list of MI2S data lines for playback
84 qcom,capture-sd-lines:
86 description: list of MI2S data lines for capture
214 /* Optional to set different MI2S SD lines */
217 qcom,playback-sd-lines = <1>;
218 qcom,capture-sd-lines = <0>;
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 11 lines, giving you the LED sysfs interface
26 mouse cable and connect the wires to GPIO lines or solder a mouse connector
27 to the lines for a more permanent solution of this type.
49 (two wires, SDA and SCL lines) by hammering (bitbang) two GPIO lines. It will
54 of wires, at least SCK and optionally MISO, MOSI and chip select lines) using
79 to a set of simple GPIO lines: RDY, NCE, ALE, CLE, NWP. It interacts with the
84 bus, data and clock line, by bit banging two GPIO lines. It will appear as
95 nothing but GPIO lines, this driver provides that and also a clearly defined
100 read card detect and write protect GPIO lines, and in the TTY serial subsystem
101 to emulate MCTRL (modem control) signals CTS/RTS by using two GPIO lines. The
[all …]
|
| D | using-gpio.rst | 2 Using GPIO Lines in Linux
5 The Linux kernel exists to abstract and present hardware to users. GPIO lines
7 and preferred way to use GPIO lines is to let kernel hardware drivers deal
20 In Linux GPIO lines also have a userspace ABI.
23 factory lines, maker community projects, workshop specimen, production tools,
33 from userspace will likely be a good fit for using GPIO lines from userspace as
|
| /Documentation/admin-guide/media/ |
| D | rcar-fdp1.rst | 26 - The current field is scaled vertically by averaging adjacent lines to
27 recover missing lines. This method is also known as blending or Line
30 - The previous and next fields are averaged to recover lines missing from
34 field is used to fill missing lines from the current field. This method
38 used to fill missing lines from the current field. This method is also
|
| /Documentation/devicetree/bindings/powerpc/opal/ |
| D | oppanel-opal.txt | 6 - #lines : Number of lines on the operator panel e.g. <0x2>.
12 #lines = <0x2>;
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-mockup.rst | 7 chips for testing purposes. The lines exposed by these chips can be accessed
21 of lines exposed by the chip. If the base GPIO is -1, the gpiolib
26 The line above creates three chips. The first one will expose 8 lines,
33 GPIO lines exposed by it should be named.
38 Manipulating simulated lines
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-gpio.yaml | 13 This represents a group of 3-n GPIO lines used for bit-banged SPI on
14 dedicated GPIO lines.
36 description: GPIOs to use for chipselect lines.
42 description: Number of chipselect lines. Should be <0> if a single device
|
| /Documentation/sphinx/ |
| D | kernel_abi.py | 112 lines = self.runCmd(cmd, shell=True, cwd=cwd, env=shell_env)
113 nodeList = self.nestedParse(lines, self.arguments[0])
140 def nestedParse(self, lines, fname): argument
146 for l in lines.split("\n"):
148 lines = code_block + "\n\n"
155 for line in lines.split("\n"):
169 # sphinx counts lines from 0
174 kernellog.info(self.state.document.settings.env.app, "%s: parsed %i lines" % (fname, n))
|
| /Documentation/sound/soc/ |
| D | dai.rst | 14 multiplexes its data on its SDATA_OUT (playback) and SDATA_IN (capture) lines.
27 Rx lines are used for audio transmission, while the bit clock (BCLK) and
29 controller or CODEC can drive (master) the BCLK and LRC clock lines. Bit clock
51 flexible protocol. It has bit clock (BCLK) and sync (SYNC) lines that are used
52 to synchronise the link while the Tx and Rx lines are used to transmit and
|
| /Documentation/devicetree/bindings/reset/ |
| D | snps,axs10x-reset.txt | 6 represents up-to 32 reset lines.
8 As of today only the following lines are used:
28 Specifying reset lines connected to IP modules:
|
| /Documentation/devicetree/bindings/gpio/ |
| D | intel,ixp4xx-gpio.txt | 4 It supports 16 GPIO lines.
10 the first 12 GPIO lines to 12 system interrupts.
12 The remaining 4 GPIO lines can not be used for receiving
|
| D | gpio-grgpio.txt | 18 - nbits : The number of gpio lines. If not present driver assumes 32 lines.
|
| /Documentation/devicetree/bindings/arm/omap/ |
| D | crossbar.txt | 3 interrupt lines from the subsystems are not needed at the same
17 - ti,irqs-reserved: List of the reserved irq lines that are not muxed using
18 crossbar. These interrupt lines are reserved in the soc,
20 lines.
|
| /Documentation/userspace-api/media/v4l/ |
| D | field-order.rst | 10 Progressive video transmits all lines of a video image sequentially.
12 odd and even lines of the image, respectively. Alternating the so called
14 fields a cathode ray TV displays the lines interleaved, yielding the
42 Whether the older field contains the top or bottom lines is a convention
108 - Images contain both fields, the top field lines are stored first
109 in memory, immediately followed by the bottom field lines. Fields
114 - Images contain both fields, the bottom field lines are stored
115 first in memory, immediately followed by the top field lines.
|
| D | dev-sliced-vbi.rst | 11 lines of an analog video signal. During VBI no picture information is
62 lines the hardware can capture or output per frame, or the number of
82 all services may be supported by the hardware on all lines (this is
130 a driver for the cx25840 video decoder sets lines 7-22 of both
198 array (that is the number of lines potentially carrying data).
228 - Lines, usually
328 reliably identify scan lines. The field number must always be
417 embed up to 36 lines of sliced VBI data per frame in an MPEG-2 *Private
446 payload is variable length, depending on the actual number of lines of
450 with 18 lines/field with 43 bytes of data/line and a 4 byte magic
[all …]
|
| D | vidioc-g-dv-timings.rst | 99 - Height of the active video frame in lines. So for interlaced
126 - Vertical front porch in lines. For interlaced formats this refers
130 - Vertical sync length in lines. For interlaced formats this refers
134 - Vertical back porch in lines. For interlaced formats this refers
138 - Vertical front porch in lines for the even field (aka field 2) of
142 - Vertical sync length in lines for the even field (aka field 2) of
146 - Vertical back porch in lines for the even field (aka field 2) of
282 same number of half-lines. Whether half-lines can be detected or
|
| /Documentation/userspace-api/media/drivers/ |
| D | cx2341x-uapi.rst | 43 If the height is not a multiple of 32 lines, then the captured video is
145 all lines can be stored while still fitting within the maximum allowed size.
148 4 + 43 * 36, which is 4 bytes for a header and 2 * 18 VBI lines with a 1 byte
150 the cx23415/6 firmware. Besides the data for the VBI lines we also need 36 bits
151 for a bitmask determining which lines are captured and 4 bytes for a magic cookie,
153 If all lines are used, then there is no longer room for the bitmask. To solve this
157 unsigned long denote which lines of the first field are captured. Bits 18-31 of
161 'ITV0': This magic number assumes all VBI lines are captured, i.e. it implicitly
165 captured VBI lines start:
175 #define IVTV_SLICED_TYPE_TELETEXT 0x1 // Teletext (uses lines 6-22 for PAL)
|
| /Documentation/devicetree/bindings/auxdisplay/ |
| D | hit,hd44780.yaml | 14 LCDs that can display one or more lines of text. It exposes an M6800 bus
23 GPIO pins connected to the data signal lines DB0-DB7 (8-bit mode) or
65 Internal buffer width (default is 40 for displays with 1 or 2 lines, and
66 display-width-chars for displays with more than 2 lines).
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 11 interrupt lines. An output interrupt line is routed to an interrupt controller
19 sources on the appropriate interrupt lines.
21 The number of h/w fifo queues and interrupt lines dictate the usable registers.
24 and interrupt lines between different instances. The interrupt lines can also be
28 into a single IP block present within the Main NavSS. The interrupt lines from
30 over a limited number of common interrupt output lines of an Interrupt Router.
95 multiple interrupt lines connected to the MPU processor.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 6 level triggered interrupt lines, "opencores,or1k-pic-edge" for variants with
7 edge triggered interrupt lines or "opencores,or1200-pic" for machines
|
| /Documentation/devicetree/bindings/rtc/ |
| D | xlnx-rtc.txt | 4 Separate IRQ lines for seconds and alarm
10 - interrupts: IRQ lines for the RTC.
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | serial.txt | 10 Modem control lines connected to GPIO controllers are listed in the gpios
16 The gpios property is optional and can be left out when control lines are
|