| /openbmc/entity-manager/docs/ |
| H A D | blacklist_configuration.md | 3 The blacklist.json in package directory can determine i2c buses and addresses
8 ## For buses
10 Put in numbers of buses. For example:
14 "buses": [1, 3, 5]
18 Note that "buses" should be an array of unsigned integer.
26 "buses": [
46 "buses": [
|
| /openbmc/u-boot/drivers/i2c/muxes/ |
| H A D | Kconfig | 5 This enables I2C buses to be multiplexed, so that you can select
6 one of several buses using some sort of control mechanism. The
14 This enables I2C buses to be multiplexed, so that you can select
15 one of several buses using some sort of control mechanism. The
|
| /openbmc/u-boot/doc/ |
| H A D | README.bitbangMII | 2 support an arbitrary number of mii buses. This feature is useful when your
3 board uses different mii buses for different phys and all (or a part) of these
4 buses are implemented via bit-banging mode.
29 the bb_miiphy_buses_num variable with the number of mii buses.
|
| /openbmc/qemu/docs/system/ |
| H A D | device-emulation.rst | 29 Device Buses
33 machine model you choose (``-M foo``) a number of buses will have been
42 additional buses to the system that other devices can be attached to.
|
| /openbmc/openbmc/meta-ingrasys/meta-zaius/recipes-phosphor/chassis/avsbus-control/ |
| H A D | zaius_avsbus.sh | 9 buses="$cpu0_i2c_bus $cpu1_i2c_bus"
40 for bus in $buses
|
| /openbmc/u-boot/doc/device-tree-bindings/net/ |
| H A D | fsl-tsec-phy.txt | 48 This PHY is accessed through the local MDIO bus. These buses are defined
49 similarly to the mdio buses. The TBI PHYs underneath them are similar to
|
| /openbmc/entity-manager/ |
| H A D | blacklist.json | 2 "buses": [] array
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/entity-manager/ |
| H A D | blocklist.json | 2 "buses": [] array
|
| /openbmc/openbmc/meta-fii/meta-kudo/recipes-phosphor/configuration/entity-manager/ |
| H A D | blacklist.json | 2 "buses": [1, 12] array
|
| /openbmc/openbmc/meta-ufispace/meta-ncplite/recipes-phosphor/configuration/entity-manager/ |
| H A D | blacklist.json | 2 "buses": [0, 1, 2, 8, 10] array
|
| /openbmc/qemu/docs/ |
| H A D | pcie_pci_bridge.txt | 29 any device plugged in, has no free buses reserved to provide any of them
32 To solve this problem we reserve additional buses on a firmware level.
49 uint32_t bus_res; Minimum number of buses to reserve
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/recipes-phosphor/configuration/entity-manager/ |
| H A D | blocklist.json | 2 "buses": [0, 1, 2, 4, 5, 6, 7, 8] array
|
| /openbmc/openbmc/meta-amd/meta-daytonax/recipes-phosphor/configuration/entity-manager/ |
| H A D | blocklist.json | 2 "buses": [0, 1, 2, 4, 5, 6, 7, 8, 12] array
|
| /openbmc/openbmc/meta-yadro/meta-vegman/recipes-phosphor/configuration/entity-manager/ |
| H A D | blacklist.json | 2 "buses": [0, 3, 4, 5, 6, 8, 9, 10, 12] array
|
| /openbmc/openbmc/meta-nuvoton/meta-evb-npcm845/recipes-phosphor/configuration/entity-manager/ |
| H A D | blacklist.json | 2 "buses": [0,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26] array
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/entity-manager/ibm-power9-cpu/ |
| H A D | blocklist.json | 2 …"buses": [100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 200, 201, 202… array
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/configuration/entity-manager/ibm-power10-cpu/ |
| H A D | blocklist.json | 2 …"buses": [100, 101, 110, 111, 112, 113, 114, 115, 202, 203, 210, 211, 214, 215, 216, 217, 300, 301… array
|
| /openbmc/openbmc/meta-facebook/meta-minerva/recipes-phosphor/configuration/entity-manager/ |
| H A D | blacklist.json | 2 "buses": [ array
|
| /openbmc/openbmc/meta-ampere/meta-mitchell/recipes-phosphor/configuration/entity-manager/ |
| H A D | blacklist.json | 2 "buses":[ array
|
| /openbmc/qemu/hw/pci/ |
| H A D | meson.build | 15 # allow plugging PCIe devices into PCI buses, include them even if
|
| /openbmc/u-boot/drivers/misc/ |
| H A D | gdsys_soc.h | 15 * To access their register maps, devices on gdsys soc buses usually have
|
| /openbmc/qemu/docs/devel/ |
| H A D | kconfig.rst | 16 Each QEMU target enables a subset of the boards, devices and buses that
141 **subsystems**, of which **buses** are a special case
153 subsystems or buses. For example, ``AUX`` (the DisplayPort auxiliary
172 have no ``depends on`` directive. Devices also *select* the buses
|
| /openbmc/openbmc/meta-ampere/meta-jade/recipes-phosphor/configuration/entity-manager/ |
| H A D | blacklist.json | 2 "buses": [ array
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | can.rst | 4 emulated CAN controller chips together by one or multiple CAN buses
5 (the controller device "canbus" parameter). The individual buses
9 The concept of buses is generic and different CAN controllers
|
| /openbmc/entity-manager/src/fru_device/ |
| H A D | fru_device.cpp | 172 return; // the mux buses are random, no need to publish in makeProbeInterface()
629 // It's expected to have at least one field, "buses" that is an array of the in loadBlocklist()
630 // buses by integer. Allow for future options to exclude further aspects, in loadBlocklist()
638 // If buses field is missing, that's fine. in loadBlocklist()
639 if (data.count("buses") == 1) in loadBlocklist()
641 // Parse the buses array after a little validation. in loadBlocklist()
642 auto buses = data.at("buses"); in loadBlocklist() local
643 if (buses.type() != nlohmann::json::value_t::array) in loadBlocklist()
645 // Buses field present but invalid, therefore this is an error. in loadBlocklist()
646 std::cerr << "Invalid contents for blocklist buses field\n"; in loadBlocklist()
[all …]
|