| /Documentation/userspace-api/gpio/ |
| D | chardev_v1.rst | 21 :ref:`gpio-v1-line-handle`, and the :ref:`gpio-v1-line-event`.
23 Where "line event" is used in this document it refers to the request that can
24 monitor a line for edge events, not the edge events themselves.
39 and the resulting line handle is used to access the GPIO chip's lines, or
40 gpio-get-lineevent-ioctl.rst and the resulting line event is used to monitor
41 a GPIO line for edge events.
54 Get Line Handle <gpio-get-linehandle-ioctl>
55 Get Line Event <gpio-get-lineevent-ioctl>
57 Get Line Info <gpio-get-lineinfo-ioctl>
58 Watch Line Info <gpio-get-lineinfo-watch-ioctl>
[all …]
|
| D | chardev.rst | 29 :ref:`gpio-v2-line-request`.
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
58 Get Line <gpio-v2-get-line-ioctl>
60 Get Line Info <gpio-v2-get-lineinfo-ioctl>
61 Watch Line Info <gpio-v2-get-lineinfo-watch-ioctl>
62 Unwatch Line Info <gpio-get-lineinfo-unwatch-ioctl>
63 Read Line Info Changed Events <gpio-v2-lineinfo-changed-read>
65 .. _gpio-v2-line-request:
67 Line Request
[all …]
|
| D | gpio-v2-get-lineinfo-watch-ioctl.rst | 12 GPIO_V2_GET_LINEINFO_WATCH_IOCTL - Enable watching a line for changes to its
30 the ``offset`` set to indicate the line to watch
35 Enable watching a line for changes to its request state and configuration
36 information. Changes to line info include a line being requested, released
40 Watching line info is not generally required, and would typically only be
43 The line info does NOT include the line value.
44 The line must be requested using gpio-v2-get-line-ioctl.rst to access
45 its value, and the line request can monitor a line for events using
46 gpio-v2-line-event-read.rst.
52 Once a watch is set, any changes to line info will generate events which can be
[all …]
|
| D | gpio-v2-get-line-ioctl.rst | 12 GPIO_V2_GET_LINE_IOCTL - Request a line or lines from the kernel.
34 On success, the requesting process is granted exclusive access to the line
35 value, write access to the line configuration, and may receive events when
36 edges are detected on the line, all of which are described in more detail in
37 :ref:`gpio-v2-line-request`.
39 A number of lines may be requested in the one line request, and request
41 as possible. e.g. gpio-v2-line-get-values-ioctl.rst will read all the
44 The state of a line, including the value of output lines, is guaranteed to
46 file descriptor is closed, the state of the line becomes uncontrolled from
49 Requesting a line already in use is an error (**EBUSY**).
[all …]
|
| D | gpio-get-lineinfo-watch-ioctl.rst | 16 GPIO_GET_LINEINFO_WATCH_IOCTL - Enable watching a line for changes to its
34 the ``offset`` set to indicate the line to watch
39 Enable watching a line for changes to its request state and configuration
40 information. Changes to line info include a line being requested, released
44 Watching line info is not generally required, and would typically only be
47 The line info does NOT include the line value.
49 The line must be requested using gpio-get-linehandle-ioctl.rst or
50 gpio-get-lineevent-ioctl.rst to access its value, and the line event can
51 monitor a line for events using gpio-lineevent-data-read.rst.
57 Once a watch is set, any changes to line info will generate events which can be
[all …]
|
| D | gpio-get-lineevent-ioctl.rst | 11 gpio-v2-get-line-ioctl.rst.
16 GPIO_GET_LINEEVENT_IOCTL - Request a line with edge detection from the kernel.
32 The :c:type:`event_request<gpioevent_request>` specifying the line
38 Request a line with edge detection from the kernel.
40 On success, the requesting process is granted exclusive access to the line
41 value and may receive events when edges are detected on the line, as
44 The state of a line is guaranteed to remain as requested until the returned
46 the line becomes uncontrolled from the userspace perspective, and may revert
49 Requesting a line already in use is an error (**EBUSY**).
51 Requesting edge detection on a line that does not support interrupts is an
[all …]
|
| D | gpio-v2-get-lineinfo-ioctl.rst | 12 GPIO_V2_GET_LINEINFO_IOCTL - Get the publicly available information for a line.
29 ``offset`` field set to indicate the line to be collected.
34 Get the publicly available information for a line.
36 This information is available independent of whether the line is in use.
39 The line info does not include the line value.
41 The line must be requested using gpio-v2-get-line-ioctl.rst to access its
|
| D | gpio-get-linehandle-ioctl.rst | 11 gpio-v2-get-line-ioctl.rst.
16 GPIO_GET_LINEHANDLE_IOCTL - Request a line or lines from the kernel.
38 Request a line or lines from the kernel.
43 On success, the requesting process is granted exclusive access to the line
44 value and write access to the line configuration.
46 The state of a line, including the value of output lines, is guaranteed to
48 file descriptor is closed, the state of the line becomes uncontrolled from
51 Requesting a line already in use is an error (**EBUSY**).
53 Closing the ``chip_fd`` has no effect on existing line handles.
65 line is requested "as-is" to allow reading of the line value without altering
[all …]
|
| D | gpio-get-lineinfo-ioctl.rst | 16 GPIO_GET_LINEINFO_IOCTL - Get the publicly available information for a line.
33 ``offset`` field set to indicate the line to be collected.
38 Get the publicly available information for a line.
40 This information is available independent of whether the line is in use.
43 The line info does not include the line value.
45 The line must be requested using gpio-get-linehandle-ioctl.rst or
|
| D | gpio-v2-line-set-config-ioctl.rst | 26 :c:type:`request.fd<gpio_v2_line_request>` by gpio-v2-get-line-ioctl.rst.
36 line or introducing potential glitches.
40 The same :ref:`gpio-v2-get-line-config-rules` and
41 :ref:`gpio-v2-get-line-config-support` that apply when requesting the lines
42 also apply when updating the line configuration, with the additional
44 If no direction flag is set in the configuration for a given line then the
45 configuration for that line is left unchanged.
53 gpio-v2-line-set-values-ioctl.rst.
|
| /Documentation/RCU/Design/Memory-Ordering/ |
| D | rcu_node-lock.svg | 80 <!-- Line: box -->
81 <!-- Line: box -->
82 <!-- Line: box -->
83 <!-- Line -->
85 <!-- Line -->
87 <!-- Line -->
89 <!-- Line -->
91 <!-- Line: box -->
92 <!-- Line: box -->
93 <!-- Line -->
[all …]
|
| D | TreeRCU-callback-invocation.svg | 234 <!-- Line: box -->
235 <!-- Line: box -->
236 <!-- Line: box -->
237 <!-- Line -->
239 <!-- Line -->
241 <!-- Line -->
243 <!-- Line -->
245 <!-- Line: box -->
246 <!-- Line: box -->
247 <!-- Line -->
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-linecard.rst | 4 Devlink Line card
11 line cards that serve as a detachable PHY modules for modular switch
14 * Get a list of supported line card types.
15 * Provision of a slot with specific line card type.
16 * Get and monitor of line card state and its change.
18 Line card according to the type may contain one or more gearboxes
20 of different speed. Line card ensures N:M mapping between
26 Each line card devlink object is created by device driver,
27 according to the physical line card slots available on the device.
31 might not have a way to detect line card type. For that devices,
[all …]
|
| /Documentation/arch/arm/samsung/ |
| D | clksrc-change-registers.awk | 69 while (getline line < ARGV[1] > 0) {
70 if (line ~ /\#define.*_MASK/ &&
71 !(line ~ /USB_SIG_MASK/)) {
72 splitdefine(line, fields)
75 printf "MASK " line "\n" > "/dev/stderr"
98 if ((getline line) <= 0) {
103 if (line ~ /\.shift/) {
104 shift = extract_value(line)
105 } else if (line ~ /\.mask/) {
106 mask = extract_value(line)
[all …]
|
| /Documentation/devicetree/bindings/media/cec/ |
| D | cec-gpio.yaml | 13 The HDMI CEC GPIO module supports CEC implementations where the CEC line is
14 hooked up to a pull-up GPIO line and - optionally - the HPD line is hooked up
15 to another GPIO line.
17 Please note:: the maximum voltage for the CEC line is 3.63V, for the HPD and
19 circuitry when connecting them to a GPIO line.
28 GPIO that the CEC line is connected to. The line should be tagged as open
34 GPIO that the HPD line is connected to. Used for debugging HPD changes
35 when the CEC line is not associated with an HDMI receiver/transmitter.
40 GPIO that the 5V line is connected to. Used for debugging changes on the
41 5V line.
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-mmio.yaml | 43 Register to READ the value of the GPIO lines. If GPIO line is high,
44 the bit will be set. If the GPIO line is low, the bit will be cleared.
49 register will drive the GPIO line high.
52 register will drive the GPIO line low. If this register is omitted,
54 actively writing the line with 0.
56 Register to set the line as OUTPUT. Setting a bit in this register
57 will turn that line into an output line. Conversely, clearing a bit
58 will turn that line into an input.
60 Register to set this line as INPUT. Setting a bit in this register
61 will turn that line into an input line. Conversely, clearing a bit
[all …]
|
| /Documentation/sphinx/ |
| D | maintainers_include.py | 63 for line in open(path):
65 if descriptions and line.startswith('Maintainers'):
67 # Ensure a blank line following the last "|"-prefixed line.
73 if re.search('^[A-Z0-9]', line):
77 line = line.rstrip()
81 m = re.search(pat, line)
84 line = re.sub(pat, ':doc:`%s <../%s>`' % (m.group(2), m.group(2)), line)
90 output = "| %s" % (line.replace("\\", "\\\\"))
93 m = re.search(r"\s(\S):\s", line)
97 m = re.search(r"\*([^\*]+)\*", line)
[all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7944.yaml | 48 line is used to initiate the conversion and the SDI line is connected to
57 device on the bus. In this mode, SDI is tied to VIO, and the CNV line
58 can be connected to the CS line of the SPI controller or to a GPIO, in
59 which case the CS line of the controller is unused.
61 on wiring when multiple ADCs are used. In this mode, the SDI line of
64 chain is connected to the SPI bus. The CNV line of all chips are tied
65 together. The CS line of the SPI controller can be used as the CNV line
105 CS line of the SPI controller.
110 GPIO connected to the TURBO line. If omitted, it is assumed that the TURBO
111 line is hard-wired and the state is determined by the adi,always-turbo
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | mt2701-cs42448.txt | 21 "Line Out Jack", "AOUT1L",
22 "Line Out Jack", "AOUT1R",
23 "Line Out Jack", "AOUT2L",
24 "Line Out Jack", "AOUT2R",
25 "Line Out Jack", "AOUT3L",
26 "Line Out Jack", "AOUT3R",
27 "Line Out Jack", "AOUT4L",
28 "Line Out Jack", "AOUT4R",
|
| D | davinci-evm-audio.txt | 24 * Line Out
26 * Line In
40 "Line Out", "LLOUT",
41 "Line Out", "RLOUT",
45 "LINE1L", "Line In",
46 "LINE2L", "Line In",
47 "LINE1R", "Line In",
48 "LINE2R", "Line In";
|
| D | widgets.txt | 10 "Microphone", "Line", "Headphone" and "Speaker".
17 "Line", "Line In Jack",
18 "Line", "Line Out Jack",
|
| /Documentation/sound/hd-audio/ |
| D | controls.rst | 20 headphone and line-out jacks. If built-in speakers and headphone
21 and/or line-out jacks are available on a machine, this controls
23 When there are only either headphones or line-out jacks, it gives
27 When both headphone and line-out jacks are present, it gives
28 "Disabled", "Speaker Only" and "Line-Out+Speaker". When
29 speaker-only is chosen, plugging into a headphone or a line-out jack
30 mutes the speakers, but not line-outs. When line-out+speaker is
32 line-outs.
50 Headphone as Line Out
51 When this control is ON, treat the headphone jacks as line-out
[all …]
|
| /Documentation/admin-guide/ |
| D | dynamic-debug-howto.rst | 24 - line number (including ranges of line numbers)
83 :#> ddcmd file svcsock.c line 1603 +p
84 :#> ddcmd "file svcsock.c line 1603 +p"
85 :#> ddcmd ' file svcsock.c line 1603 +p '
122 'line' line-range
124 line-range ::= lineno |
133 ``line-range`` cannot contain space, e.g.
155 file inode.c:1-100 # parse :tail as a line-range (above)
193 line
194 The given line number or range of line numbers is compared
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-sliced-vbi.rst | 18 packets of fixed size, covering one scan line each. The number of
63 services it can identify on a given line are limited. For example on PAL
64 line 16 the hardware may be able to look for a VPS or Teletext signal,
81 hardware must be told which VBI service to expect on each scan line. Not
84 other services can only be inserted in one specific line). In many
131 fields [#f1]_ to ``V4L2_SLICED_TELETEXT_B`` and line 23 of the first
145 driver shall look for or insert on the respective scan line.
148 When the hardware cannot handle multiple services on the same line
153 map to ITU-R line numbers\ [#f2]_ as follows:
157 - 525 line systems
[all …]
|
| /Documentation/driver-api/ |
| D | reset.rst | 29 Reset line
31 Physical reset line carrying a reset signal from a reset controller
38 either allows direct control over the physical state of the reset line, or
40 reset line.
52 reset line.
61 trigger reset pulses, or to query reset line status.
85 effect on the reset line.
88 That is, an assert causes the reset line to be asserted immediately, and a
89 deassert causes the reset line to be deasserted immediately.
100 will actually cause the reset line to be asserted.
[all …]
|
![[all …]](/android16-6.12-lts/more/Documentation/RCU/Design/Memory-Ordering/rcu_node-lock.svg?full=Line){kind=link}
![[all …]](/android16-6.12-lts/more/Documentation/RCU/Design/Memory-Ordering/TreeRCU-callback-invocation.svg?full=Line){kind=link}