Home
last modified time | relevance | path

Searched full:fsi (Results 1 – 21 of 21) 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
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
20 * exposes an FSI bus */
[all …]
Daspeed,ast2600-fsi-master.yaml4 $id: http://devicetree.org/schemas/fsi/aspeed,ast2600-fsi-master.yaml#
7 title: Aspeed FSI master
13 The AST2600 and later contain two identical FSI masters. They share a
19 - aspeed,ast2600-fsi-master
20 - aspeed,ast2700-fsi-master
30 fsi-routing-gpios:
33 Output GPIO pin for setting the FSI mux (internal or cabled)
35 fsi-mux-gpios:
38 Input GPIO pin for detecting the desired FSI mux state
48 - aspeed,ast2600-fsi-master
[all …]
Dibm,p9-fsi-controller.yaml4 $id: http://devicetree.org/schemas/fsi/ibm,p9-fsi-controller.yaml#
7 title: IBM FSI-attached FSI Hub Controller
13 The FSI Hub Controller is an FSI controller, providing a number of FSI links,
14 located on a CFAM. Therefore this node will always be a child of an FSI CFAM
20 - ibm,p9-fsi-controller
24 - description: FSI slave address
27 - $ref: fsi-controller.yaml#
33 fsi@3400 {
34 compatible = "ibm,p9-fsi-controller";
Dibm,i2cr-fsi-master.yaml4 $id: http://devicetree.org/schemas/fsi/ibm,i2cr-fsi-master.yaml#
7 title: IBM I2C Responder virtual FSI master
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
30 - $ref: fsi-controller.yaml#
41 compatible = "ibm,i2cr-fsi-master";
Dfsi-master-gpio.txt1 Device-tree bindings for gpio-based FSI master driver
5 - compatible = "fsi-master-gpio";
6 - clock-gpios = <gpio-descriptor>; : GPIO for FSI clock
7 - data-gpios = <gpio-descriptor>; : GPIO for FSI data signal
13 functions (eg, external FSI masters)
21 fsi-master {
22 compatible = "fsi-master-gpio", "fsi-master";
Dfsi-master-ast-cf.txt1 Device-tree bindings for ColdFire offloaded gpio-based FSI master driver
6 "aspeed,ast2400-cf-fsi-master" for an AST2400 based system
8 "aspeed,ast2500-cf-fsi-master" for an AST2500 based system
10 - clock-gpios = <gpio-descriptor>; : GPIO for FSI clock
11 - data-gpios = <gpio-descriptor>; : GPIO for FSI data signal
15 functions (eg, external FSI masters)
24 fsi-master {
25 compatible = "aspeed,ast2500-cf-fsi-master", "fsi-master";
Dibm,p9-sbefifo.yaml4 $id: http://devicetree.org/schemas/fsi/ibm,p9-sbefifo.yaml#
7 title: IBM FSI-attached SBEFIFO engine
13 The SBEFIFO is an FSI CFAM engine that provides an interface to the
15 of an FSI CFAM node.
25 - description: FSI slave address
39 fsi-slave-engine@2400 {
Dibm,fsi2spi.yaml4 $id: http://devicetree.org/schemas/fsi/ibm,fsi2spi.yaml#
7 title: IBM FSI-attached SPI controllers
13 This binding describes an FSI CFAM engine called the FSI2SPI. Therefore this
14 node will always be a child of an FSI CFAM node. This FSI2SPI engine provides
24 - description: FSI slave address
35 $ref: /schemas/spi/ibm,spi-fsi.yaml
52 compatible = "ibm,spi-fsi";
Dfsi-controller.yaml4 $id: http://devicetree.org/schemas/fsi/fsi-controller.yaml#
7 title: FSI Controller Common Properties
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
36 The FSI controller cannot scan the bus during initialization.
Dibm,p9-scom.yaml4 $id: http://devicetree.org/schemas/fsi/ibm,p9-scom.yaml#
7 title: IBM FSI-attached SCOM engine
14 Interconnect Bus). This node will always be a child of an FSI CFAM node.
24 - description: FSI slave address
Dibm,p9-occ.yaml4 $id: http://devicetree.org/schemas/fsi/ibm,p9-occ.yaml#
7 title: IBM FSI-attached On-Chip Controller (OCC)
14 thermals for the system, accessed through the FSI-attached SBEFIFO
/Documentation/ABI/testing/
Dsysfs-bus-fsi1 What: /sys/bus/platform/devices/../fsi-master/fsi0/rescan
4 Contact: linux-fsi@lists.ozlabs.org
6 Initiates a FSI master scan for all connected slave devices
9 What: /sys/bus/platform/devices/../fsi-master/fsi0/break
12 Contact: linux-fsi@lists.ozlabs.org
14 Sends an FSI BREAK command on a master's communication
19 What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/term
22 Contact: linux-fsi@lists.ozlabs.org
24 Sends an FSI terminate command from the master to its
32 What: /sys/bus/platform/devices/../fsi-master/fsi0/slave@00:00/raw
[all …]
Dsysfs-driver-fsi-master-gpio1 What: /sys/bus/platform/devices/[..]/fsi-master-gpio/external_mode
6 Controls access arbitration for GPIO-based FSI master. A
8 driver performs FSI bus transactions, 1 sets external mode,
9 where the FSI bus is driven externally (for example, by
Dsysfs-bus-fsi-devices-sbefifo1 What: /sys/bus/fsi/devices/XX.XX.00:06/sbefifoX/timeout
/Documentation/devicetree/bindings/sound/
Drenesas,fsi.yaml4 $id: http://devicetree.org/schemas/sound/renesas,fsi.yaml#
7 title: Renesas FIFO-buffered Serial Interface (FSI)
50 "^fsi(a|b),spdif-connection$":
52 description: FSI is connected by S/PDIF
54 "^fsi(a|b),stream-mode-support$":
56 description: FSI supports 16bit stream mode
58 "^fsi(a|b),use-internal-clock$":
60 description: FSI uses internal clock when master mode
/Documentation/devicetree/bindings/i2c/
Dibm,i2c-fsi.yaml4 $id: http://devicetree.org/schemas/i2c/ibm,i2c-fsi.yaml#
7 title: IBM FSI-attached I2C controller
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
55 compatible = "ibm,i2c-fsi";
/Documentation/devicetree/bindings/spi/
Dibm,spi-fsi.yaml4 $id: http://devicetree.org/schemas/spi/ibm,spi-fsi.yaml#
7 title: IBM FSI-attached SPI Controller
13 A SPI controller found on IBM Power processors, accessed over FSI from a
20 - ibm,spi-fsi
36 fsi {
41 compatible = "ibm,spi-fsi";
/Documentation/hwmon/
Docc.rst23 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.
/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra234-cbb.yaml17 which include cluster fabrics BPMP, AON, PSC, SCE, RCE, DCE, FSI and
/Documentation/process/
Dmaintainer-pgp-guide.rst400 - `Nitrokey Start`_: Open hardware and Free Software, based on FSI
/Documentation/devicetree/bindings/
Dvendor-prefixes.yaml19 "^(at25|bm|devbus|dmacap|dsa|exynos|fsi[ab]|gpio-fan|gpio-key|gpio|gpmc|hdmi|i2c-gpio),.*": true