| /openbmc/linux/drivers/scsi/smartpqi/ |
| H A D | smartpqi_sas_transport.c | 59 struct sas_identify *identify; in pqi_sas_port_add_phy() local
64 identify = &phy->identify; in pqi_sas_port_add_phy()
65 memset(identify, 0, sizeof(*identify)); in pqi_sas_port_add_phy()
66 identify->sas_address = pqi_sas_port->sas_address; in pqi_sas_port_add_phy()
67 identify->device_type = SAS_END_DEVICE; in pqi_sas_port_add_phy()
68 identify->initiator_port_protocols = SAS_PROTOCOL_ALL; in pqi_sas_port_add_phy()
69 identify->target_port_protocols = SAS_PROTOCOL_ALL; in pqi_sas_port_add_phy()
91 struct sas_identify *identify; in pqi_sas_port_add_rphy() local
93 identify = &rphy->identify; in pqi_sas_port_add_rphy()
94 identify->sas_address = pqi_sas_port->sas_address; in pqi_sas_port_add_rphy()
[all …]
|
| /openbmc/phosphor-led-sysfs/ |
| H A D | README.md | 7 Say we have 'identify' LED in our system, which may be declared in devicetree.
13 identify {
23 ./add-led-action --path /sys/class/leds/identify
34 `- /xyz/openbmc_project/led/physical/identify
36 busctl introspect xyz.openbmc_project.LED.Controller /xyz/openbmc_project/led/physical/identify
55 /xyz/openbmc_project/led/physical/identify \
64 /xyz/openbmc_project/led/physical/identify \
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_general.robot | 202 Verify Chassis Identify via IPMI
203 [Documentation] Set chassis identify using IPMI and verify.
208 # Set to default "chassis identify" and verify that LED blinks for 15s.
209 Run IPMI Standard Command chassis identify
210 Verify Identify LED State Via Redfish True
213 Verify Identify LED State Via Redfish False
215 # Set "chassis identify" to 10s and verify that the LED blinks for 10s.
216 Run IPMI Standard Command chassis identify 10
217 Verify Identify LED State Via Redfish True
220 Verify Identify LED State Via Redfish False
[all …]
|
| H A D | test_ipmi_sel_time.robot | 102 # Identify Time difference and find the difference is less than 6 seconds.
120 ${sel_time} ${set_sel_time}= Identify SEL Time +06:15:00
143 ${sel_time} ${set_sel_time}= Identify SEL Time -24:00:00
225 # Identify Time difference and find the difference is less than 6 seconds.
257 # Identify and find the time difference is less than 60 seconds.
271 ${sel_time} ${set_sel_time}= Identify SEL Time +06:15:00
308 # Identify and find the time difference is less than 60 seconds.
322 ${sel_time} ${set_sel_time}= Identify SEL Time -24:00:00
359 # Identify and find the time difference is less than 60 seconds.
375 ${sel_time} ${set_sel_time}= Identify SEL Time ${time_difference_list[${i}]}
[all …]
|
| /openbmc/linux/drivers/scsi/libsas/ |
| H A D | sas_internal.h | 156 rphy->identify.sas_address = SAS_ADDR(dev->sas_addr); in sas_fill_in_rphy()
157 rphy->identify.initiator_port_protocols = dev->iproto; in sas_fill_in_rphy()
158 rphy->identify.target_port_protocols = dev->tproto; in sas_fill_in_rphy()
164 rphy->identify.device_type = SAS_END_DEVICE; in sas_fill_in_rphy()
167 rphy->identify.device_type = SAS_EDGE_EXPANDER_DEVICE; in sas_fill_in_rphy()
170 rphy->identify.device_type = SAS_FANOUT_EXPANDER_DEVICE; in sas_fill_in_rphy()
173 rphy->identify.device_type = SAS_PHY_UNUSED; in sas_fill_in_rphy()
184 phy->identify.device_type = SAS_END_DEVICE; in sas_phy_set_target()
186 phy->identify.device_type = dev->dev_type; in sas_phy_set_target()
187 phy->identify.target_port_protocols = dev->tproto; in sas_phy_set_target()
[all …]
|
| H A D | sas_phy.c | 138 phy->phy->identify.initiator_port_protocols = in sas_register_phys()
140 phy->phy->identify.target_port_protocols = phy->tproto; in sas_register_phys()
141 phy->phy->identify.sas_address = SAS_ADDR(sas_ha->sas_addr); in sas_register_phys()
142 phy->phy->identify.phy_identifier = i; in sas_register_phys()
|
| /openbmc/linux/drivers/net/ethernet/intel/ |
| H A D | Kconfig | 34 to identify the adapter.
47 adapters. For more information on how to identify your adapter, go
67 identify your adapter, go to the Adapter & Driver ID Guide that
95 adapters. For more information on how to identify your adapter, go
131 information on how to identify your adapter, go to the Adapter &
150 adapters. For more information on how to identify your adapter, go
202 Intel(R) ixgbe driver. For more information on how to identify your
230 devices. For more information on how to identify your adapter, go
263 information on how to identify your adapter, go to the Adapter
289 devices. For more information on how to identify your adapter, go
[all …]
|
| /openbmc/libpldm/include/libpldm/ |
| H A D | bios.h | 248 * @param[in] transfer_handle - Handle to identify a BIOS table transfer
275 * @param[out] next_transfer_handle - Pointer to a handle that identify the
288 * @param[in] transfer_handle - Handle to identify a BIOS table transfer
318 * @param[out] next_transfer_handle - Pointer to a handle that identify the
357 * @param[in] next_transfer_handle - handle to identify the next portion of the
374 * @param[in] transfer_handle - Handle to identify a BIOS table transfer
389 * @param[out] transfer_handle - Handle to identify a BIOS table transfer
404 * @param[in] next_transfer_handle - handle to identify the next portion of the
423 * @param[in] transfer_handle - Handle to identify a BIOS attribute transfer
426 * @param[in] attribute_handle - Handle to identify the BIOS attribute
[all …]
|
| H A D | fru.h | 245 * @param[out] data_transfer_handle - A handle, used to identify a FRU Record
260 * @param[in] next_data_transfer_handle - A handle that is used to identify the
281 * @param[out] data_transfer_handle - A handle, used to identify a FRU Record
283 * @param[out] fru_table_handle - A handle, used to identify a FRU DATA
302 * @param[in] next_data_transfer_handle - A handle that is used to identify the
328 * @param[in] data_transfer_handle - A handle, used to identify a FRU Record
350 * @param[out] next_data_transfer_handle - A handle used to identify the next
374 * @param[out] next_data_transfer_handle - A handle used to identify the next
419 * @param[in] data_transfer_handle - A handle, used to identify a FRU Record
421 * @param[in] fru_table_handle - A handle, used to identify a FRU DATA records
[all …]
|
| /openbmc/u-boot/include/ |
| H A D | nvme.h | 13 * nvme_identify - identify controller or namespace capabilities and status
15 * This issues an identify command to the NVMe controller to return a data
19 * @nsid: 0 for controller, namespace id for namespace to identify
21 * @dma_addr: dma buffer address to store the identify result
77 * @return: 0 on success, -EIO if NVMe identify command fails
|
| /openbmc/openbmc/meta-nuvoton/meta-evb-npcm845/recipes-phosphor/leds/evb-npcm845-led-manager-config/ |
| H A D | led.yaml | 8 identify:
12 identify:
16 identify:
|
| /openbmc/linux/drivers/scsi/mpt3sas/ |
| H A D | mpt3sas_transport.c | 121 if (rphy->identify.device_type == SAS_EDGE_EXPANDER_DEVICE || in _transport_get_port_id_by_rphy()
122 rphy->identify.device_type == SAS_FANOUT_EXPANDER_DEVICE) { in _transport_get_port_id_by_rphy()
132 } else if (rphy->identify.device_type == SAS_END_DEVICE) { in _transport_get_port_id_by_rphy()
192 * _transport_set_identify - set identify for phys and end devices
195 * @identify: sas identify info
197 * Populates sas identify info.
203 struct sas_identify *identify) in _transport_set_identify() argument
230 memset(identify, 0, sizeof(struct sas_identify)); in _transport_set_identify()
234 identify->sas_address = le64_to_cpu(sas_device_pg0.SASAddress); in _transport_set_identify()
237 identify->phy_identifier = sas_device_pg0.PhyNum; in _transport_set_identify()
[all …]
|
| /openbmc/openbmc/meta-quanta/meta-olympus-nuvoton/recipes-phosphor/leds/olympus-nuvoton-led-manager-config/ |
| H A D | led.yaml | 8 identify:
14 identify:
20 identify:
|
| /openbmc/openbmc/meta-ibm/meta-palmetto/recipes-phosphor/leds/palmetto-led-manager-config/ |
| H A D | led.yaml | 14 identify:
20 identify:
31 identify:
|
| /openbmc/linux/drivers/nvme/host/ |
| H A D | zns.c | 30 c.identify.opcode = nvme_admin_identify; in nvme_set_max_append()
31 c.identify.cns = NVME_ID_CNS_CS_CTRL; in nvme_set_max_append()
32 c.identify.csi = NVME_CSI_ZNS; in nvme_set_max_append()
81 c.identify.opcode = nvme_admin_identify; in nvme_update_zone_info()
82 c.identify.nsid = cpu_to_le32(ns->head->ns_id); in nvme_update_zone_info()
83 c.identify.cns = NVME_ID_CNS_CS_NS; in nvme_update_zone_info()
84 c.identify.csi = NVME_CSI_ZNS; in nvme_update_zone_info()
|
| /openbmc/linux/include/linux/iio/ |
| H A D | machine.h | 13 * @adc_channel_label: Label used to identify the channel on the provider.
16 * @consumer_dev_name: Name to uniquely identify the consumer device.
17 * @consumer_channel: Unique name used to identify the channel on the
|
| /openbmc/linux/drivers/message/fusion/ |
| H A D | mptsas.c | 110 static void mptsas_parse_device_info(struct sas_identify *identify,
414 if (port_info->phy_info[i].identify.handle == handle) { in mptsas_find_portinfo_by_handle()
446 if (port_info->phy_info[i].identify.sas_address == in mptsas_find_portinfo_by_sas_address()
629 if (rphy->identify.sas_address == sas_address) { in mptsas_add_device_component()
792 rphy->identify.sas_address); in mptsas_add_device_component_starget()
1448 struct sas_identify identify; in mptsas_add_end_device() local
1492 mptsas_parse_device_info(&identify, &phy_info->attached); in mptsas_add_end_device()
1501 rphy->identify = identify; in mptsas_add_end_device()
1788 rphy->identify.sas_address) in mptsas_target_alloc()
1847 rphy->identify.sas_address) in mptsas_target_destroy()
[all …]
|
| /openbmc/linux/drivers/misc/sgi-gru/ |
| H A D | grukservices.h | 160 * handle to identify resource
170 * han - handle to identify resources
178 * han - handle to identify resources
186 * han - handle to identify resources
197 * han - handle to identify resources
|
| /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/linux/drivers/scsi/mpi3mr/ |
| H A D | mpi3mr_transport.c | 494 * address and hba port are used to identify the exact expander
526 phy->identify.sas_address, in mpi3mr_parent_present()
772 * mpi3mr_set_identify - set identify for phys and end devices
775 * @identify: SAS transport layer's identify info
777 * Populates sas identify info for a specific device.
782 struct sas_identify *identify) in mpi3mr_set_identify() argument
807 memset(identify, 0, sizeof(struct sas_identify)); in mpi3mr_set_identify()
812 identify->sas_address = le64_to_cpu(sasinf->sas_address); in mpi3mr_set_identify()
815 identify->phy_identifier = sasinf->phy_num; in mpi3mr_set_identify()
820 identify->device_type = SAS_PHY_UNUSED; in mpi3mr_set_identify()
[all …]
|
| /openbmc/linux/drivers/scsi/ |
| H A D | scsi_transport_sas.c | 166 BUG_ON(rphy->identify.device_type != SAS_END_DEVICE); in sas_bitfield_name_search()
332 return rdev->rphy.identify.sas_address; in sas_get_address()
547 if (!phy->identify.device_type) in show_sas_device_type()
549 return get_sas_device_type_names(phy->identify.device_type, buf); in show_sas_device_type()
632 sas_phy_protocol_attr(identify.initiator_port_protocols,
634 sas_phy_protocol_attr(identify.target_port_protocols,
636 sas_phy_simple_attr(identify.sas_address, sas_address, "0x%016llx\n",
638 sas_phy_simple_attr(identify.phy_identifier, phy_identifier, "%d\n", u8);
1202 if (!rphy->identify.device_type) in show_sas_rphy_device_type()
1205 rphy->identify.device_type, buf); in show_sas_rphy_device_type()
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/ |
| H A D | AssetTag.interface.yaml | 2 Implement to provide Asset Tag. The asset tag is used to uniquely identify
8 The tag provided to an object to identify it.
|
| /openbmc/linux/include/uapi/drm/ |
| H A D | qaic_accel.h | 66 * @hdr: In. Header to identify this transaction.
77 * @hdr: In. Header to identify this transaction.
94 * @hdr: In. Header to identify this transaction.
110 * @hdr: Out. Header to identify this transaction.
124 * @hdr: In. Header to identify this transaction.
136 * @hdr: In. Header to identify this transaction.
144 * @hdr: Out. Header to identify this transaction.
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 16 to identify which functions are live is to use a stacktrace.
116 trace, it is strongly recommended that architectures positively identify code
124 There are several ways an architecture may identify kernel code which is deemed
145 and it may not be possible to identify whether such unwinding will be reliable.
148 Architectures which cannot identify when it is reliable to unwind such cases
154 Architectures which can identify when it is reliable to unwind such cases (or
308 reliably identify when the LR or stack value should be used (e.g. using
|