Home
last modified time | relevance | path

Searched refs:identify (Results 1 – 25 of 344) sorted by relevance

12345678910>>...14

/Linux-v5.15/drivers/scsi/libsas/
Dsas_internal.h120 rphy->identify.sas_address = SAS_ADDR(dev->sas_addr); in sas_fill_in_rphy()
121 rphy->identify.initiator_port_protocols = dev->iproto; in sas_fill_in_rphy()
122 rphy->identify.target_port_protocols = dev->tproto; in sas_fill_in_rphy()
128 rphy->identify.device_type = SAS_END_DEVICE; in sas_fill_in_rphy()
131 rphy->identify.device_type = SAS_EDGE_EXPANDER_DEVICE; in sas_fill_in_rphy()
134 rphy->identify.device_type = SAS_FANOUT_EXPANDER_DEVICE; in sas_fill_in_rphy()
137 rphy->identify.device_type = SAS_PHY_UNUSED; in sas_fill_in_rphy()
148 phy->identify.device_type = SAS_END_DEVICE; in sas_phy_set_target()
150 phy->identify.device_type = dev->dev_type; in sas_phy_set_target()
151 phy->identify.target_port_protocols = dev->tproto; in sas_phy_set_target()
[all …]
Dsas_phy.c138 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()
Dsas_host_smp.c47 resp_data[12] = rphy->identify.device_type << 4; in sas_host_smp_discover()
48 resp_data[14] = rphy->identify.initiator_port_protocols; in sas_host_smp_discover()
49 resp_data[15] = rphy->identify.target_port_protocols; in sas_host_smp_discover()
157 if (rphy->identify.target_port_protocols != SAS_PROTOCOL_SATA) in sas_report_phy_sata()
/Linux-v5.15/drivers/scsi/smartpqi/
Dsmartpqi_sas_transport.c59 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 …]
/Linux-v5.15/drivers/scsi/mpt3sas/
Dmpt3sas_transport.c121 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()
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()
242 identify->device_type = SAS_PHY_UNUSED; in _transport_set_identify()
245 identify->device_type = SAS_END_DEVICE; in _transport_set_identify()
248 identify->device_type = SAS_EDGE_EXPANDER_DEVICE; in _transport_set_identify()
[all …]
/Linux-v5.15/drivers/nvme/host/
Dzns.c31 c.identify.opcode = nvme_admin_identify; in nvme_set_max_append()
32 c.identify.cns = NVME_ID_CNS_CS_CTRL; in nvme_set_max_append()
33 c.identify.csi = NVME_CSI_ZNS; in nvme_set_max_append()
82 c.identify.opcode = nvme_admin_identify; in nvme_update_zone_info()
83 c.identify.nsid = cpu_to_le32(ns->head->ns_id); in nvme_update_zone_info()
84 c.identify.cns = NVME_ID_CNS_CS_NS; in nvme_update_zone_info()
85 c.identify.csi = NVME_CSI_ZNS; in nvme_update_zone_info()
/Linux-v5.15/drivers/message/fusion/
Dmptsas.c110 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 …]
/Linux-v5.15/drivers/scsi/
Dscsi_transport_sas.c166 BUG_ON(rphy->identify.device_type != SAS_END_DEVICE); in sas_bitfield_name_search()
326 return rdev->rphy.identify.sas_address; in sas_get_address()
518 if (!phy->identify.device_type) in show_sas_device_type()
520 return get_sas_device_type_names(phy->identify.device_type, buf); in show_sas_device_type()
603 sas_phy_protocol_attr(identify.initiator_port_protocols,
605 sas_phy_protocol_attr(identify.target_port_protocols,
607 sas_phy_simple_attr(identify.sas_address, sas_address, "0x%016llx\n",
609 sas_phy_simple_attr(identify.phy_identifier, phy_identifier, "%d\n", u8);
1168 if (!rphy->identify.device_type) in show_sas_rphy_device_type()
1171 rphy->identify.device_type, buf); in show_sas_rphy_device_type()
[all …]
/Linux-v5.15/include/scsi/
Dscsi_transport_sas.h65 struct sas_identify identify; member
97 struct sas_identify identify; member
238 return rphy->identify.device_type == SAS_FANOUT_EXPANDER_DEVICE || in scsi_is_sas_expander_device()
239 rphy->identify.device_type == SAS_EDGE_EXPANDER_DEVICE; in scsi_is_sas_expander_device()
/Linux-v5.15/drivers/net/ethernet/intel/
DKconfig34 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 &
148 instead. For more information on how to identify your adapter, go
167 adapters. For more information on how to identify your adapter, go
219 Intel(R) ixgbe driver. For more information on how to identify your
247 devices. For more information on how to identify your adapter, go
280 information on how to identify your adapter, go to the Adapter
[all …]
/Linux-v5.15/drivers/hwmon/pmbus/
Dtps53679.c250 info->identify = tps53679_identify; in tps53679_probe()
253 info->identify = tps53676_identify; in tps53679_probe()
258 info->identify = tps53679_identify; in tps53679_probe()
263 info->identify = tps53681_identify; in tps53679_probe()
/Linux-v5.15/Documentation/devicetree/bindings/leds/
Dleds-powernv.txt12 - led-types : Supported LED types (attention/identify/fault) provided
22 led-types = "identify", "fault";
/Linux-v5.15/drivers/block/mtip32xx/
Dmtip32xx.c1091 *timeout = ((*(dd->port->identify + 90) * 2) * 60000); in mtip_set_timeout()
1093 *timeout = ((*(dd->port->identify + 89) * 2) * 60000); in mtip_set_timeout()
1148 memset(port->identify, 0, sizeof(u16) * ATA_ID_WORDS); in mtip_get_identify()
1169 ata_swap_string(port->identify + 27, 40); /* model string*/ in mtip_get_identify()
1170 ata_swap_string(port->identify + 23, 8); /* firmware string*/ in mtip_get_identify()
1171 ata_swap_string(port->identify + 10, 20); /* serial# string*/ in mtip_get_identify()
1176 port->identify[i] = le16_to_cpu(port->identify[i]); in mtip_get_identify()
1181 if (port->identify[128] & 0x4) in mtip_get_identify()
1192 port->identify, in mtip_get_identify()
1340 if (!(port->identify[82] & 0x1)) { in mtip_get_smart_attr()
[all …]
/Linux-v5.15/drivers/nvme/target/
Dadmin-cmd.c489 if (le32_to_cpu(req->cmd->identify.nsid) == NVME_NSID_ALL) { in nvmet_execute_identify_ns()
573 u32 min_nsid = le32_to_cpu(req->cmd->identify.nsid); in nvmet_execute_identify_nslist()
661 switch (req->cmd->identify.csi) { in nvmet_handle_identify_desclist()
681 switch (req->cmd->identify.cns) { in nvmet_execute_identify()
683 switch (req->cmd->identify.csi) { in nvmet_execute_identify()
692 switch (req->cmd->identify.csi) { in nvmet_execute_identify()
701 switch (req->cmd->identify.csi) { in nvmet_execute_identify()
708 switch (req->cmd->identify.csi) { in nvmet_execute_identify()
717 switch (req->cmd->identify.csi) { in nvmet_execute_identify()
Dpassthru.c172 switch (req->cmd->identify.cns) { in nvmet_passthru_execute_cmd_work()
474 switch (req->cmd->identify.cns) { in nvmet_parse_passthru_admin_cmd()
480 switch (req->cmd->identify.csi) { in nvmet_parse_passthru_admin_cmd()
492 switch (req->cmd->identify.csi) { in nvmet_parse_passthru_admin_cmd()
/Linux-v5.15/arch/mips/dec/prom/
DMakefile7 lib-y += init.o memory.o cmdline.o identify.o console.o
/Linux-v5.15/arch/mips/fw/arc/
DMakefile9 lib-y += cmdline.o env.o file.o identify.o init.o \
/Linux-v5.15/Documentation/ABI/obsolete/
Dsysfs-kernel-fadump_enabled7 Primarily used to identify whether the FADump is enabled in
/Linux-v5.15/Documentation/networking/devlink/
Ddevlink-flash.rst73 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
Dice.rst36 identify what commands are supported. Historical versions of the
72 required to uniquely identify the package.
77 referred to as the DDP Track ID. Can be used to uniquely identify
/Linux-v5.15/Documentation/livepatch/
Dreliable-stacktrace.rst16 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
/Linux-v5.15/arch/arm/boot/dts/
Darmada-370-seagate-nas-2bay.dts11 * Here are some information allowing to identify the device:
Darmada-370-seagate-personal-cloud.dts11 * Here are some information allowing to identify the device:
/Linux-v5.15/Documentation/devicetree/bindings/misc/
Dnvidia,tegra186-misc.txt4 that can be used to identify a given chip and various strapping options.
/Linux-v5.15/Documentation/ABI/testing/
Dsysfs-devices-sun13 So reading the sysfs file, we can identify a physical position

12345678910>>...14