/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/Callout/ |
H A D | README.md | 7 would be `xyz.openbmc_project.Error.Callout.IIC`, to indicate an IIC callout. 10 is familiar to them, such as a sysfs entry, or an IIC address. It would be up to 18 xyz.openbmc_project.Error.Callout.IIC) : 21 - name: IIC 29 An application wanting to add an IIC callout will have to provide values for the 31 figure out that this is in fact an IIC callout. 34 `xyz.openbmc_project.Error.Foo` may want to add an IIC callout. This is 41 - xyz.openbmc_project.Error.Callout.IIC 45 include Callout.IIC's as well, so an application wanting to add an IIC callout 46 will have to provide values for Foo and IIC metadata. Like mentioned before, due [all …]
|
/openbmc/openpower-host-ipmi-oem/ |
H A D | elog-errors.hpp | 39 struct IIC; 294 struct IIC struct 312 using IIC = phosphor::logging::xyz::openbmc_project::common::callout::IIC; typedef 321 sdbusplus::error::xyz::openbmc_project::common::callout::IIC> 323 using type = phosphor::logging::xyz::openbmc_project::common::callout::IIC;
|
/openbmc/entity-manager/docs/ |
H A D | address_size_detection_modes.md | 34 1-byte read operation. The proposed solution fully complies with IIC standard 35 and should be applicable to any IIC EEPROM manufacturer. 69 is the ambiguity (not standard defined) in the IIC specification. 71 In [IIC specification:](https://www.nxp.com/docs/en/user-guide/UM10204.pdf) 88 is the address pointer, as being the first data byte in IIC communication.
|
/openbmc/linux/arch/sh/kernel/cpu/sh3/ |
H A D | setup-sh7720.c | 230 PINT07, PINT815, TPU, IIC, enumerator 259 INTC_VECT(TPU, 0xde0), INTC_VECT(IIC, 0xe00), 274 { 0xA4080004UL, 0, 16, 4, /* IPRH */ { PINT07, PINT815, TPU, IIC } },
|
/openbmc/linux/arch/sh/kernel/cpu/sh4a/ |
H A D | setup-shx3.c | 182 IIC, VIN0, VIN1, VCORE0, ATAPI, enumerator 220 INTC_VECT(IIC, 0xae0), 266 { FE1, FE0, 0, ATAPI, VCORE0, VIN1, VIN0, IIC, 301 VIN1, VIN0, IIC, DU} },
|
/openbmc/witherspoon-pfault-analysis/ |
H A D | elog-errors.hpp | 79 struct IIC; 508 struct IIC struct 526 using IIC = phosphor::logging::xyz::openbmc_project::common::callout::IIC; argument 535 sdbusplus::error::xyz::openbmc_project::common::callout::IIC> 537 using type = phosphor::logging::xyz::openbmc_project::common::callout::IIC;
|
/openbmc/phosphor-power/ |
H A D | elog-errors.hpp | 227 struct IIC; 1803 struct IIC struct 1821 using IIC = phosphor::logging::xyz::openbmc_project::common::callout::IIC; argument 1830 sdbusplus::error::xyz::openbmc_project::common::callout::IIC> 1832 using type = phosphor::logging::xyz::openbmc_project::common::callout::IIC;
|
/openbmc/linux/Documentation/i2c/ |
H A D | summary.rst | 12 e.g. TWI (Two Wire Interface), IIC.
|
/openbmc/linux/arch/powerpc/boot/dts/ |
H A D | acadia.dts | 112 IIC: i2c@ef600500 { label
|
H A D | hotfoot.dts | 119 IIC: i2c@ef600500 { label
|
/openbmc/u-boot/drivers/i2c/ |
H A D | Kconfig | 367 bool "Renesas RCar Gen3 IIC driver" 370 Support for Renesas RCar Gen3 IIC controller.
|
/openbmc/linux/drivers/i2c/busses/ |
H A D | Kconfig | 701 Say Y here if you want to use IIC peripheral found on 722 Say Y here if you want to use the IIC bus controller on 732 Say Y here if you want to use the Low Power IIC bus controller 742 Say Y here if you want to use the IIC bus controller on
|