Home
last modified time | relevance | path

Searched +full:i2c +full:- +full:fsi (Results 1 – 6 of 6) sorted by relevance

/Documentation/devicetree/bindings/fsi/
Dfsi.txt1 FSI bus & engine generic device tree bindings
4 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
7 busses, which are then exposed by the device tree. For example, an FSI engine
8 that is an I2C master - the I2C bus can be described by the device tree under
11 FSI masters may require their own DT nodes (to describe the master HW itself);
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
[all …]
Dibm,i2cr-fsi-master.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/fsi/ibm,i2cr-fsi-master.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM I2C Responder virtual FSI master
10 - Eddie James <eajames@linux.ibm.com>
13 The I2C Responder (I2CR) is a an I2C device that's connected to an FSI CFAM
14 (see fsi.txt). The I2CR translates I2C bus operations to FSI CFAM reads and
15 writes or SCOM operations, thereby acting as an FSI master.
20 - ibm,i2cr-fsi-master
[all …]
Dfsi-controller.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/fsi/fsi-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: FSI Controller Common Properties
10 - Eddie James <eajames@linux.ibm.com>
13 FSI (FRU (Field Replaceable Unit) Service Interface) is a two wire bus. The
14 FSI bus is connected to a CFAM (Common FRU Access Macro) which contains
15 various engines such as I2C controllers, SPI controllers, etc.
18 "#address-cells":
[all …]
/Documentation/devicetree/bindings/i2c/
Dibm,i2c-fsi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/i2c/ibm,i2c-fsi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached I2C controller
10 - Eddie James <eajames@linux.ibm.com>
13 This I2C controller is an FSI CFAM engine, providing access to a number of
14 I2C busses. Therefore this node will always be a child of an FSI CFAM node.
19 - ibm,i2c-fsi
23 - description: FSI slave address
[all …]
/Documentation/hwmon/
Docc.rst1 Kernel driver occ-hwmon
12 -----------
14 This driver supports hardware monitoring for the On-Chip Controller (OCC)
19 The P8 version of this driver is a client driver of I2C. It may be probed
20 manually if an "ibm,p8-occ-hwmon" compatible device is found under the
21 appropriate I2C bus node in the device-tree.
23 The P9 version of this driver is a client driver of the FSI-based OCC driver.
24 It will be probed automatically by the FSI-based OCC driver.
27 -------------
29 The following attributes are supported. All attributes are read-only unless
[all …]
/Documentation/devicetree/bindings/
Dvendor-prefixes.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/vendor-prefixes.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
19 "^(at25|bm|devbus|dmacap|dsa|exynos|fsi[ab]|gpio-fan|gpio-key|gpio|gpmc|hdmi|i2c-gpio),.*": true
21 "^(pinctrl-single|#pinctrl-single|PowerPC),.*": true
22 "^(pl022|pxa-mmc|rcar_sound|rotary-encoder|s5m8767|sdhci),.*": true
23 "^(simple-audio-card|st-plgpio|st-spics|ts),.*": true
50 "^active-semi,.*":
[all …]