Searched +full:master +full:- +full:side (Results 1 – 25 of 61) sorted by relevance
123
| /Documentation/driver-api/ |
| D | spi.rst | 7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data
8 line, and a "Master In, Slave Out" (MISO) data line. SPI is a full
12 additional chipselect line is usually active-low (nCS); four signals are
18 only "master" side interfaces are supported, where Linux talks to SPI
25 a pair of FIFOs connected to dual DMA engines on the other side of the
28 the SPI side of their device as a :c:type:`struct spi_controller
29 <spi_controller>`. SPI devices are children of that master,
33 board-specific initialization code. A :c:type:`struct spi_driver
46 .. kernel-doc:: include/linux/spi/spi.h
49 .. kernel-doc:: drivers/spi/spi.c
[all …]
|
| D | i2c.rst | 5 the "Inter-IC" bus, a simple bus protocol which is widely used where low
7 some vendors use another name (such as "Two-Wire Interface", TWI) for
12 I2C is a multi-master bus; open drain signaling is used to arbitrate
16 The Linux I2C programming interfaces support the master side of bus
17 interactions and the slave side. The programming interface is
38 .. kernel-doc:: include/linux/i2c.h
41 .. kernel-doc:: drivers/i2c/i2c-boardinfo.c
44 .. kernel-doc:: drivers/i2c/i2c-core-base.c
47 .. kernel-doc:: drivers/i2c/i2c-core-smbus.c
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-arb-gpio-challenge.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO-based I2C Arbitration Using a Challenge & Response Mechanism
10 - Doug Anderson <dianders@chromium.org>
11 - Peter Rosin <peda@axentia.se>
15 the master of an I2C bus in a multimaster situation.
18 standard I2C multi-master rules. Using GPIOs is generally useful in the case
25 problems (hard to tell if i2c issues were caused by one master, another,
[all …]
|
| D | i2c-mux-reg.txt | 1 Register-based I2C Bus Mux
7 - compatible: i2c-mux-reg
8 - i2c-parent: The phandle of the I2C bus that this multiplexer's master-side
10 * Standard I2C mux properties. See i2c-mux.yaml in this directory.
11 * I2C child bus nodes. See i2c-mux.yaml in this directory.
14 - reg: this pair of <offset size> specifies the register to control the mux.
15 The <offset size> depends on its parent node. It can be any memory-mapped
18 - little-endian: The existence indicates the register is in little endian.
19 - big-endian: The existence indicates the register is in big endian.
20 If both little-endian and big-endian are omitted, the endianness of the
[all …]
|
| D | i2c-mux-pinctrl.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-mux-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Pinctrl-based I2C Bus Mux
10 - Wolfram Sang <wsa@kernel.org>
17 +-----+ +-----+
19 +------------------------+ +-----+ +-----+
21 | /----|------+--------+
22 | +---+ +------+ | child bus A, on first set of pins
[all …]
|
| D | i2c-mux-gpmux.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-mux-gpmux.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Peter Rosin <peda@axentia.se>
16 .-----. .-----.
18 .------------. '-----' '-----'
20 | | .--------+--------'
21 | .------. | .------+ child bus A, on MUX value set to 0
22 | | I2C |-|--| Mux |
[all …]
|
| D | i2c-mux-gpio.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-mux-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO-based I2C Bus Mux
10 - Wolfram Sang <wsa@kernel.org>
15 +-----+ +-----+
17 +------------+ +-----+ +-----+
19 | | /--------+--------+
20 | +------+ | +------+ child bus A, on GPIO value set to 0
[all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smp2p.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andy Gross <agross@kernel.org>
11 - Bjorn Andersson <bjorn.andersson@linaro.org>
12 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
16 of a single 32-bit value between two processors. Each value has a single
17 writer (the local side) and a single reader (the remote side). Values are
35 $ref: /schemas/types.yaml#/definitions/phandle-array
37 - items:
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | mdio-mux.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/net/mdio-mux.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andrew Lunn <andrew@lunn.ch>
18 mdio-parent-bus:
21 The phandle of the MDIO bus that this multiplexer's master-side port is
24 '#address-cells':
27 '#size-cells':
31 '^mdio@[0-9a-f]+$':
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 5 The GPIO based I2C bus master driver can be configured to provide fault
7 which is driven by the I2C bus master driver under test. The GPIO fault
9 master driver should handle gracefully.
12 'i2c-fault-injector' subdirectory in the Kernel debugfs filesystem, usually
15 injection. They will be described now along with their intended use-cases.
21 -----
26 because the bus master under test will not be able to clock. It should detect
31 -----
36 master under test should detect this condition and trigger a bus recovery (see
48 there are I2C client devices which detect a stuck SDA on their side and release
[all …]
|
| D | instantiating-devices.rst | 13 --------------------------------------------
17 is known in advance. It is thus possible to pre-declare the I2C devices
24 instantiated automatically by i2c-core. The devices will be automatically
32 subnodes of the master controller.
36 .. code-block:: dts
39 /* ... master properties skipped ... */
40 clock-frequency = <100000>;
49 gpio-controller;
50 #gpio-cells = <2>;
64 which is currently located at Documentation/firmware-guide/acpi/enumeration.rst.
[all …]
|
| /Documentation/trace/ |
| D | stm.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 which is assigned a unique pair of master and channel. While some of
14 master/channel combination from this pool.
16 On the receiving end of this STP stream (the decoder side), trace
17 sources can only be identified by master/channel combination, so in
20 master/channel pairs to the trace sources that it understands.
23 master 7 channel 15, while arbitrary user applications can use masters
34 associated with it, located in "stp-policy" subsystem directory in
40 $ ls /config/stp-policy/dummy_stm.my-policy/user
42 $ cat /config/stp-policy/dummy_stm.my-policy/user/masters
[all …]
|
| /Documentation/spi/ |
| D | spi-lm70llp.rst | 2 spi_lm70llp : LM70-LLP parport-to-SPI adapter
15 -----------
19 This is a SPI master controller driver. It can be used in conjunction with
27 --------------------
28 The schematic for this particular board (the LM70EVAL-LLP) is
39 D0 2 - -
40 D1 3 --> V+ 5
41 D2 4 --> V+ 5
42 D3 5 --> V+ 5
43 D4 6 --> V+ 5
[all …]
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 13 1. Bus clash or parity errors: This mechanism relies on low-level detectors
20 impact its audibility (most-significant bits will be more impacted in PCM),
34 be applied. In case of a bad programming (command sent to non-existent
35 Slave or to a non-implemented register) or electrical issue, no response
36 signals the command was ignored. Some Master implementations allow for a
40 reset and re-enumerate all devices.
47 driver will return a -ETIMEOUT. Such timeouts are symptoms of a faulty
56 problems when enabling multiple bus segments (a command with side effects
58 hard-reset might be the best solution.
62 that the Slave might behave in implementation-defined ways. The bus
[all …]
|
| /Documentation/hwmon/ |
| D | lm70.rst | 35 -----------
46 comprise the MOSI/MISO loop. At the end of the transfer, the 11-bit 2's
48 driver for interpretation. This driver makes use of the kernel's in-core
51 As a real (in-tree) example of this "SPI protocol driver" interfacing
52 with a "SPI master controller driver", see drivers/spi/spi_lm70llp.c
56 13-bit temperature data (0.0625 degrees celsius resolution).
60 The TMP125 is less accurate and provides 10-bit temperature data
63 The LM71 is also very similar; main difference is 14-bit temperature
67 ---------
68 Jean Delvare <jdelvare@suse.de> for mentoring the hwmon-side driver
|
| /Documentation/admin-guide/ |
| D | devices.rst | 11 version in the mainline Linux kernel is the master document. Updates
13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>` document).
63 --------------------------------------
81 /dev/nfsd socksys symbolic Required by iBCS-2
82 /dev/X0R null symbolic Required by iBCS-2
85 Note: ``/dev/X0R`` is <letter X>-<digit 0>-<letter R>.
100 /dev/scd? sr? hard Alternate SCSI CD-ROM name
114 /dev/cdrom CD-ROM device symbolic Current CD-ROM device
115 /dev/cdwriter CD-writer symbolic Current CD-writer device
138 Non-transient sockets and named pipes may exist in /dev. Common entries are:
[all …]
|
| /Documentation/sound/designs/ |
| D | control-names.rst | 8 ---------------
39 Side side left/right for 7.1 surround
54 Master
55 Master Mono
56 Hardware Master
68 Headset Mic mic part of combined headset jack - 4-pin
70 Headphone Mic mic part of either/or - 3-pin headphone or mic
79 Analog Loopback D/A -> A/D loopback
80 Digital Loopback playback -> capture loopback -
98 -----------------------
[all …]
|
| /Documentation/driver-api/usb/ |
| D | gadget.rst | 11 This document presents a Linux-USB "Gadget" kernel mode API, for use
17 - Supports USB 2.0, for high speed devices which can stream data at
20 - Handles devices with dozens of endpoints just as well as ones with
21 just two fixed-function ones. Gadget drivers can be written so
24 - Flexible enough to expose more complex USB device capabilities such
28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the
29 Linux-USB host side.
31 - Sharing data structures and API models with the Linux-USB host side
32 API. This helps the OTG support, and looks forward to more-symmetric
34 side drivers).
[all …]
|
| /Documentation/filesystems/ |
| D | ubifs-authentication.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 binary to perform a malicious action when executed [DMC-CBC-ATTACK]. Since
28 Other full disk encryption systems like dm-crypt cover all filesystem metadata,
31 time. For dm-crypt and other filesystems that build upon the Linux block IO
32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
34 These can also be combined with dm-crypt [CRYPTSETUP2].
44 ----------------
50 addition, it deals with flash-specific wear-leveling and transparent I/O error
60 +------------+ +*******+ +-----------+ +-----+
61 | | * UBIFS * | UBI-BLOCK | | ... |
[all …]
|
| D | fscrypt.rst | 2 Filesystem-level encryption (fscrypt)
11 Note: "fscrypt" in this document refers to the kernel-level portion,
14 covers the kernel-level portion. For command-line examples of how to
20 <https://source.android.com/security/encryption/file-based>`_, over
25 Unlike dm-crypt, fscrypt operates at the filesystem level rather than
28 filesystem. This is useful for multi-user systems where each user's
29 data-at-rest needs to be cryptographically isolated from the others.
34 directly into supported filesystems --- currently ext4, F2FS, UBIFS,
44 fscrypt does not support encrypting files in-place. Instead, it
54 ---------------
[all …]
|
| /Documentation/driver-api/acpi/ |
| D | linuxized-acpica.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 Linuxized ACPICA - Introduction to ACPICA Release Automation
8 :Copyright: |copy| 2013-2016, Intel Corporation
24 system (OS)-independent reference implementation of the Advanced
36 +---------------------------------------------------------+
38 | +---------------------------------------------------+ |
39 | | +------------------+ | |
41 | | +------------------+ | |
42 | | +----------------------+ | |
44 | | +----------------------+ | |
[all …]
|
| /Documentation/gpu/ |
| D | drm-uapi.rst | 9 addition, drivers export device-specific interfaces for use by userspace
10 drivers & device-aware applications through ioctls and sysfs files.
16 Cover generic ioctls and sysfs layout here. We only need high-level
22 .. kernel-doc:: drivers/gpu/drm/drm_ioctl.c
28 Primary Nodes, DRM Master and Authentication
31 .. kernel-doc:: drivers/gpu/drm/drm_auth.c
32 :doc: master and authentication
34 .. kernel-doc:: drivers/gpu/drm/drm_auth.c
37 .. kernel-doc:: include/drm/drm_auth.h
46 .. kernel-doc:: drivers/gpu/drm/drm_lease.c
[all …]
|
| /Documentation/i2c/busses/ |
| D | i2c-parport.rst | 2 Kernel driver i2c-parport
7 This is a unified driver for several i2c-over-parallel-port adapters,
11 * i2c-philips-par
12 * i2c-elv
13 * i2c-velleman
14 * video/i2c-parport
25 * (type=6) Barco LPT->DVI (K5800236) adapter
27 * (type=8) VCT-jig
42 -------------------------
44 If you want to build you own i2c-over-parallel-port adapter, here is
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | fsl,rpmsg.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shengjiu Wang <shengjiu.wang@nxp.com>
15 Linux side is a device which provides audio service by rpmsg channel.
18 Cortex-A and Cortex-M.
21 - $ref: sound-card-common.yaml#
26 - fsl,imx7ulp-rpmsg-audio
27 - fsl,imx8mn-rpmsg-audio
28 - fsl,imx8mm-rpmsg-audio
[all …]
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,sc7280-wpss-pil.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/qcom,sc7280-wpss-pil.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
19 - qcom,sc7280-wpss-pil
28 - description: Watchdog interrupt
29 - description: Fatal interrupt
30 - description: Ready interrupt
31 - description: Handover interrupt
[all …]
|
123