Searched full:cfam (Results 1 – 10 of 10) sorted by relevance
| /Documentation/devicetree/bindings/fsi/ |
| D | ibm,p9-fsi-controller.yaml | 14 located on a CFAM. Therefore this node will always be a child of an FSI CFAM
39 cfam@0,0 {
|
| D | aspeed,ast2600-fsi-master.yaml | 25 cfam-reset-gpios:
28 Output GPIO pin for CFAM reset
94 cfam-reset-gpios = <&gpio0 ASPEED_GPIO(Q, 0) GPIO_ACTIVE_LOW>;
96 cfam@0,0 {
|
| D | ibm,p9-sbefifo.yaml | 13 The SBEFIFO is an FSI CFAM engine that provides an interface to the
15 of an FSI CFAM node.
|
| D | ibm,i2cr-fsi-master.yaml | 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
|
| D | ibm,fsi2spi.yaml | 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
|
| D | fsi-controller.yaml | 14 FSI bus is connected to a CFAM (Common FRU Access Macro) which contains
39 "cfam@[0-9a-f],[0-9a-f]":
|
| D | fsi.txt | 74 cfam@1,2 {
127 /* A FSI slave (aka. CFAM) at link 0, ID 0. */
128 cfam@0,0 {
|
| D | ibm,p9-scom.yaml | 14 Interconnect Bus). This node will always be a child of an FSI CFAM node.
|
| /Documentation/devicetree/bindings/i2c/ |
| D | ibm,i2c-fsi.yaml | 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.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-fsi | 45 Provides a means of resetting the cfam that is attached to the
|