Home
last modified time | relevance | path

Searched refs:cable (Results 1 – 25 of 86) sorted by relevance

1234

/openbmc/u-boot/board/freescale/lx2160a/
H A DREADME90 |Connect I/O cable to IO_SLOT1(J110)
93 |Connect I/O cable to IO_SLOT2(J113)
97 |Connect I/O cable to IO_SLOT1(J110)
100 |Connect I/O cable to IO_SLOT2(J113)
104 |Connect I/O cable to IO_SLOT1(J110)
107 |Connect I/O cable to IO_SLOT2(J113)
111 |Connect I/O cable to IO_SLOT1(J110)
114 |Connect I/O cable to IO_SLOT2(J113)
118 |Connect I/O cable to IO_SLOT1(J110)
121 |Connect I/O cable to IO_SLOT2(J113)
[all …]
/openbmc/dbus-sensors/src/cable-monitor/
H A DCableConfig.cpp12 namespace cable namespace
65 for (auto cable : cables) in processConfig() local
67 std::replace(cable.begin(), cable.end(), ' ', '_'); in processConfig()
68 debug("Config: Cable {NAME}", "NAME", cable); in processConfig()
69 cablesTemp.insert(cable); in processConfig()
H A DCableConfig.hpp8 namespace cable namespace
H A Dmeson.build1 if not get_option('cable-monitor').allowed()
H A DCableEvents.hpp9 namespace cable namespace
H A DCableMonitor.cpp18 namespace cable namespace
189 cable::Monitor cableMonitor{ctx}; in main()
/openbmc/docs/designs/
H A Dcable-monitor.md27 1. Able to support runtime configuration of cable connectivity.
41 A["cable-config.json"] --> B["Cable Monitor"]
47 #### cable.conf
58 "description": "The connected cable definition.",
62 "description": "The connected cable list.",
67 "description": "The name of the cable"
79 ##### Example cablemonitor/cable-config.json
91 #### cable-monitor
93 The cable monitor is responsible for processing the cable-config.json file and
95 on expected cable connectivity and inventory item status. Additionally, it
[all …]
H A Dgpio-based-cable-presence.md9 The intent of this new daemon design is to report GPIO-based cable presence
23 1. The openbmc IPMI interface should support exposing cable presence states.
29 cable objects. We will also need to introduce a new dbus daemon to collect
60 When the cable is not properly seated, the daemon will assert on the
80 and cable1 become cable. Therefore, objects with the same name after removing
82 new SDR name is cable[0-1]. The SDR name implies that this SDR has the presence
86 if there are 20 cable indexed from 0 to 19, we shall see two SDRs. One is
87 cable0-13. One is cable[14-19]. If the object path is not indexed by the user,
101 example, `/xyz/openbmc_project/inventory/item/cable`. The group handler will not
121 GetSubTree method to list all the instances under the cable interface. In
[all …]
/openbmc/openbmc/meta-facebook/meta-catalina/recipes-phosphor/sensors/
H A Dphosphor-virtual-sensor_%.bbappend14 file://no-cable-tsense.json \
19 ${datadir}/phosphor-virtual-sensor/no-cable-tsense.json \
28 …install -m 0644 -D ${UNPACKDIR}/no-cable-tsense.json ${D}${datadir}/phosphor-virtual-sensor/no-cab…
/openbmc/openbmc/meta-facebook/meta-santabarbara/recipes-phosphor/sensors/
H A Ddbus-sensors_%.bbappend12 SRC_URI += "${@bb.utils.contains('PACKAGECONFIG', 'cablemonitor', ' file://cable-config.json', '', …
17 install -m 0755 ${UNPACKDIR}/cable-config.json ${D}/var/lib/cablemonitor/cable-config.json
/openbmc/openbmc/meta-facebook/meta-ventura/recipes-phosphor/sensors/
H A Ddbus-sensors_%.bbappend22 SRC_URI += "${@bb.utils.contains('PACKAGECONFIG', 'cablemonitor', ' file://cable-config.json', '', …
38 install -m 0755 ${UNPACKDIR}/cable-config.json ${D}/var/lib/cablemonitor/cable-config.json
/openbmc/u-boot/board/freescale/t4qds/
H A DREADME84 four Lanes A/B/C/D to a SFP+ cages, which to house fiber cable or
85 direct attach cable(copper), the copper cable is used to emulate
87 So, for XFI usage, there are two scenarios, one will use fiber cable,
88 another will use copper cable. An hwconfig env "fsl_10gkr_copper" is
89 introduced to indicate a XFI port will use copper cable, and U-Boot
94 "fsl_10gkr_copper", it will use copper cable, otherwise, fiber cable
97 hwconfig, then both four XFI ports will use copper cable.
99 XFI ports will use copper cable, the other two XFI ports will use fiber
100 cable.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/ifplugd/
H A Difplugd_0.28.bb2 when a cable is plugged in and automatically unconfigure it if the cable is pulled."
/openbmc/pldm/host-bmc/dbus/
H A Dcustom_dbus.cpp103 if (!cable.contains(path)) in implementCableInterface()
105 cable.emplace(path, std::make_unique<Cable>( in implementCableInterface()
113 if (cable.contains(path)) in setCableAttributes()
115 cable.at(path)->length(length); in setCableAttributes()
116 cable.at(path)->cableTypeDescription(cableDescription); in setCableAttributes()
/openbmc/u-boot/board/freescale/t208xqds/
H A DREADME90 a on-board SFP+ cages, which to house optical module (fiber cable) or
91 direct attach cable(copper), the copper cable is used to emulate
93 So, for XFI usage, there are two scenarios, one will use fiber cable,
94 another will use copper cable. An hwconfig env "fsl_10gkr_copper" is
95 introduced to indicate a XFI port will use copper cable, and U-Boot
100 "fsl_10gkr_copper", it will use copper cable, otherwise, fiber cable
103 hwconfig, then both four XFI ports will use copper cable.
105 XFI ports will use copper cable, the other two XFI ports will use fiber
106 cable.
/openbmc/openbmc/meta-facebook/meta-ventura/recipes-phosphor/sensors/dbus-sensors/
H A Dcritical-leak-handler29 /xyz/openbmc_project/inventory/system/cable/ReturnValve_1_Port \
32 /xyz/openbmc_project/inventory/system/cable/SupplyValve_1_Port \
/openbmc/openbmc/meta-quanta/meta-gbs/recipes-phosphor/gpio/phosphor-gpio-monitor/obmc/gpio/
H A Dgpios-3.conf3 INVENTORY=/system/chassis/cable/ss_cab3_prsnt
H A Dgpios-1.conf3 INVENTORY=/system/chassis/cable/ss_cab1_prsnt
H A Dgpios-5.conf3 INVENTORY=/system/chassis/cable/fanbd_cab_prsnt
H A Dgpios-4.conf3 INVENTORY=/system/chassis/cable/hsbp_cab_prsnt
H A Dgpios-6.conf3 INVENTORY=/system/chassis/cable/bp12v_cab_prsnt
H A Dgpios-2.conf3 INVENTORY=/system/chassis/cable/ss_cab2_prsnt
H A Dgpios-0.conf3 INVENTORY=/system/chassis/cable/ss_cab0_prsnt
/openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/
H A Dparselogs-ignores-qemuppc.txt3 host side 80-wire cable detection failed, limiting max speed
/openbmc/docs/designs/inventory/
H A Dgpio-based-hardware-inventory.md11 … gpio based cable presence detection](https://github.com/openbmc/docs/blob/46902afd6ebd20d1148379d…
25 The existing design for the gpio based cable presence is partially implemented
28 …om/openbmc/docs/blob/879601d92becfa1dbc082f487abfb5e0151a5091/designs/gpio-based-cable-presence.md)
101 - e.g. cable
405 board/daughter board/cable through an additional variable besides "Name" that
414 the external interfaces can expose a cable inventory based on the
415 …[cable dbus interface](https://github.com/openbmc/phosphor-dbus-interfaces/commit/3c5b76491afb8401…
418 - Comparing to Chu Lin's design, this design does not directly provide a cable
420 expose a cable inventory item.

1234