Home
last modified time | relevance | path

Searched +full:i2c +full:- +full:gate (Results 1 – 14 of 14) sorted by relevance

/Documentation/devicetree/bindings/i2c/
Di2c-gate.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-gate.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Common i2c gate properties
10 - Peter Rosin <peda@axentia.se>
13 An i2c gate is useful to e.g. reduce the digital noise for RF tuners connected
14 to the i2c bus. Gates are similar to arbitrators in that you need to perform
15 some kind of operation to access the i2c bus past the arbitrator/gate, but
20 - $ref: /schemas/i2c/i2c-controller.yaml
[all …]
/Documentation/devicetree/bindings/iio/imu/
Dinvensense,mpu6050.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: InvenSense MPU-6050 Six-Axis (Gyro + Accelerometer) MEMS MotionTracking Device
10 - Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
13 These devices support both I2C and SPI bus interfaces.
18 - enum:
19 - invensense,iam20680
20 - invensense,icm20608
21 - invensense,icm20609
[all …]
/Documentation/devicetree/bindings/iio/gyroscope/
Dinvensense,mpu3050.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Invensense MPU-3050 Gyroscope
10 - Linus Walleij <linus.walleij@linaro.org>
19 vdd-supply: true
21 vlogic-supply: true
28 mount-matrix: true
30 i2c-gate:
31 $ref: /schemas/i2c/i2c-controller.yaml
[all …]
/Documentation/devicetree/bindings/media/i2c/
Dmaxim,max96717.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/media/i2c/maxim,max96717.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: MAX96717 CSI-2 to GMSL2 Serializer
11 - Julien Massot <julien.massot@collabora.com>
14 The MAX96717 serializer converts MIPI CSI-2 D-PHY formatted input
16 simultaneously transmit bidirectional control-channel data while forward
18 remotely located deserializer using industry-standard coax or STP
32 - const: maxim,max96717f
[all …]
Dmaxim,max96714.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/media/i2c/maxim,max96714.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Maxim MAX96714 GMSL2 to CSI-2 Deserializer
11 - Julien Massot <julien.massot@collabora.com>
15 CSI-2 D-PHY formatted output. The device allows the GMSL2 link to
16 simultaneously transmit bidirectional control-channel data while forward
18 remotely located serializer using industry-standard coax or STP
30 - const: maxim,max96714f
[all …]
/Documentation/driver-api/nfc/
Dnfc-hci.rst5 - Author: Eric Lapuyade, Samuel Ortiz
6 - Contact: eric.lapuyade@intel.com, samuel.ortiz@intel.com
9 -------
12 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core
17 ---
30 - one for executing commands : nfc_hci_msg_tx_work(). Only one command
32 - one for dispatching received events and commands : nfc_hci_msg_rx_work().
35 --------------------------
41 In case the chip supports pre-opened gates and pseudo-static pipes, the driver
45 -------------------
[all …]
/Documentation/devicetree/bindings/display/imx/
Dldb.txt1 Device-Tree bindings for LVDS Display Bridge (ldb)
6 The LVDS Display Bridge device tree node contains up to two lvds-channel
10 - #address-cells : should be <1>
11 - #size-cells : should be <0>
12 - compatible : should be "fsl,imx53-ldb" or "fsl,imx6q-ldb".
16 - gpr : should be <&gpr> on i.MX53 and i.MX6q.
17 The phandle points to the iomuxc-gpr region containing the LVDS
19 - clocks, clock-names : phandles to the LDB divider and selector clocks and to
21 Documentation/devicetree/bindings/clock/clock-bindings.txt
23 "di0_pll" - LDB LVDS channel 0 mux
[all …]
/Documentation/i2c/
Di2c-topology.rst2 I2C muxes and complex topologies
5 There are a couple of reasons for building more complex I2C topologies
6 than a straight-forward I2C bus with one adapter and one or more devices.
16 from the I2C bus, at least most of the time, and sits behind a gate
19 Several types of hardware components such as I2C muxes, I2C gates and I2C
22 These components are represented as I2C adapter trees by Linux, where
25 I2C transfers, and all adapters with a parent are part of an "i2c-mux"
26 object (quoted, since it can also be an arbitrator or a gate).
29 an I2C transfer on one of its child adapters. The mux driver can
31 bus master or open a gate. The mux driver has two operations for this,
[all …]
/Documentation/hwmon/
Dltc4282.rst1 .. SPDX-License-Identifier: GPL-2.0-only
12 Addresses scanned: - I2C 0x40 - 0x5A (7-bit)
13 Addresses scanned: - I2C 0x80 - 0xB4 with a step of 2 (8-bit)
17 https://www.analog.com/media/en/technical-documentation/data-sheets/ltc4282.pdf
25 from a live backplane. Using one or more external N-channel pass transistors,
27 I2C interface and onboard ADC allows for monitoring of board current, voltage,
29 limiting and supply monitoring for applications from 2.9V to 33V. Dual 12V gate
31 parallel MOSFETs or support a 2-stage start-up that first charges the load
32 capacitance followed by enabling a low on-resistance path to the load. The
35 and power supplies must safely operate. Non-volatile configuration allows for
[all …]
/Documentation/driver-api/gpio/
Ddrivers-on-gpio.rst6 the right in-kernel and userspace APIs/ABIs for the job, and that these
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
15 (and that LED may in turn use the leds-gpio as per above).
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from
31 off/on, for an actual PWM waveform, see pwm-gpio below.)
33 - pwm-gpio: drivers/pwm/pwm-gpio.c is used to toggle a GPIO with a high
[all …]
/Documentation/devicetree/bindings/mfd/
Drohm,bd71815-pmic.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71815-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <mazziesaccount@gmail.com>
13 BD71815AGW is a single-chip power management ICs for battery-powered
15 for LED and a 500 mA single-cell linear charger. Also included is a Coulomb
16 counter, a real-time clock (RTC), and a 32.768 kHz clock gate and two GPOs.
24 I2C slave address.
30 gpio-controller: true
[all …]
Drohm,bd71828-pmic.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71828-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <mazziesaccount@gmail.com>
13 BD71828GW is a single-chip power management IC for battery-powered portable
15 single-cell linear charger. Also included is a Coulomb counter, a real-time
16 clock (RTC), and a 32.768 kHz clock gate.
21 - const: rohm,bd71828
23 - items:
[all …]
/Documentation/devicetree/bindings/soc/tegra/
Dnvidia,tegra20-pmc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/tegra/nvidia,tegra20-pmc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jonathan Hunter <jonathanh@nvidia.com>
16 - nvidia,tegra20-pmc
17 - nvidia,tegra30-pmc
18 - nvidia,tegra114-pmc
19 - nvidia,tegra124-pmc
[all …]
/Documentation/driver-api/media/
Ddtv-frontend.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------------
9 The Digital TV Frontend kABI defines a driver-internal interface for
10 registering low-level, hardware specific driver to a hardware independent
29 .name = "foo DVB-T/T2/C driver",
70 .name = "Bar DVB-S/S2 demodulator",
91 /* Satellite-specific */
100 #) For satellite digital TV standards (DVB-S, DVB-S2, ISDB-S), the
106 allows controlling an I2C gate (either directly of via some GPIO pin),
107 in order to remove the tuner from the I2C bus after a channel is
[all …]