Searched full:i2cr (Results 1 – 12 of 12) sorted by relevance
/linux/drivers/fsi/ |
H A D | fsi-master-i2cr.c | 11 #include "fsi-master-i2cr.h" 137 int fsi_master_i2cr_read(struct fsi_master_i2cr *i2cr, u32 addr, u64 *data) in fsi_master_i2cr_read() argument 142 mutex_lock(&i2cr->lock); in fsi_master_i2cr_read() 144 ret = i2cr_transfer(i2cr->client, command, data); in fsi_master_i2cr_read() 148 ret = i2cr_check_status(i2cr->client); in fsi_master_i2cr_read() 152 trace_i2cr_read(i2cr->client, command, data); in fsi_master_i2cr_read() 155 mutex_unlock(&i2cr->lock); in fsi_master_i2cr_read() 160 int fsi_master_i2cr_write(struct fsi_master_i2cr *i2cr, u32 addr, u64 data) in fsi_master_i2cr_write() argument 168 mutex_lock(&i2cr->lock); in fsi_master_i2cr_write() 170 ret = i2c_master_send(i2cr->client, (const char *)buf, sizeof(buf)); in fsi_master_i2cr_write() [all …]
|
H A D | i2cr-scom.c | 11 #include "fsi-master-i2cr.h" 17 struct fsi_master_i2cr *i2cr; member 44 ret = fsi_master_i2cr_read(scom->i2cr, (u32)*offset, &data); in i2cr_scom_read() 69 ret = fsi_master_i2cr_write(scom->i2cr, (u32)*offset, data); in i2cr_scom_write() 98 scom->i2cr = to_fsi_master_i2cr(fsi_dev->slave->master); in i2cr_scom_probe() 129 { .compatible = "ibm,i2cr-scom" },
|
H A D | Kconfig | 70 behind an IBM I2C Responder (I2CR) chip. The I2CR is an I2C device 102 I2CR has the capability to directly perform SCOM operations instead
|
H A D | Makefile | 7 obj-$(CONFIG_FSI_MASTER_I2CR) += fsi-master-i2cr.o 12 obj-$(CONFIG_I2CR_SCOM) += i2cr-scom.o
|
H A D | fsi-master-i2cr.h | 22 int fsi_master_i2cr_read(struct fsi_master_i2cr *i2cr, u32 addr, u64 *data); 23 int fsi_master_i2cr_write(struct fsi_master_i2cr *i2cr, u32 addr, u64 data);
|
/linux/arch/arm/boot/dts/aspeed/ |
H A D | ibm-power10-quad.dtsi | 7 i2cr@20 { 8 compatible = "ibm,i2cr-fsi-master"; 20 compatible = "ibm,i2cr-scom"; 35 i2cr@20 { 36 compatible = "ibm,i2cr-fsi-master"; 48 compatible = "ibm,i2cr-scom"; 63 i2cr@20 { 64 compatible = "ibm,i2cr-fsi-master"; 76 compatible = "ibm,i2cr-scom"; 91 i2cr@20 { [all …]
|
H A D | ibm-power11-quad.dtsi | 154 compatible = "ibm,i2cr-fsi-master"; 166 compatible = "ibm,i2cr-scom"; 184 compatible = "ibm,i2cr-fsi-master"; 196 compatible = "ibm,i2cr-scom"; 214 compatible = "ibm,i2cr-fsi-master"; 226 compatible = "ibm,i2cr-scom"; 244 compatible = "ibm,i2cr-fsi-master"; 256 compatible = "ibm,i2cr-scom"; 274 compatible = "ibm,i2cr-fsi-master"; 286 compatible = "ibm,i2cr-scom"; [all …]
|
H A D | aspeed-bmc-ibm-everest.dts | 2525 i2cr@20 { 2526 compatible = "ibm,i2cr-fsi-master"; 2538 compatible = "ibm,i2cr-scom"; 2557 i2cr@20 { 2558 compatible = "ibm,i2cr-fsi-master"; 2570 compatible = "ibm,i2cr-scom"; 2589 i2cr@20 { 2590 compatible = "ibm,i2cr-fsi-master"; 2602 compatible = "ibm,i2cr-scom"; 2621 i2cr@20 { [all …]
|
H A D | aspeed-bmc-ibm-fuji.dts | 2492 compatible = "ibm,i2cr-fsi-master"; 2504 compatible = "ibm,i2cr-scom"; 2522 compatible = "ibm,i2cr-fsi-master"; 2534 compatible = "ibm,i2cr-scom"; 2552 compatible = "ibm,i2cr-fsi-master"; 2564 compatible = "ibm,i2cr-scom"; 2582 compatible = "ibm,i2cr-fsi-master"; 2594 compatible = "ibm,i2cr-scom"; 2612 compatible = "ibm,i2cr-fsi-master"; 2624 compatible = "ibm,i2cr-scom"; [all …]
|
/linux/Documentation/devicetree/bindings/fsi/ |
H A D | ibm,i2cr-fsi-master.yaml | 4 $id: http://devicetree.org/schemas/fsi/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 20 - ibm,i2cr-fsi-master 40 i2cr@20 { 41 compatible = "ibm,i2cr-fsi-master";
|
H A D | ibm,p9-scom.yaml | 20 - ibm,i2cr-scom
|
/linux/drivers/i2c/busses/ |
H A D | i2c-imx.c | 109 * 2) I2CR: I2C module enable operation also differ between SoCs:
|