| /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/userspace-api/gpio/ |
| D | gpio-v2-line-set-config-ioctl.rst | 12 GPIO_V2_LINE_SET_CONFIG_IOCTL - Update the configuration of previously requested lines.
30 requested lines.
35 Update the configuration of previously requested lines, without releasing the
38 The new configuration must specify a configuration for all requested lines.
41 :ref:`gpio-v2-get-line-config-support` that apply when requesting the lines
48 bi-directional lines between input and output, but it may also be used to
49 dynamically control edge detection, or more generally move lines seamlessly
52 To only change the value of output lines, use
|
| D | gpio-handle-set-config-ioctl.rst | 16 GPIOHANDLE_SET_CONFIG_IOCTL - Update the configuration of previously requested lines.
34 requested lines.
39 Update the configuration of previously requested lines, without releasing the
42 The configuration applies to all requested lines.
46 lines also apply when updating the line configuration, with the additional
52 bi-directional lines between input and output, but it may be used more
53 generally to move lines seamlessly from one configuration state to another.
55 To only change the value of output lines, use
|
| D | chardev.rst | 21 Similarly, for multi-function lines there may be other subsystems, such as
39 Each chip supports a number of GPIO lines,
40 :c:type:`chip.lines<gpiochip_info>`. Lines on the chip are identified by an
41 ``offset`` in the range from 0 to ``chip.lines - 1``, i.e. `[0,chip.lines)`.
43 Lines are requested from the chip using gpio-v2-get-line-ioctl.rst
44 and the resulting line request is used to access the GPIO chip's lines or
45 monitor the lines for edge events.
71 access to a set of requested lines. The line request is exposed to userspace
89 Reconfigure Lines <gpio-v2-line-set-config-ioctl>
|
| D | chardev_v1.rst | 34 Each chip supports a number of GPIO lines,
35 :c:type:`chip.lines<gpiochip_info>`. Lines on the chip are identified by an
36 ``offset`` in the range from 0 to ``chip.lines - 1``, i.e. `[0,chip.lines)`.
38 Lines are requested from the chip using either gpio-get-linehandle-ioctl.rst
39 and the resulting line handle is used to access the GPIO chip's lines, or
68 access to a set of requested lines. The line handle is exposed to userspace
85 Reconfigure Lines <gpio-handle-set-config-ioctl>
|
| D | gpio-v2-line-get-values-ioctl.rst | 12 GPIO_V2_LINE_GET_VALUES_IOCTL - Get the values of requested lines.
30 to indicate the subset of requested lines to get.
35 Get the values of requested lines.
44 The values of both input and output lines may be read.
46 For output lines, the value returned is driver and configuration dependent and
|
| D | gpio-v2-line-set-values-ioctl.rst | 12 GPIO_V2_LINE_SET_VALUES_IOCTL - Set the values of requested output lines.
30 to indicate the subset of requested lines to set and ``bits`` set to
36 Set the values of requested output lines.
45 Only the values of output lines may be set.
|
| D | gpio-handle-set-line-values-ioctl.rst | 15 GPIO_HANDLE_SET_LINE_VALUES_IOCTL - Set the values of all requested output lines.
37 Set the values of all requested output lines.
46 Only the values of output lines may be set.
47 Attempting to set the value of input lines is an error (**EPERM**).
|
| D | gpio-handle-get-line-values-ioctl.rst | 15 GPIOHANDLE_GET_LINE_VALUES_IOCTL - Get the values of all requested lines.
37 Get the values of all requested lines.
46 The values of both input and output lines may be read.
48 For output lines, the value returned is driver and configuration dependent and
|
| D | gpio-get-linehandle-ioctl.rst | 16 GPIO_GET_LINEHANDLE_IOCTL - Request a line or lines from the kernel.
32 The :c:type:`handle_request<gpiohandle_request>` specifying the lines to
38 Request a line or lines from the kernel.
40 While multiple lines may be requested, the same configuration applies to all
41 lines in the request.
46 The state of a line, including the value of output lines, is guaranteed to
|
| /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.
54 (two wires, SDA and SCL lines) by hammering (bitbang) two GPIO lines. It will
59 of wires, at least SCK and optionally MISO, MOSI and chip select lines) using
84 to a set of simple GPIO lines: RDY, NCE, ALE, CLE, NWP. It interacts with the
89 bus, data and clock line, by bit banging two GPIO lines. It will appear as
100 nothing but GPIO lines, this driver provides that and also a clearly defined
105 n GPIO lines such that you can mux in 2^n different devices by activating
106 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/gpio/ |
| D | nuvoton,sgpio.yaml | 24 - ngpios is number of nuvoton,input-ngpios GPIO lines and nuvoton,output-ngpios GPIO lines.
25 nuvoton,input-ngpios GPIO lines is only for GPI.
26 nuvoton,output-ngpios GPIO lines is only for GPO.
51 The numbers of GPIO's exposed. GPIO lines are only for GPI.
58 The numbers of GPIO's exposed. GPIO lines are only for GPO.
|
| 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/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/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/admin-guide/gpio/ |
| D | gpio-mockup.rst | 15 chips for testing purposes. The lines exposed by these chips can be accessed
31 parameter is the number of lines exposed by the chip.
35 The line above creates three chips. The first one will expose 8 lines,
42 GPIO lines exposed by it should be named.
47 Manipulating simulated lines
|
| /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.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:
|