| /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 …]
|
| /linux/drivers/scsi/libsas/ |
| H A D | sas_internal.h | 155 rphy->identify.sas_address = SAS_ADDR(dev->sas_addr); in sas_fill_in_rphy()
156 rphy->identify.initiator_port_protocols = dev->iproto; in sas_fill_in_rphy()
157 rphy->identify.target_port_protocols = dev->tproto; in sas_fill_in_rphy()
163 rphy->identify.device_type = SAS_END_DEVICE; in sas_fill_in_rphy()
166 rphy->identify.device_type = SAS_EDGE_EXPANDER_DEVICE; in sas_fill_in_rphy()
169 rphy->identify.device_type = SAS_FANOUT_EXPANDER_DEVICE; in sas_fill_in_rphy()
172 rphy->identify.device_type = SAS_PHY_UNUSED; in sas_fill_in_rphy()
183 phy->identify.device_type = SAS_END_DEVICE; in sas_phy_set_target()
185 phy->identify.device_type = dev->dev_type; in sas_phy_set_target()
186 phy->identify.target_port_protocols = dev->tproto; in sas_phy_set_target()
[all …]
|
| H A D | sas_phy.c | 141 phy->phy->identify.initiator_port_protocols = in sas_register_phys()
143 phy->phy->identify.target_port_protocols = phy->tproto; in sas_register_phys()
144 phy->phy->identify.sas_address = SAS_ADDR(sas_ha->sas_addr); in sas_register_phys()
145 phy->phy->identify.phy_identifier = i; in sas_register_phys()
|
| H A 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/drivers/scsi/ |
| H A D | scsi_transport_sas.c | 168 BUG_ON(rphy->identify.device_type != SAS_END_DEVICE); in sas_bitfield_name_search()
334 return rdev->rphy.identify.sas_address; in sas_get_address()
549 if (!phy->identify.device_type) in show_sas_device_type()
551 return get_sas_device_type_names(phy->identify.device_type, buf); in show_sas_device_type()
634 sas_phy_protocol_attr(identify.initiator_port_protocols,
636 sas_phy_protocol_attr(identify.target_port_protocols,
638 sas_phy_simple_attr(identify.sas_address, sas_address, "0x%016llx\n",
640 sas_phy_simple_attr(identify.phy_identifier, phy_identifier, "%d\n", u8);
1206 if (!rphy->identify.device_type) in show_sas_rphy_device_type()
1209 rphy->identify.device_type, buf); in show_sas_rphy_device_type()
[all …]
|
| /linux/include/scsi/ |
| H A D | scsi_transport_sas.h | 66 struct sas_identify identify; member
98 struct sas_identify identify; member
241 return rphy->identify.device_type == SAS_FANOUT_EXPANDER_DEVICE || in scsi_is_sas_expander_device()
242 rphy->identify.device_type == SAS_EDGE_EXPANDER_DEVICE;
|
| /linux/Documentation/devicetree/bindings/leds/ |
| H A D | leds-powernv.txt | 12 - led-types : Supported LED types (attention/identify/fault) provided
22 led-types = "identify", "fault";
|
| /linux/drivers/net/ethernet/intel/ |
| H A D | Kconfig | 37 to identify the adapter.
50 adapters. For more information on how to identify your adapter, go
70 identify your adapter, go to the Adapter & Driver ID Guide that
98 adapters. For more information on how to identify your adapter, go
134 information on how to identify your adapter, go to the Adapter &
156 adapters. For more information on how to identify your adapter, go
208 Intel(R) ixgbe driver. For more information on how to identify your
239 devices. For more information on how to identify your adapter, go
277 information on how to identify your adapter, go to the Adapter
309 devices. For more information on how to identify your adapter, go
[all …]
|
| /linux/arch/mips/dec/prom/ |
| H A D | Makefile | 7 lib-y += init.o memory.o cmdline.o identify.o console.o
|
| /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
|
| /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 */
|
| H A D | aspeed-bmc-tyan-s7106.dts | 48 identify {
425 * Notes on led-identify and id-button:
429 * - The flip-flop's Q output drives led-identify which is
446 /*A2*/ "led-identify", /* in/out: BMC_IDLED_ON_N */
|
| H A D | aspeed-bmc-amd-daytonax.dts | 46 led-identify {
125 /*A0-A7*/ "","","led-fault","led-identify","","","","",
|
| /linux/arch/mips/fw/arc/ |
| H A D | Makefile | 9 lib-y += cmdline.o env.o file.o identify.o init.o \
|
| /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
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-kernel-fadump_enabled | 7 Primarily used to identify whether the FADump is enabled in
|
| /linux/drivers/nvme/target/ |
| H A D | passthru.c | 227 switch (req->cmd->identify.cns) { in nvmet_passthru_execute_cmd_work()
543 switch (req->cmd->identify.cns) { in nvmet_parse_passthru_admin_cmd()
545 switch (req->cmd->identify.csi) { in nvmet_parse_passthru_admin_cmd()
559 switch (req->cmd->identify.csi) { in nvmet_parse_passthru_admin_cmd()
|
| /linux/include/linux/pds/ |
| H A D | pds_core_if.h | 456 struct pds_core_dev_identify_cmd identify; member
474 struct pds_core_dev_identify_comp identify; member
|
| /linux/drivers/soc/vt8500/ |
| H A D | Kconfig | 14 which helps identify the exact hardware revision of the SoC the kernel
|
| /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:
|
| H A D | armada-370-seagate-personal-cloud.dts | 11 * Here are some information allowing to identify the device:
|
| H A D | armada-370-seagate-personal-cloud-2bay.dts | 11 * Here are some information allowing to identify the device:
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-sun | 13 So reading the sysfs file, we can identify a physical position
|
| /linux/Documentation/driver-api/pldmfw/ |
| H A D | file-format.rst | 83 Each record will identify the device it supports via TLVs that describe the
142 data is stored, and includes version data used to identify the version of
|