| /openbmc/u-boot/drivers/led/ |
| H A D | Kconfig | 111 CONFIG_LED_STATUS_BIT is passed into the __led_* functions to identify
146 identify which LED is being acted on. As such, the chosen value must
181 identify which LED is being acted on. As such, the chosen value must
216 identify which LED is being acted on. As such, the chosen value must
251 identify which LED is being acted on. As such, the chosen value must
286 identify which LED is being acted on. As such, the chosen value must
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-maintainer-entry-profile.rst | 60 Reviewers should identify themselves with an ``R:`` entry in the kernel
68 The testing lead should identify themselves with an ``M:`` entry in
72 enough detail to identify the person to whom the report should be
75 The bug triagers should identify themselves with a ``B:`` entry in
86 The release manager should identify themselves with an ``M:`` entry in
99 The maintainer for a given LTS release should identify themselves with an
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/recipes-phosphor/leds/ethanolx-led-manager-config/ |
| H A D | led.yaml | 11 identify:
22 identify:
|
| /openbmc/openbmc/meta-intel-openbmc/meta-common/recipes-phosphor/leds/intel-led-manager-config/ |
| H A D | led.yaml | 34 identify:
|
| /openbmc/linux/drivers/block/mtip32xx/ |
| H A D | mtip32xx.c | 1164 port->identify[i] = le16_to_cpu(port->identify[i]); in mtip_get_identify()
1169 if (port->identify[128] & 0x4) in mtip_get_identify()
1180 port->identify, in mtip_get_identify()
1328 if (!(port->identify[82] & 0x1)) { in mtip_get_smart_attr()
1332 if (!(port->identify[85] & 0x1)) { in mtip_get_smart_attr()
1374 raw0 = port->identify[100]; in mtip_hw_get_capacity()
1375 raw1 = port->identify[101]; in mtip_hw_get_capacity()
1376 raw2 = port->identify[102]; in mtip_hw_get_capacity()
1377 raw3 = port->identify[103]; in mtip_hw_get_capacity()
1412 port->identify[128], in mtip_dump_identify()
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-networking/licenses/ |
| H A D | DMTF | 15 // identify any or all such third party patent right, owners or
20 // identify any such third party patent rights, or for such party's
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/cim-schema/files/ |
| H A D | LICENSE | 15 // identify any or all such third party patent right, owners or
20 // identify any such third party patent rights, or for such party's
|
| /openbmc/u-boot/cmd/ |
| H A D | pcmcia.c | 197 static int identify (volatile uchar *p) in identify() function
307 found = identify (ident); in check_ide_device()
|
| /openbmc/openbmc/meta-amd/meta-daytonax/recipes-phosphor/leds/daytonax-led-manager-config/ |
| H A D | led.yaml | 11 led-identify:
22 led-identify:
|
| /openbmc/linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-kernel-fadump_enabled | 7 Primarily used to identify whether the FADump is enabled in
|
| /openbmc/ibm-dbus-interfaces/com/ibm/Logging/ |
| H A D | Policy.interface.yaml | 7 This ID is defined by IBM service to uniquely identify an error
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Logging/ |
| H A D | Policy.interface.yaml | 7 This ID is defined by IBM service to uniquely identify an error in the
|
| /openbmc/pldm/libpldmresponder/examples/events/ |
| H A D | event_state_sensor.json | 1 // Each entry is to uniquely identify a remote state sensor(there are separate
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/gpio/id-button/ |
| H A D | toggle_identify_led.sh | 9 object=$(busctl tree $SERVICE --list | grep identify)
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/ |
| H A D | LocationCode.interface.yaml | 8 an Inventory Item. Location codes can be used to identify specific
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/ipzvpd/ |
| H A D | VSBP.interface.yaml | 19 A unique keyword to identify the system.
|
| /openbmc/openbmc/poky/meta/recipes-core/os-release/ |
| H A D | os-release.bb | 31 # advise developers leave it as this value to clearly identify the
33 # understand people will want to identify themselves as the people who
|
| /openbmc/linux/arch/arm/boot/dts/aspeed/ |
| H A D | aspeed-bmc-opp-vesnin.dts | 72 event-identify {
73 label = "identify";
|
| H A D | aspeed-bmc-tyan-s8036.dts | 48 identify {
379 * Notes on led-identify and id-button:
383 * - The flip-flop's Q output drives led-identify which is
400 /*A2*/ "led-identify", /* in/out: BMC_CHASSIS_ID_LED_L */
|
| /openbmc/u-boot/doc/ |
| H A D | README.fsl-dpaa | 9 so we introduce CONFIG_FSL_FM_10GEC_REGULAR_NOTATION to identify the new SoCs on
|
| /openbmc/pldm/libpldmresponder/test/pdr_jsons/state_sensor/malformed/ |
| H A D | sensor_pdr.json | 1 // This JSON is tied with BMC's PDRs. Each entry is used to identify a group of
|
| /openbmc/pldm/libpldmresponder/examples/pdr/ |
| H A D | sensor_pdr.json | 1 // This JSON is tied with BMC's PDRs. Each entry is used to identify a group of
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | devlink-flash.rst | 73 The ``driver`` attribute and ``fixed`` group identify the specific device
76 is fixed) - ``fixed`` versions should identify the design, not a single
79 ``running`` and ``stored`` firmware versions identify the firmware running
|
| /openbmc/u-boot/drivers/nvme/ |
| H A D | nvme.c | 438 c.identify.opcode = nvme_admin_identify; in nvme_identify()
439 c.identify.nsid = cpu_to_le32(nsid); in nvme_identify()
440 c.identify.prp1 = cpu_to_le64(dma_addr); in nvme_identify()
444 c.identify.prp2 = 0; in nvme_identify()
447 c.identify.prp2 = cpu_to_le64(dma_addr); in nvme_identify()
450 c.identify.cns = cpu_to_le32(cns); in nvme_identify()
|
| /openbmc/linux/arch/arm/boot/dts/marvell/ |
| H A D | armada-370-seagate-nas-2bay.dts | 11 * Here are some information allowing to identify the device:
|