| /Linux-v6.6/drivers/scsi/smartpqi/ |
| 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 …]
|
| /Linux-v6.6/drivers/scsi/libsas/ |
| D | sas_internal.h | 142 rphy->identify.sas_address = SAS_ADDR(dev->sas_addr); in sas_fill_in_rphy()
143 rphy->identify.initiator_port_protocols = dev->iproto; in sas_fill_in_rphy()
144 rphy->identify.target_port_protocols = dev->tproto; in sas_fill_in_rphy()
150 rphy->identify.device_type = SAS_END_DEVICE; in sas_fill_in_rphy()
153 rphy->identify.device_type = SAS_EDGE_EXPANDER_DEVICE; in sas_fill_in_rphy()
156 rphy->identify.device_type = SAS_FANOUT_EXPANDER_DEVICE; in sas_fill_in_rphy()
159 rphy->identify.device_type = SAS_PHY_UNUSED; in sas_fill_in_rphy()
170 phy->identify.device_type = SAS_END_DEVICE; in sas_phy_set_target()
172 phy->identify.device_type = dev->dev_type; in sas_phy_set_target()
173 phy->identify.target_port_protocols = dev->tproto; in sas_phy_set_target()
[all …]
|
| 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()
|
| D | sas_host_smp.c | 47 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-v6.6/drivers/scsi/mpt3sas/ |
| 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()
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-v6.6/drivers/nvme/host/ |
| 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()
|
| /Linux-v6.6/drivers/message/fusion/ |
| 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 …]
|
| /Linux-v6.6/drivers/scsi/mpi3mr/ |
| D | mpi3mr_transport.c | 526 phy->identify.sas_address, in mpi3mr_parent_present()
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()
823 identify->device_type = SAS_END_DEVICE; in mpi3mr_set_identify()
826 identify->device_type = SAS_EDGE_EXPANDER_DEVICE; in mpi3mr_set_identify()
832 identify->initiator_port_protocols |= SAS_PROTOCOL_SSP; in mpi3mr_set_identify()
835 identify->initiator_port_protocols |= (SAS_PROTOCOL_STP | in mpi3mr_set_identify()
[all …]
|
| /Linux-v6.6/drivers/scsi/ |
| 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()
524 if (!phy->identify.device_type) in show_sas_device_type()
526 return get_sas_device_type_names(phy->identify.device_type, buf); in show_sas_device_type()
609 sas_phy_protocol_attr(identify.initiator_port_protocols,
611 sas_phy_protocol_attr(identify.target_port_protocols,
613 sas_phy_simple_attr(identify.sas_address, sas_address, "0x%016llx\n",
615 sas_phy_simple_attr(identify.phy_identifier, phy_identifier, "%d\n", u8);
1179 if (!rphy->identify.device_type) in show_sas_rphy_device_type()
1182 rphy->identify.device_type, buf); in show_sas_rphy_device_type()
[all …]
|
| /Linux-v6.6/include/scsi/ |
| D | scsi_transport_sas.h | 66 struct sas_identify identify; member
98 struct sas_identify identify; member
239 return rphy->identify.device_type == SAS_FANOUT_EXPANDER_DEVICE || in scsi_is_sas_expander_device()
240 rphy->identify.device_type == SAS_EDGE_EXPANDER_DEVICE; in scsi_is_sas_expander_device()
|
| /Linux-v6.6/drivers/hwmon/pmbus/ |
| D | tps53679.c | 250 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-v6.6/Documentation/devicetree/bindings/leds/ |
| D | leds-powernv.txt | 12 - led-types : Supported LED types (attention/identify/fault) provided
22 led-types = "identify", "fault";
|
| /Linux-v6.6/drivers/net/ethernet/intel/ |
| 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 …]
|
| /Linux-v6.6/Documentation/filesystems/ |
| 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
|
| /Linux-v6.6/drivers/block/mtip32xx/ |
| D | mtip32xx.c | 1079 *timeout = ((*(dd->port->identify + 90) * 2) * 60000); in mtip_set_timeout()
1081 *timeout = ((*(dd->port->identify + 89) * 2) * 60000); in mtip_set_timeout()
1136 memset(port->identify, 0, sizeof(u16) * ATA_ID_WORDS); in mtip_get_identify()
1157 ata_swap_string(port->identify + 27, 40); /* model string*/ in mtip_get_identify()
1158 ata_swap_string(port->identify + 23, 8); /* firmware string*/ in mtip_get_identify()
1159 ata_swap_string(port->identify + 10, 20); /* serial# string*/ in mtip_get_identify()
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()
[all …]
|
| /Linux-v6.6/arch/mips/dec/prom/ |
| D | Makefile | 7 lib-y += init.o memory.o cmdline.o identify.o console.o
|
| /Linux-v6.6/arch/mips/fw/arc/ |
| D | Makefile | 9 lib-y += cmdline.o env.o file.o identify.o init.o \
|
| /Linux-v6.6/arch/arm/boot/dts/aspeed/ |
| D | aspeed-bmc-opp-vesnin.dts | 72 event-identify {
73 label = "identify";
|
| 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 */
|
| /Linux-v6.6/Documentation/networking/devlink/ |
| 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
|
| /Linux-v6.6/Documentation/ABI/obsolete/ |
| D | sysfs-kernel-fadump_enabled | 7 Primarily used to identify whether the FADump is enabled in
|
| /Linux-v6.6/Documentation/livepatch/ |
| 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
|
| /Linux-v6.6/drivers/nvme/target/ |
| D | passthru.c | 227 switch (req->cmd->identify.cns) { in nvmet_passthru_execute_cmd_work()
537 switch (req->cmd->identify.cns) { in nvmet_parse_passthru_admin_cmd()
543 switch (req->cmd->identify.csi) { in nvmet_parse_passthru_admin_cmd()
555 switch (req->cmd->identify.csi) { in nvmet_parse_passthru_admin_cmd()
|
| /Linux-v6.6/arch/arm/boot/dts/marvell/ |
| D | armada-370-seagate-nas-2bay.dts | 11 * Here are some information allowing to identify the device:
|
| D | armada-370-seagate-personal-cloud.dts | 11 * Here are some information allowing to identify the device:
|
