Home
last modified time | relevance | path

Searched full:identify (Results 1 – 25 of 1082) sorted by relevance

12345678910>>...44

/linux/drivers/scsi/smartpqi/
H A 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/drivers/scsi/libsas/
H A Dsas_internal.h168 rphy->identify.sas_address = SAS_ADDR(dev->sas_addr); in sas_fill_in_rphy()
169 rphy->identify.initiator_port_protocols = dev->iproto; in sas_fill_in_rphy()
170 rphy->identify.target_port_protocols = dev->tproto; in sas_fill_in_rphy()
176 rphy->identify.device_type = SAS_END_DEVICE; in sas_fill_in_rphy()
179 rphy->identify.device_type = SAS_EDGE_EXPANDER_DEVICE; in sas_fill_in_rphy()
182 rphy->identify.device_type = SAS_FANOUT_EXPANDER_DEVICE; in sas_fill_in_rphy()
185 rphy->identify.device_type = SAS_PHY_UNUSED; in sas_fill_in_rphy()
196 phy->identify.device_type = SAS_END_DEVICE; in sas_phy_set_target()
198 phy->identify.device_type = dev->dev_type; in sas_phy_set_target()
199 phy->identify.target_port_protocols = dev->tproto; in sas_phy_set_target()
[all …]
H A 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()
H A 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/drivers/nvme/host/
H A Dzns.c20 c.identify.opcode = nvme_admin_identify; in nvme_set_max_append()
21 c.identify.cns = NVME_ID_CNS_CS_CTRL; in nvme_set_max_append()
22 c.identify.csi = NVME_CSI_ZNS; in nvme_set_max_append()
71 c.identify.opcode = nvme_admin_identify; in nvme_query_zone_info()
72 c.identify.nsid = cpu_to_le32(ns->head->ns_id); in nvme_query_zone_info()
73 c.identify.cns = NVME_ID_CNS_CS_NS; in nvme_query_zone_info()
74 c.identify.csi = NVME_CSI_ZNS; in nvme_query_zone_info()
/linux/include/uapi/linux/
H A Dlsm.h44 * ID tokens to identify Linux Security Modules (LSMs)
46 * These token values are used to uniquely identify specific LSMs
70 * LSM_ATTR_XXX definitions identify different LSM attributes
88 * LSM_FLAG_XXX definitions identify special handling instructions
/linux/include/linux/iio/
H A Dmachine.h13 * @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
/linux/drivers/misc/sgi-gru/
H A Dgrukservices.h160 * 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
/linux/drivers/scsi/
H A Dscsi_transport_sas.c168 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/Documentation/livepatch/
H A 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/include/uapi/drm/
H A Dqaic_accel.h66 * @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.
/linux/include/linux/pds/
H A Dpds_core_if.h106 * @version: Version of device identify
107 * @type: Identify type (0 for now)
139 * struct pds_core_dev_identify_cmd - Driver/device identify command
141 * @ver: Highest version of identify supported by driver
153 * struct pds_core_dev_identify_comp - Device identify command completion
155 * @ver: Version of identify returned by device
456 struct pds_core_dev_identify_cmd identify; member
474 struct pds_core_dev_identify_comp identify; member
/linux/arch/arm64/kernel/vdso/
H A Dsigreturn.S38 * unwinders (e.g. libstdc++) to implement _Unwind_GetIPInfo() and identify
59 * identify the calling function.
65 * GDB, libgcc and libunwind rely on being able to identify the sigreturn
/linux/include/uapi/scsi/
H A Dscsi_bsg_ufs.h101 * @index: Index to further identify data B-2
102 * @selector: Index to further identify data B-3
124 * @index: Index to further identify data B-2
125 * @selector: Index to further identify data B-3
/linux/drivers/block/mtip32xx/
H A Dmtip32xx.h326 * identify field is valid.
358 * Pointer to the DMA region for RX Fis, Identify, RLE10, and SMART
362 * DMA address of region for RX Fis, Identify, RLE10, and SMART
366 * Pointer to the beginning of the identify data memory as used
369 u16 *identify; member
371 * Pointer to the beginning of the identify data memory as used
/linux/include/scsi/
H A Dscsi_transport_sas.h66 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 Dleds-powernv.txt12 - led-types : Supported LED types (attention/identify/fault) provided
22 led-types = "identify", "fault";
/linux/drivers/hwmon/pmbus/
H A Dmp2975.c567 * Identify multiphase for rail 2 - could be from 0 to data->max_phases[1]. in mp2975_identify_multiphase_rail2()
610 /* Identify multiphase for rail 1 - could be from 1 to data->max_phases[0]. */ in mp2975_identify_multiphase()
646 /* Identify VID mode and step selection. */ in mp2975_identify_vid()
675 /* Identify VID mode for rail 1. */ in mp2975_identify_rails_vid()
682 /* Identify VID mode for rail 2, if connected. */ in mp2975_identify_rails_vid()
702 /* Identify VID mode for rail 1. */ in mp2973_identify_rails_vid()
710 /* Identify VID mode for rail 2, if connected. */ in mp2973_identify_rails_vid()
1020 /* Identify multiphase configuration for rail 2. */ in mp2975_probe()
1034 /* Identify multiphase configuration. */ in mp2975_probe()
1040 /* Identify VID setting per rail. */ in mp2975_probe()
[all …]
H A Dmp2891.c16 * is used to identify the iout scale and the MFR_VOUT_LOOP_CTRL(0xBD)
17 * is used to identify the vout scale. The READ_PIN_EST(0x94) is used
179 /* Identify vout scale for rail 1. */ in mp2891_identify()
184 /* Identify vout scale for rail 2. */ in mp2891_identify()
189 /* Identify iout scale for rail 1. */ in mp2891_identify()
194 /* Identify iout scale for rail 2. */ in mp2891_identify()
558 .identify = mp2891_identify,
/linux/include/linux/
H A DmISDNdsp.h27 int hfc_id; /* unique id to identify the chip (or -1) */
32 int pcm_id; /* unique id to identify the pcm bus (or -1) */
/linux/sound/soc/sof/
H A Dipc4-telemetry.h38 /* Identify the version of the header */
58 /* Identify the version of this block */
/linux/Documentation/networking/devlink/
H A 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
/linux/tools/power/cpupower/bench/
H A DREADME-BENCH7 - Identify worst case performance loss when doing dynamic frequency
9 - Identify average reaction time of a governor to CPU load changes
12 - Identify cpufreq related performance regressions between kernels
/linux/include/linux/irqchip/
H A Dirq-bcm2836.h12 * The low 2 bits identify the CPU that the GPU IRQ goes to, and the
13 * next 2 bits identify the CPU that the GPU FIQ goes to.
/linux/drivers/staging/greybus/Documentation/firmware/
H A Dfirmware-management57 and user first needs to identify the character device used for
61 be used by the user to identify the right character device for it. The class
195 gb-authenticate-N and user first needs to identify the character device used for
199 be used by the user to identify the right character device for it. The class

12345678910>>...44