| /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/dev-tools/ |
| D | ktap.rst | 18 lines -- and a final result. The test structure and results are
22 KTAP output is built from four different types of lines:
23 - Version lines
24 - Plan lines
25 - Test case result lines
26 - Diagnostic lines
34 Version lines
53 Plan lines
58 Plan lines must follow the format of "1..N" where N is the number of tests or subtests.
59 Plan lines follow version lines to indicate the number of nested tests.
[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/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 n GPIO lines such that you can mux in 2^n different devices by activating
101 different GPIO lines. Often the GPIOs are on a SoC and the devices are
[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/sphinx/ |
| D | kernel_abi.py | 90 … lines = subprocess.check_output(args, cwd=os.path.dirname(doc.current_source)).decode('utf-8')
91 nodeList = self.nestedParse(lines, self.arguments[0])
94 def nestedParse(self, lines, fname): argument
101 for l in lines.split("\n"):
103 lines = code_block + "\n\n"
110 for line in lines.split("\n"):
127 # sphinx counts lines from 0
132 kernellog.info(self.state.document.settings.env.app, "%s: parsed %i lines" % (fname, n))
|
| D | kernel_feat.py | 96 … lines = subprocess.check_output(args, cwd=os.path.dirname(doc.current_source)).decode('utf-8')
102 for line in lines.split("\n"):
115 def nestedParse(self, lines, fname): argument
121 for l in lines.split("\n"):
123 lines = code_block + "\n\n"
125 for c, l in enumerate(lines.split("\n")):
|
| /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/serial/ |
| D | nxp,sc16is7xx.txt | 27 should have shared GPIO lines configured as
28 modem control lines.
47 nxp,modem-control-line-ports = <1>; /* Port 1 as modem control lines */
58 nxp,modem-control-line-ports = <0 1>; /* Ports 0 and 1 as modem control lines */
86 should have shared GPIO lines configured as
87 modem control lines.
106 nxp,modem-control-line-ports = <1>; /* Port 1 as modem control lines */
117 nxp,modem-control-line-ports = <0 1>; /* Ports 0 and 1 as modem control lines */
|
| /Documentation/devicetree/bindings/display/ |
| D | arm,malidp.yaml | 65 arm,malidp-output-port-lines:
68 Number of output lines/bits for each colour channel.
70 - description: number of output lines for the red channel (R)
71 - description: number of output lines for the green channel (G)
72 - description: number of output lines for the blue channel (B)
98 - arm,malidp-output-port-lines
110 arm,malidp-output-port-lines = /bits/ 8 <8 8 8>;
|
| /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
23 parameter is the number of lines exposed by the chip.
27 The line above creates three chips. The first one will expose 8 lines,
34 GPIO lines exposed by it should be named.
39 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/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/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-mmio.yaml | 43 Register to READ the value of the GPIO lines. If GPIO line is high,
48 Register to SET the value of the GPIO lines. Setting a bit in this
51 Register to CLEAR the value of the GPIO lines. Setting a bit in this
53 the SET register will be used to clear the GPIO lines as well, by
80 If this property is present, the controller cannot drive the GPIO lines.
|
| /Documentation/devicetree/bindings/reset/ |
| D | snps,axs10x-reset.yaml | 16 represents up-to 32 reset lines.
17 As of today only the following lines are used:
45 // Specifying reset lines connected to IP modules:
|
| /Documentation/userspace-api/media/drivers/ |
| D | cx2341x-uapi.rst | 41 If the height is not a multiple of 32 lines, then the captured video is
143 all lines can be stored while still fitting within the maximum allowed size.
146 4 + 43 * 36, which is 4 bytes for a header and 2 * 18 VBI lines with a 1 byte
148 the cx23415/6 firmware. Besides the data for the VBI lines we also need 36 bits
149 for a bitmask determining which lines are captured and 4 bytes for a magic cookie,
151 If all lines are used, then there is no longer room for the bitmask. To solve this
155 unsigned long denote which lines of the first field are captured. Bits 18-31 of
159 'ITV0': This magic number assumes all VBI lines are captured, i.e. it implicitly
163 captured VBI lines start:
173 #define IVTV_SLICED_TYPE_TELETEXT 0x1 // Teletext (uses lines 6-22 for PAL)
|
| /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 | pixfmt-yuv-planar.rst | 20 tiled. Padding may be supported at the end of the lines, and the line stride of
41 chroma lines is identical to the padding of the luma lines. Without horizontal
215 direction. Chroma lines contain half the number of pixels and the same number
216 of bytes as luma lines, and the chroma plane contains half the number of lines
306 subsampled by 2 in each direction. Chroma lines contain half the number of
307 pixels and the same number of bytes as luma lines, and the chroma plane
308 contains half the number of lines of the luma plane. Each tile follows the
407 horizontal direction. Chroma lines contain half the number of pixels and the
408 same number of bytes as luma lines, and the chroma plane contains the same
409 number of lines as the luma plane.
[all …]
|
| 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
337 reliably identify scan lines. The field number must always be
426 embed up to 36 lines of sliced VBI data per frame in an MPEG-2 *Private
455 payload is variable length, depending on the actual number of lines of
459 with 18 lines/field with 43 bytes of data/line and a 4 byte magic
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,q6dsp-lpass-ports.yaml | 41 qcom,sd-lines:
44 List of serial data lines used by this dai.should be one or more of the 0-3 sd lines.
138 - qcom,sd-lines
162 qcom,sd-lines = <0 1 2 3>;
|
| D | qcom,lpass-cpu.yaml | 92 qcom,playback-sd-lines:
94 description: list of MI2S data lines for playback
96 qcom,capture-sd-lines:
98 description: list of MI2S data lines for capture
281 /* Optional to set different MI2S SD lines */
284 qcom,playback-sd-lines = <1>;
285 qcom,capture-sd-lines = <0>;
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | ti,omap-mailbox.yaml | 20 output interrupt lines. An output interrupt line is routed to an interrupt
29 interrupt lines.
31 The number of h/w fifo queues and interrupt lines dictate the usable
34 h/w fifo queues and interrupt lines between different instances. The interrupt
35 lines can also be routed to different processor sub-systems on DRA7xx as they
39 NavSS. The interrupt lines from all these clusters are multiplexed and routed
41 output lines of an Interrupt Router. The AM64x SoCS also uses a single IP
43 smaller, and the interrupt output lines are connected directly to various
78 on mailboxes that have multiple interrupt lines connected to the MPU
135 is required on SoCs where the interrupt lines are connected through a
|