Home
last modified time | relevance | path

Searched +full:i2c +full:- +full:slave +full:- +full:addr (Results 1 – 9 of 9) sorted by relevance

/Documentation/devicetree/bindings/soc/tegra/
Dnvidia,nvec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
26 - description: divider clock
27 - description: fast clock
29 clock-names:
32 - const: div-clk
33 - const: fast-clk
[all …]
/Documentation/i2c/
Dsmbus-protocol.rst11 which is a subset from the I2C protocol. Fortunately, many devices use
14 If you write a driver for some I2C device, please try to use the SMBus
16 I2C protocol). This makes it possible to use the device driver on both
17 SMBus adapters and I2C adapters (the SMBus command set is automatically
18 translated to I2C on I2C adapters, but plain I2C commands can not be
29 the corresponding functionality flag to ensure that the underlying I2C
31 Documentation/i2c/functionality.rst for the details.
44 Addr (7 bits) I2C 7 bit address. Note that this can be expanded to
45 get a 10 bit I2C address.
52 [..] Data sent by I2C device, as opposed to data sent by the host
[all …]
Ddev-interface.rst2 Implementing I2C device drivers in userspace
5 Usually, I2C devices are controlled by a kernel driver. But it is also
7 the /dev interface. You need to load module i2c-dev for this.
9 Each registered I2C adapter gets a number, counting from 0. You can
10 examine /sys/class/i2c-dev/ to see what number corresponds to which adapter.
11 Alternatively, you can run "i2cdetect -l" to obtain a formatted list of all
12 I2C adapters present on your system at a given time. i2cdetect is part of
13 the i2c-tools package.
15 I2C device files are character device files with major device number 89
17 explained above. They should be called "i2c-%d" (i2c-0, i2c-1, ...,
[all …]
Dwriting-clients.rst2 Implementing I2C device drivers
5 This is a small guide for those who want to write kernel drivers for I2C
6 or SMBus devices, using Linux as the protocol host/master (not slave).
19 it for non-exported symbols too. We will use the prefix ``foo_`` in this
28 routines, and should be zero-initialized except for fields with data you
29 provide. A client structure holds device-specific information like the
30 driver model device node, and its I2C address.
40 MODULE_DEVICE_TABLE(i2c, foo_idtable);
62 All other fields are for call-back functions which will be explained
70 structure at all. You should use this to keep device-specific data.
[all …]
/Documentation/devicetree/bindings/fsi/
Dfsi.txt4 The FSI bus is probe-able, so the OS is able to enumerate FSI slaves, and
6 nodes to probed engines. This allows for fsi engines to expose non-probeable
8 that is an I2C master - the I2C bus can be described by the device tree under
13 the fsi-master-* binding specifications.
16 represent the FSI slaves and their slave engines. As a basic outline:
18 fsi-master {
19 /* top-level of FSI bus topology, bound to an FSI master driver and
22 fsi-slave@<link,id> {
23 /* this node defines the FSI slave device, and is handled
26 fsi-slave-engine@<addr> {
[all …]
/Documentation/devicetree/bindings/mfd/
D88pm860x.txt4 - compatible : "marvell,88pm860x"
5 - reg : the I2C slave address for the 88pm860x chip
6 - interrupts : IRQ line for the 88pm860x chip
7 - interrupt-controller: describes the 88pm860x as an interrupt controller (has its own domain)
8 - #interrupt-cells : should be 1.
9 - The cell is the 88pm860x local IRQ number
12 - marvell,88pm860x-irq-read-clr: inicates whether interrupt status is cleared by read
13 - marvell,88pm860x-slave-addr: 88pm860x are two chips solution. <reg> stores the I2C address
14 of one chip, and this property stores the I2C address of
17 88pm860x consists of a large and varied group of sub-devices:
[all …]
/Documentation/devicetree/bindings/i2c/
Dsamsung,s3c2410-i2c.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/i2c/samsung,s3c2410-i2c.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung S3C/S5P/Exynos SoC I2C Controller
10 - Krzysztof Kozlowski <krzk@kernel.org>
15 - enum:
16 - samsung,s3c2410-i2c
17 - samsung,s3c2440-i2c
18 # For s3c2440-like I2C used inside HDMIPHY block found on several SoCs:
[all …]
/Documentation/devicetree/bindings/sound/
Dtas2552.txt1 Texas Instruments - tas2552 Codec module
3 The tas2552 serial control bus communicates through I2C protocols
6 - compatible - One of:
7 "ti,tas2552" - TAS2552
8 - reg - I2C slave address: it can be 0x40 if ADDR pin is 0
9 or 0x41 if ADDR pin is 1.
10 - supply-*: Required supply regulators are:
16 - enable-gpio - gpio pin to enable/disable the device
21 For system integration the dt-bindings/sound/tas2552.h header file provides
29 vbat-supply = <&reg_vbat>;
[all …]
/Documentation/driver-api/
Dipmi.rst12 standardized database for field-replaceable units (FRUs) and a watchdog
25 -------------
32 No matter what, you must pick 'IPMI top-level message handler' to use
35 The message handler does not provide any user-level interfaces.
45 for direct I2C access to the IPMI management controller. Some boards
50 these enabled and let the drivers auto-detect what is present.
61 "The SMBus Driver" on how to hand-configure your system.
65 the kernel, then via a kernel command-line option you can have the
74 'IPMI Poweroff' to do this. The driver will auto-detect if the system
89 ------------
[all …]