Home
last modified time | relevance | path

Searched +full:in +full:- +full:line (Results 1 – 25 of 1034) sorted by relevance

12345678910>>...42

/Documentation/userspace-api/gpio/
Dchardev.rst1 .. SPDX-License-Identifier: GPL-2.0
7 This is latest version (v2) of the character device API, as defined in
10 First added in 5.10.
18 Read Documentation/driver-api/gpio/drivers-on-gpio.rst to avoid reinventing
19 kernel wheels in userspace.
21 Similarly, for multi-function lines there may be other subsystems, such as
23 Documentation/driver-api/pwm.rst, Documentation/w1/index.rst etc, that
26 Basic examples using the character device API can be found in ``tools/gpio/*``.
28 The API is based around two major objects, the :ref:`gpio-v2-chip` and the
29 :ref:`gpio-v2-line-request`.
[all …]
Dchardev_v1.rst1 .. SPDX-License-Identifier: GPL-2.0
12 in the future. The v2 API is a functional superset of the v1 API so any
18 First added in 4.8.
20 The API is based around three major objects, the :ref:`gpio-v1-chip`, the
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.
26 .. _gpio-v1-chip:
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
[all …]
Dgpio-v2-get-line-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
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
[all …]
Dgpio-get-linehandle-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
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.
41 lines in the request.
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**).
[all …]
Dgpio-get-lineinfo-watch-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-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
[all …]
Dgpio-v2-get-lineinfo-watch-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
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.
[all …]
Dgpio-get-lineevent-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
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
42 described in gpio-lineevent-data-read.rst.
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
[all …]
Dgpio-v2-lineinfo-changed-read.rst1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINEINFO_CHANGED_READ - Read line info changed events for watched
30 The number of bytes available in ``buf``, which must be at least the size
36 Read line info changed events for watched lines from the chip.
39 Monitoring line info changes is not generally required, and would typically
42 These events relate to changes in a line's request state or configuration,
43 not its value. Use gpio-v2-line-event-read.rst to receive events when a
44 line changes value.
46 A line must be watched using gpio-v2-get-lineinfo-watch-ioctl.rst to generate
48 of the line will generate an info changed event.
[all …]
Dgpio-v2-get-lineinfo-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
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
49 On error -1 and the ``errno`` variable is set appropriately.
50 Common error codes are described in error-codes.rst.
Dgpio-v2-line-set-config-ioctl.rst1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINE_SET_CONFIG_IOCTL - Update the configuration of previously requested lines.
25 The file descriptor of the GPIO character device, as returned in the
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.
[all …]
Dgpio-lineevent-data-read.rst1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-line-event-read.rst.
16 GPIO_LINEEVENT_DATA_READ - Read edge detection events from a line event.
27 The file descriptor of the GPIO character device, as returned in the
28 :c:type:`request.fd<gpioevent_request>` by gpio-get-lineevent-ioctl.rst.
34 The number of bytes available in ``buf``, which must be at
40 Read edge detection events for a line from a line event.
42 Edge detection must be enabled for the input line using either
45 the input line.
47 Edges are defined in terms of changes to the logical line value, so an inactive
[all …]
/Documentation/devicetree/bindings/sound/
Dmt2701-cs42448.txt4 - compatible: "mediatek,mt2701-cs42448-machine"
5 - mediatek,platform: the phandle of MT2701 ASoC platform
6 - audio-routing: a list of the connections between audio
7 - mediatek,audio-codec: the phandles of cs42448 codec
8 - mediatek,audio-codec-bt-mrg the phandles of bt-sco dummy codec
9 - pinctrl-names: Should contain only one value - "default"
10 - pinctrl-0: Should specify pin control groups used for this controller.
11 - i2s1-in-sel-gpio1, i2s1-in-sel-gpio2: Should specify two gpio pins to
12 control I2S1-in mux.
17 compatible = "mediatek,mt2701-cs42448-machine";
[all …]
Ddavinci-evm-audio.txt4 - compatible : "ti,da830-evm-audio" : forDM365/DA8xx/OMAPL1x/AM33xx
5 - ti,model : The user-visible name of this sound complex.
6 - ti,audio-codec : The phandle of the TLV320AIC3x audio codec
7 - ti,mcasp-controller : The phandle of the McASP controller
8 - ti,audio-routing : A list of the connections between audio components.
14 - ti,codec-clock-rate : The Codec Clock rate (in Hz) applied to the Codec.
15 - clocks : Reference to the master clock
16 - clock-names : The clock should be named "mclk"
17 - Either codec-clock-rate or the codec-clock reference has to be defined. If
24 * Line Out
[all …]
Dwidgets.txt3 This mainly specifies audio off-codec DAPM widgets.
5 Each entry is a pair of strings in DT:
7 "template-wname", "user-supplied-wname"
9 The "template-wname" being the template widget name and currently includes:
10 "Microphone", "Line", "Headphone" and "Speaker".
12 The "user-supplied-wname" being the user specified widget name.
15 simple-audio-widgets =
17 "Line", "Line In Jack",
18 "Line", "Line Out Jack",
/Documentation/sphinx/
Dmaintainers_include.py2 # SPDX-License-Identifier: GPL-2.0
3 # -*- coding: utf-8; mode: python -*-
7 maintainers-include
10 Implementation of the ``maintainers-include`` reST-directive.
15 The ``maintainers-include`` reST-directive performs extensive parsing
16 specific to the Linux kernel's standard "MAINTAINERS" file, in an
32 app.add_directive("maintainers-include", MaintainersInclude)
40 u"""MaintainersInclude (``maintainers-include``) directive"""
44 """Parse all the MAINTAINERS lines into ReST for human-readability"""
63 for line in open(path):
[all …]
/Documentation/admin-guide/
Ddynamic-debug-howto.rst9 debug-print code to obtain additional kernel information.
16 * a Catalog of all *prdbgs* in your kernel.
22 - source filename
23 - function name
24 - line number (including ranges of line numbers)
25 - module name
26 - format string
27 - class name (as known/declared by each module)
29 NOTE: To actually get the debug-print output on the console, you may
31 Read about these kernel parameters in
[all …]
/Documentation/devicetree/bindings/gpio/
Dgpio-mmio.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/gpio-mmio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
11 - Bartosz Golaszewski <brgl@bgdev.pl>
15 of set/clear-bit registers. Such controllers are common for glue logic in
16 FPGAs or ASICs. Commonly, these controllers are accessed over memory-mapped
17 NAND-style parallel busses.
22 - brcm,bcm6345-gpio
[all …]
/Documentation/userspace-api/media/v4l/
Ddev-sliced-vbi.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 VBI stands for Vertical Blanking Interval, a gap in the sequence of
15 Sliced VBI devices use hardware to demodulate data transmitted in the
17 :ref:`raw VBI interface <raw-vbi>`. The data is passed as short
18 packets of fixed size, covering one scan line each. The number of
36 respectively, in the ``capabilities`` field of struct
51 .. _sliced-vbi-format-negotitation:
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
[all …]
/Documentation/devicetree/bindings/iio/adc/
Dadi,ad7944.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michael Hennerich <Michael.Hennerich@analog.com>
11 - Nuno Sá <nuno.sa@analog.com>
14 A family of pin-compatible single channel differential analog to digital
15 converters with SPI support in a LFCSP package.
21 $ref: /schemas/spi/spi-peripheral-props.yaml#
26 - adi,ad7944
27 - adi,ad7985
[all …]
/Documentation/sound/hd-audio/
Dcontrols.rst2 HD-Audio Codec-Specific Mixer Controls
6 This file explains the codec-specific mixer controls.
9 --------------
12 This is an enum control to change the surround-channel setup,
16 jack-retasking of multi-I/O jacks.
18 Auto-Mute Mode
19 This is an enum control to change the auto-mute behavior of the
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
[all …]
/Documentation/driver-api/
Dreset.rst1 .. SPDX-License-Identifier: GPL-2.0-only
13 the `consumer driver interface <#consumer-driver-interface>`__ (`API reference
14 <#reset-consumer-api>`__), which allows peripheral drivers to request control
16 <#reset-controller-driver-interface>`__ (`API reference
17 <#reset-controller-driver-api>`__), which is used by drivers for reset
25 --------
29 Reset line
31 Physical reset line carrying a reset signal from a reset controller
37 Most commonly this is a single bit in reset controller register space that
38 either allows direct control over the physical state of the reset line, or
[all …]
/Documentation/driver-api/gpio/
Ddriver.rst18 line is not general purpose, it is not GPIO and should not be handled by a
19 GPIO chip. The use case is the indicative: certain lines in a system may be
21 of a general purpose I/O. On the other hand a LED driver line may be used as a
26 between 0 and n-1, n being the number of GPIOs managed by the chip.
29 example if a system uses a memory-mapped set of I/O-registers where 32 GPIO
30 lines are handled by one bit per line in a 32-bit register, it makes sense to
31 use hardware offsets 0..31 for these, corresponding to bits 0..31 in the
35 line is never made visible outside of the driver.
37 On top of this internal number, each GPIO line also needs to have a global
38 number in the integer GPIO namespace so that it can be used with the legacy GPIO
[all …]
/Documentation/userspace-api/media/drivers/
Dcx2341x-uapi.rst1 .. SPDX-License-Identifier: GPL-2.0
6 Non-compressed file format
7 --------------------------
19 and from top to bottom. Each block is transmitted in turn, line-by-line.
21 So the first 16 bytes are the first line of the top-left block, the
22 second 16 bytes are the second line of the top-left block, etc. After
23 transmitting this block the first line of the block on the right to the
27 to right, top to bottom. Each block is transmitted in turn, line-by-line.
29 So the first 16 bytes are the first line of the top-left block and
30 contain 8 UV value pairs (16 bytes in total). The second 16 bytes are the
[all …]
/Documentation/driver-api/tty/
Dtty_ldisc.rst1 .. SPDX-License-Identifier: GPL-2.0
4 TTY Line Discipline
9 TTY line discipline process all incoming and outgoing character from/to a tty
10 device. The default line discipline is :doc:`N_TTY <n_tty>`. It is also a
13 characters -- it throws them away.
18 Line disciplines are registered with tty_register_ldisc() passing the ldisc
21 returns an error then it won’t get called. Do not re-use ldisc numbers as they
23 demons to eat your computer. You must not re-register over the top of the line
25 demons. In order to remove a line discipline call tty_unregister_ldisc().
28 tty_ldisc structure in the ldisc table counts the number of lines using this
[all …]
/Documentation/firmware-guide/acpi/
Dgpio-properties.rst1 .. SPDX-License-Identifier: GPL-2.0
31 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
34 Package () { "reset-gpios", Package () { ^BTH, 1, 1, 0 } },
35 Package () { "shutdown-gpios", Package () { ^BTH, 0, 0, 0 } },
46 typically this is the device itself (BTH in our case).
48 Index of the GpioIo()/GpioInt() resource in _CRS starting from zero.
50 Pin in the GpioIo()/GpioInt() resource. Typically this is zero.
58 Note, active_low in _DSD does not make sense for GpioInt() resource and
61 In our Bluetooth example the "reset-gpios" refers to the second GpioIo()
62 resource, second pin in that resource with the GPIO number of 31.
[all …]

12345678910>>...42