Searched refs:FSI (Results 1 – 19 of 19) sorted by relevance
3 # FSI subsystem6 menuconfig FSI config7 tristate "FSI support"11 FSI - the FRU Support Interface - is a simple bus for low-level14 if FSI20 This option causes char devices created for FSI devices to be32 tristate "GPIO-based FSI master"36 This option enables a FSI master driver using GPIO lines.39 tristate "FSI hub master"41 This option enables a FSI hub master driver. Hub is a type of FSI[all …]
1 FSI bus & engine generic device tree bindings4 The FSI bus is probe-able, so the OS is able to enumerate FSI slaves, and7 busses, which are then exposed by the device tree. For example, an FSI engine11 FSI masters may require their own DT nodes (to describe the master HW itself);16 represent the FSI slaves and their slave engines. As a basic outline:19 /* top-level of FSI bus topology, bound to an FSI master driver and20 * exposes an FSI bus */23 /* this node defines the FSI slave device, and is handled24 * entirely with FSI core code */41 adding subordinate device tree nodes as children of FSI engines.[all …]
1 Device-tree bindings for FSI-attached POWER9/POWER10 On-Chip Controller (OCC)4 This is the binding for the P9 or P10 On-Chip Controller accessed over FSI from5 a service processor. See fsi.txt for details on bindings for FSI slave and CFAM6 nodes. The OCC is not an FSI slave device itself, rather it is accessed
1 Device-tree bindings for gpio-based FSI master driver6 - clock-gpios = <gpio-descriptor>; : GPIO for FSI clock7 - data-gpios = <gpio-descriptor>; : GPIO for FSI data signal13 functions (eg, external FSI masters)
1 Device-tree bindings for AST2600 FSI master4 The AST2600 contains two identical FSI masters. They share a clock and have a18 - fsi-routing-gpios: GPIO for setting the FSI mux (internal or cabled)19 - fsi-mux-gpios: GPIO for detecting the desired FSI mux state
1 Device-tree bindings for ColdFire offloaded gpio-based FSI master driver10 - clock-gpios = <gpio-descriptor>; : GPIO for FSI clock11 - data-gpios = <gpio-descriptor>; : GPIO for FSI data signal15 functions (eg, external FSI masters)
6 Initiates a FSI master scan for all connected slave devices14 Sends an FSI BREAK command on a master's communication24 Sends an FSI terminate command from the master to its38 specified FSI bus address.46 FSI device.
6 Controls access arbitration for GPIO-based FSI master. A8 driver performs FSI bus transactions, 1 sets external mode,9 where the FSI bus is driven externally (for example, by
1 Device-tree bindings for FSI-attached I2C master and busses6 - reg = < address size >; : The FSI CFAM address and address
25 tristate "SH4 FSI support"29 This option enables FSI sound support
29 established through SBE fifo on an FSI bus.
93 depends on FSI
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.
882 FSI, enumerator974 INTC_VECT(FSI, 0xF80),1041 0, 0, SCIFA5, FSI } },1070 { 0xa4080024, 0, 16, 4, /* IPRJ */ { CEU1, ETHI, FSI, SDHI1 } },
154 /* 2nd level UICs for FSI */
1460 tristate "FSI I2C driver"1461 depends on FSI1463 Driver for FSI bus attached I2C masters. These are I2C masters that1464 are connected to the system over an FSI bus, instead of the more
373 tristate "FSI SPI driver"374 depends on FSI376 This enables support for the driver for FSI bus attached SPI
400 - `Nitrokey Start`_: Open hardware and Free Software, based on FSI
8501 FSI SUBSYSTEM8514 FSI-ATTACHED I2C DRIVER8522 FSI-ATTACHED SPI DRIVER
