Home
last modified time | relevance | path

Searched refs:identify (Results 1 – 200 of 206) sorted by relevance

12

/linux-4.4.14/drivers/scsi/libsas/
Dsas_internal.h128 rphy->identify.sas_address = SAS_ADDR(dev->sas_addr); in sas_fill_in_rphy()
129 rphy->identify.initiator_port_protocols = dev->iproto; in sas_fill_in_rphy()
130 rphy->identify.target_port_protocols = dev->tproto; in sas_fill_in_rphy()
136 rphy->identify.device_type = SAS_END_DEVICE; in sas_fill_in_rphy()
139 rphy->identify.device_type = SAS_EDGE_EXPANDER_DEVICE; in sas_fill_in_rphy()
142 rphy->identify.device_type = SAS_FANOUT_EXPANDER_DEVICE; in sas_fill_in_rphy()
145 rphy->identify.device_type = SAS_PHY_UNUSED; in sas_fill_in_rphy()
156 phy->identify.device_type = SAS_END_DEVICE; in sas_phy_set_target()
158 phy->identify.device_type = dev->dev_type; in sas_phy_set_target()
159 phy->identify.target_port_protocols = dev->tproto; in sas_phy_set_target()
[all …]
Dsas_phy.c166 phy->phy->identify.initiator_port_protocols = in sas_register_phys()
168 phy->phy->identify.target_port_protocols = phy->tproto; in sas_register_phys()
169 phy->phy->identify.sas_address = SAS_ADDR(sas_ha->sas_addr); in sas_register_phys()
170 phy->phy->identify.phy_identifier = i; in sas_register_phys()
Dsas_host_smp.c50 resp_data[12] = rphy->identify.device_type << 4; in sas_host_smp_discover()
51 resp_data[14] = rphy->identify.initiator_port_protocols; in sas_host_smp_discover()
52 resp_data[15] = rphy->identify.target_port_protocols; in sas_host_smp_discover()
160 if (rphy->identify.target_port_protocols != SAS_PROTOCOL_SATA) in sas_report_phy_sata()
Dsas_expander.c273 phy->phy->identify.sas_address = SAS_ADDR(phy->attached_sas_addr); in sas_set_ex_phy()
274 phy->phy->identify.device_type = dr->attached_dev_type; in sas_set_ex_phy()
275 phy->phy->identify.initiator_port_protocols = phy->attached_iproto; in sas_set_ex_phy()
276 phy->phy->identify.target_port_protocols = phy->attached_tproto; in sas_set_ex_phy()
278 phy->phy->identify.target_port_protocols = SAS_PROTOCOL_SATA; in sas_set_ex_phy()
279 phy->phy->identify.phy_identifier = phy_id; in sas_set_ex_phy()
2150 type = rphy->identify.device_type; in sas_smp_handler()
Dsas_discover.c141 rphy->identify.phy_identifier = phy->phy->identify.phy_identifier; in sas_get_port_device()
Dsas_scsi_host.c872 BUG_ON(dev->rphy->identify.device_type != SAS_END_DEVICE); in sas_slave_configure()
/linux-4.4.14/drivers/scsi/mpt3sas/
Dmpt3sas_transport.c141 struct sas_identify *identify) in _transport_set_identify() argument
171 memset(identify, 0, sizeof(struct sas_identify)); in _transport_set_identify()
175 identify->sas_address = le64_to_cpu(sas_device_pg0.SASAddress); in _transport_set_identify()
178 identify->phy_identifier = sas_device_pg0.PhyNum; in _transport_set_identify()
183 identify->device_type = SAS_PHY_UNUSED; in _transport_set_identify()
186 identify->device_type = SAS_END_DEVICE; in _transport_set_identify()
189 identify->device_type = SAS_EDGE_EXPANDER_DEVICE; in _transport_set_identify()
192 identify->device_type = SAS_FANOUT_EXPANDER_DEVICE; in _transport_set_identify()
198 identify->initiator_port_protocols |= SAS_PROTOCOL_SSP; in _transport_set_identify()
200 identify->initiator_port_protocols |= SAS_PROTOCOL_STP; in _transport_set_identify()
[all …]
Dmpt3sas_base.h580 struct sas_identify identify; member
/linux-4.4.14/drivers/message/fusion/
Dmptsas.c110 static void mptsas_parse_device_info(struct sas_identify *identify,
389 if (port_info->phy_info[i].identify.handle == handle) { in mptsas_find_portinfo_by_handle()
419 if (port_info->phy_info[i].identify.sas_address == in mptsas_find_portinfo_by_sas_address()
600 if (rphy->identify.sas_address == sas_address) { in mptsas_add_device_component()
766 rphy->identify.sas_address); in mptsas_add_device_component_starget()
1421 struct sas_identify identify; in mptsas_add_end_device() local
1465 mptsas_parse_device_info(&identify, &phy_info->attached); in mptsas_add_end_device()
1474 rphy->identify = identify; in mptsas_add_end_device()
1761 rphy->identify.sas_address) in mptsas_target_alloc()
1820 rphy->identify.sas_address) in mptsas_target_destroy()
[all …]
Dmptsas.h166 struct mptsas_devinfo identify; /* point to phy device info */ member
/linux-4.4.14/drivers/scsi/
Dscsi_transport_sas.c164 BUG_ON(rphy->identify.device_type != SAS_END_DEVICE); in sas_bitfield_name_search()
554 if (!phy->identify.device_type) in show_sas_device_type()
556 return get_sas_device_type_names(phy->identify.device_type, buf); in show_sas_device_type()
639 sas_phy_protocol_attr(identify.initiator_port_protocols,
641 sas_phy_protocol_attr(identify.target_port_protocols,
643 sas_phy_simple_attr(identify.sas_address, sas_address, "0x%016llx\n",
645 sas_phy_simple_attr(identify.phy_identifier, phy_identifier, "%d\n", u8);
1205 if (!rphy->identify.device_type) in show_sas_rphy_device_type()
1208 rphy->identify.device_type, buf); in show_sas_rphy_device_type()
1253 sas_rphy_protocol_attr(identify.initiator_port_protocols,
[all …]
Dhpsa.c9268 struct sas_identify *identify; in hpsa_sas_port_add_phy() local
9273 identify = &phy->identify; in hpsa_sas_port_add_phy()
9274 memset(identify, 0, sizeof(*identify)); in hpsa_sas_port_add_phy()
9275 identify->sas_address = hpsa_sas_port->sas_address; in hpsa_sas_port_add_phy()
9276 identify->device_type = SAS_END_DEVICE; in hpsa_sas_port_add_phy()
9277 identify->initiator_port_protocols = SAS_PROTOCOL_STP; in hpsa_sas_port_add_phy()
9278 identify->target_port_protocols = SAS_PROTOCOL_STP; in hpsa_sas_port_add_phy()
9301 struct sas_identify *identify; in hpsa_sas_port_add_rphy() local
9303 identify = &rphy->identify; in hpsa_sas_port_add_rphy()
9304 identify->sas_address = hpsa_sas_port->sas_address; in hpsa_sas_port_add_rphy()
[all …]
D53c700.scr184 ; Receive a message. Need to identify the message to
D53c700_d.h_shipped247 ; Receive a message. Need to identify the message to
/linux-4.4.14/include/scsi/
Dscsi_transport_sas.h54 struct sas_identify identify; member
86 struct sas_identify identify; member
225 return rphy->identify.device_type == SAS_FANOUT_EXPANDER_DEVICE || in scsi_is_sas_expander_device()
226 rphy->identify.device_type == SAS_EDGE_EXPANDER_DEVICE; in scsi_is_sas_expander_device()
/linux-4.4.14/Documentation/devicetree/bindings/leds/
Dleds-powernv.txt12 - led-types : Supported LED types (attention/identify/fault) provided
22 led-types = "identify", "fault";
Dcommon.txt18 name (excluding the unit address). It has to uniquely identify
/linux-4.4.14/drivers/net/ethernet/intel/
DKconfig32 to identify the adapter.
49 adapters. For more information on how to identify your adapter, go
74 identify your adapter, go to the Adapter & Driver ID Guide at:
94 adapters. For more information on how to identify your adapter, go
135 information on how to identify your adapter, go to the Adapter &
157 instead. For more information on how to identify your adapter, go
180 adapters. For more information on how to identify your adapter, go
236 Intel(R) ixgbe driver. For more information on how to identify your
259 devices. For more information on how to identify your adapter, go
309 For more information on how to identify your adapter, go to the
[all …]
/linux-4.4.14/drivers/block/mtip32xx/
Dmtip32xx.c1305 *timeout = ((*(dd->port->identify + 90) * 2) * 60000); in mtip_set_timeout()
1307 *timeout = ((*(dd->port->identify + 89) * 2) * 60000); in mtip_set_timeout()
1362 memset(port->identify, 0, sizeof(u16) * ATA_ID_WORDS); in mtip_get_identify()
1384 ata_swap_string(port->identify + 27, 40); /* model string*/ in mtip_get_identify()
1385 ata_swap_string(port->identify + 23, 8); /* firmware string*/ in mtip_get_identify()
1386 ata_swap_string(port->identify + 10, 20); /* serial# string*/ in mtip_get_identify()
1391 port->identify[i] = le16_to_cpu(port->identify[i]); in mtip_get_identify()
1396 if (port->identify[128] & 0x4) in mtip_get_identify()
1403 if (port->identify[69] & (1 << 14) && port->identify[69] & (1 << 5)) in mtip_get_identify()
1415 port->identify, in mtip_get_identify()
[all …]
Dmtip32xx.h406 u16 *identify; member
/linux-4.4.14/arch/mips/dec/prom/
DMakefile6 lib-y += init.o memory.o cmdline.o identify.o console.o
/linux-4.4.14/arch/mips/fw/arc/
DMakefile5 lib-y += cmdline.o env.o file.o identify.o init.o \
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dplda,xpressrich3-axi.txt9 - compatible: should contain "plda,xpressrich3-axi" to identify the IP used.
Dversatile.txt6 - compatible: should contain "arm,versatile-pci" to identify the Versatile PCI
Ddesignware-pcie.txt4 - compatible: should contain "snps,dw-pcie" to identify the core.
Dxgene-pci.txt5 - compatible: should contain "apm,xgene-pcie" to identify the core.
Dxgene-pci-msi.txt5 - compatible: should be "apm,xgene1-msi" to identify
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Dcdns,uart.txt9 - clock-names: Tuple to identify input clocks, must contain "uart_clk" and "pclk"
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-devices-sun13 So reading the sysfs file, we can identify a physical position
Dsysfs-devices-memory19 identify removable sections of the memory before attempting
Dsysfs-bus-fcoe109 used to identify the discovered FCF. FCFs will exist in a
Dconfigfs-usb-gadget-uvc219 guidFormat - globally unique id used to identify
/linux-4.4.14/arch/arm/boot/dts/
Darmada-370-seagate-personal-cloud.dts14 * Here are some information allowing to identify the device:
Darmada-370-seagate-nas-2bay.dts14 * Here are some information allowing to identify the device:
Darmada-370-seagate-personal-cloud-2bay.dts14 * Here are some information allowing to identify the device:
Darmada-370-seagate-nas-4bay.dts14 * Here are some information allowing to identify the device:
/linux-4.4.14/drivers/mcb/
DKconfig12 FPGA based devices. It is used to identify MCB based IP-Cores within
/linux-4.4.14/drivers/android/
DKconfig19 Android process, using Binder to identify, invoke and pass arguments
/linux-4.4.14/Documentation/devicetree/bindings/thermal/
Dqcom-spmi-temp-alarm.txt5 interrupt signal and status register to identify high PMIC die temperature.
Dthermal.txt37 to identify uniquely the sensor instances within
/linux-4.4.14/Documentation/hwmon/
Dltc415124 which can be safely used to identify the chip. You will have to instantiate
Dltc426025 which can be safely used to identify the chip. You will have to instantiate
Dads782856 There is no reliable way to identify this chip, so the driver will not scan
Dlineage-pem30 which can be safely used to identify the chip. You will have to instantiate
Dltc426125 which can be safely used to identify the chip. You will have to instantiate
Dltc294525 which can be safely used to identify the chip. You will have to instantiate
Dmax1606561 can be safely used to identify the chip. You will have to instantiate
Dsmm66562 can be safely used to identify the chip. You will have to instantiate
Dpmbus-core173 int (*identify)(struct i2c_client *client, struct pmbus_driver_info *info);
240 identify function if supported. Must only be called from device probe
Dpmbus60 which can be safely used to identify the chip (The MFG_ID register is not
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dti,keystone-irq.txt5 The IRQ handler running on HOST OS can identify DSP signal source by
/linux-4.4.14/Documentation/networking/
Di40evf.txt25 For more information on how to identify your adapter, go to the Adapter &
Dixgbevf.txt30 For more information on how to identify your adapter, go to the Adapter &
Digbvf.txt44 For more information on how to identify your adapter, go to the Adapter &
Dtproxy.txt12 The idea is that you identify packets with destination address matching a local
Di40e.txt23 For more information on how to identify your adapter, go to the Adapter &
Digb.txt20 For specific information on how to identify your adapter, go to the Adapter &
Ds2io.txt31 The above messages identify the adapter type(Xframe I/II), adapter revision,
De100.txt39 For more information on how to identify your adapter, go to the Adapter &
De1000e.txt25 For more information on how to identify your adapter, go to the Adapter &
Drds.txt29 RDS uses IPv4 addresses and 16bit port numbers to identify
Dopenvswitch.txt123 identify the flow for all future operations. However, when reporting the
Dixgbe.txt23 For more information on how to identify your adapter, go to the Adapter &
Dixgb.txt60 For more information on how to identify your adapter, go to the Adapter &
De1000.txt19 For more information on how to identify your adapter, go to the Adapter &
Dcs89x0.txt251 identify the card. This could be dangerous if you are
Darcnet-hardware.txt1708 used a memory dump in DOS to identify them. For the 00000 configuration and
1907 This is another SMC 90C65-based ARCnet card. I couldn't identify the
Dcan.txt224 layer problems is a vital requirement for CAN users to identify
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dingenic,cgu.txt17 Clock consumers specify this argument to identify a clock. The valid values
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-opal.txt12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/
Daltera-mailbox.txt8 - #mbox-cells: Common mailbox binding property to identify the number
Domap-mailbox.txt46 - #mbox-cells: Common mailbox binding property to identify the number
/linux-4.4.14/drivers/pcmcia/
Di82365.c572 static int __init identify(unsigned int port, u_short sock) in identify() function
791 id = identify(i365_base, 0); in isa_probe()
792 if ((id == IS_I82365DF) && (identify(i365_base, 1) != id)) { in isa_probe()
797 if (identify(port, sock) == IS_I82365DF) { in isa_probe()
808 id = identify(port, sock); in isa_probe()
813 if ((ignore == i+j) || (identify(port, sock+j) < 0)) in isa_probe()
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Dpar_io.txt34 - gpio-controller : node to identify gpio controllers.
/linux-4.4.14/Documentation/misc-devices/
Disl2900330 The ISL29003 does not have an ID register which could be used to identify
/linux-4.4.14/security/smack/
DKconfig26 identify which rules are necessary and what accesses
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dprimecell.txt4 identify the peripheral type, vendor, and revision. This value can be used for
/linux-4.4.14/drivers/eisa/
DKconfig10 Bus (VLB) card that identify itself as an EISA card (such as
/linux-4.4.14/certs/
DKconfig10 the URI should identify, both the certificate and its corresponding
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dwakeup-source.txt13 then they need to specify/identify the same using device specific
/linux-4.4.14/drivers/hwmon/pmbus/
Dpmbus.c177 info->identify = pmbus_identify; in pmbus_probe()
Dpmbus.h380 int (*identify)(struct i2c_client *client, member
Dpmbus_core.c1761 if (info->identify) { in pmbus_init_common()
1762 ret = (*info->identify)(client, info); in pmbus_init_common()
/linux-4.4.14/Documentation/devicetree/bindings/arm/msm/
Dqcom,saw2.txt15 or Little) or cache, may be needed to uniquely identify the SAW register
/linux-4.4.14/Documentation/
Dmen-chameleon-bus.txt109 Each MCB driver has a structure to identify the device driver as well as
110 device ids which identify the IP Core inside the FPGA. The driver structure
DSAK.txt51 You can identify processes which will be killed by SAK with the
Dmodule-signing.txt97 The string provided should identify a file containing both a private key
Dvme_api.txt102 of type vme_resource that should be used to identify the allocated resource
Dpinctrl.txt474 identify three pinmux functions, one for spi, one for i2c and one for mmc.
510 name. Defining a pin controller, function and group thus uniquely identify
978 software engineers will usually quickly identify that this is some
Dvfio.txt84 of functionality. To do this, the user first needs to identify the
DSubmittingPatches636 The "subsystem" in the email's Subject should identify which
/linux-4.4.14/drivers/scsi/mvsas/
Dmv_sas.c265 id->dev_type = phy->identify.device_type; in mvs_bytes_dmaed()
267 id->target_bits = phy->identify.target_port_protocols; in mvs_bytes_dmaed()
1033 phy->identify.target_port_protocols = SAS_PROTOCOL_STP; in mvs_update_phyinfo()
1058 phy->identify.device_type = in mvs_update_phyinfo()
1061 if (phy->identify.device_type == SAS_END_DEVICE) in mvs_update_phyinfo()
1062 phy->identify.target_port_protocols = in mvs_update_phyinfo()
1064 else if (phy->identify.device_type != SAS_PHY_UNUSED) in mvs_update_phyinfo()
1065 phy->identify.target_port_protocols = in mvs_update_phyinfo()
Dmv_sas.h222 struct sas_identify identify; member
/linux-4.4.14/tools/perf/Documentation/
Dintel-bts.txt8 similarities because it can also identify every branch a program takes. A
Dperf-report.txt148 A regex filter to identify parent. The parent is a caller of this
/linux-4.4.14/Documentation/sound/oss/
DSoundblaster53 The driver will identify the audio device as a "Sound Blaster 16 (ALS-100)".
DALS22 When using kernel level ISAPnP, the kernel should correctly identify and
DSoundPro25 mis-identify the chip. You can still force soundpro=1 in the modprobe
DOpti174 to all C931 based cards. I do not know how to identify cards that
DREADME.OSS299 systems to easily identify and reconfigure I/O ports, IRQs and DMAs of ISA
1296 to look at the card and try to identify its origin.
/linux-4.4.14/arch/unicore32/kernel/
Dhead.S67 @ process identify
/linux-4.4.14/Documentation/devicetree/bindings/
Dsubmitting-patches.txt15 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
/linux-4.4.14/Documentation/power/
Dbasic-pm-debugging.txt37 identify what goes wrong.
102 it usually is possible to identify the offending task by analysing the output of
196 you to identify drivers that fail to suspend or resume their devices. They
Dswsusp-and-swap-files.txt17 identify a swap file swsusp uses the name of the partition that holds the file
Dopp.txt339 struct device - This is used to identify a domain to the OPP layer. The
Ddevices.txt383 system is in the sleep state. For example, enable_irq_wake() might identify
Dpci.txt232 in turn, allows the kernel to identify the source of the event (that may be
/linux-4.4.14/Documentation/usb/
Dfunctionfs.txt49 On kernel level the gadget checks ffs_data->dev_name to identify
Dehci.txt123 The contents of those files can help identify driver problems.
Dusbmon.txt111 - URB Tag. This is used to identify URBs, and is normally an in-kernel address
Dproc_usb_info.txt186 | be omitted, or (for newer drivers) will identify the kernel
/linux-4.4.14/Documentation/devicetree/bindings/opp/
Dopp.txt51 identify the OPP tables.
59 tables are present), to uniquely identify them. The same list must be present
/linux-4.4.14/Documentation/filesystems/
Dxfs-self-describing-metadata.txt41 is supposed to be. We can't even identify if it is the right place. Put simply,
61 location. This allows us to identify the expected contents of the block and
62 hence parse and verify the metadata object. IF we can't independently identify
116 looking at. The owner information can also identify misplaced writes (e.g.
Dqnx6.txt37 That serial number is used to identify the "active" superblock.
Dromfs.txt76 The first eight bytes identify the filesystem, even for the casual
Daffs.txt74 identify itself as one. This option is necessary if
Dautofs4-mount-control.txt294 also sets the process group id used to identify the controlling process
371 ioctlfd field to identify a specific mount point to check while the other
Dcoda.txt410 unique number which will identify the message uniquely. A process and
443 The next item is the fundamental identifier used to identify Coda
461 to be prefixed to identify the Coda cell; this will probably take the
Dporting170 number is not sufficient to identify the actual file object. 'set'
Df2fs.txt577 In order to identify whether the data in the victim segment are valid or not,
DLocking154 identify the superblock. Everything else (statfs(), fstatfs(), etc.)
Dproc.txt1044 identify device identify block
1291 lines. These numbers identify the amount of time the CPU has spent performing
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DSuspend.txt130 identify any faults with better precision
/linux-4.4.14/Documentation/acpi/
Dgpio-properties.txt62 available to the driver can be used to identify the device and that is supposed
Denumeration.txt394 property to identify the corresponding device in analogy with the original DT
/linux-4.4.14/drivers/ssb/
DKconfig97 Note that you won't be able to identify problems, once
/linux-4.4.14/Documentation/i2c/
Dwriting-clients201 identify supported devices (returning 0 for supported ones and -ENODEV
213 devices. You need some reliable way to identify the supported devices
218 alone a standard way to identify devices. Even worse is the lack of
Dinstantiating-devices224 segment, the address is sufficient to uniquely identify the device to be
/linux-4.4.14/Documentation/trace/
Dstm.txt55 trace data into its file descriptor. In order to identify themselves
Devents-kmem.txt24 kmalloc with kfree, it may be possible to identify memory leaks and where
Dtracepoint-analysis.txt218 There may also be a requirement to identify what functions within a program
Dcoresight.txt196 Before trace collection can start, a coresight sink needs to be identify.
/linux-4.4.14/Documentation/filesystems/nfs/
Drpc-cache.txt21 - mapping from network identify to public key for crypto authentication.
100 This will be passed to ->match to identify the target entry. If no
Dnfs.txt22 NFSv4 requires clients to identify themselves to servers with a unique
/linux-4.4.14/drivers/net/ethernet/intel/ixgbe/
Dixgbe_82598.c129 phy->ops.identify(hw); in ixgbe_init_phy_ops_82598()
1216 .identify = &ixgbe_identify_phy_generic,
Dixgbe_x550.c1995 ret_val = phy->ops.identify(hw); in ixgbe_init_phy_ops_X550em()
2443 .identify = &ixgbe_identify_phy_generic,
2449 .identify = &ixgbe_identify_phy_x550em,
Dixgbe_x540.c874 .identify = &ixgbe_identify_phy_generic,
Dixgbe_82599.c317 ret_val = phy->ops.identify(hw); in ixgbe_init_phy_ops_82599()
2245 .identify = &ixgbe_identify_phy_82599,
Dixgbe_common.c284 hw->phy.ops.identify(hw); in ixgbe_start_hw_generic()
475 hw->phy.ops.identify(hw); in ixgbe_clear_hw_cntrs_generic()
Dixgbe_type.h3316 s32 (*identify)(struct ixgbe_hw *); member
/linux-4.4.14/drivers/scsi/pm8001/
Dpm8001_hwi.c3249 id->dev_type = phy->identify.device_type; in pm8001_bytes_dmaed()
3251 id->target_bits = phy->identify.target_port_protocols; in pm8001_bytes_dmaed()
3411 phy->identify.device_type = deviceType; in hw_event_sas_phy_up()
3413 if (phy->identify.device_type == SAS_END_DEVICE) in hw_event_sas_phy_up()
3414 phy->identify.target_port_protocols = SAS_PROTOCOL_SSP; in hw_event_sas_phy_up()
3415 else if (phy->identify.device_type != SAS_PHY_UNUSED) in hw_event_sas_phy_up()
3416 phy->identify.target_port_protocols = SAS_PROTOCOL_SMP; in hw_event_sas_phy_up()
3468 phy->identify.target_port_protocols = SAS_PROTOCOL_SATA; in hw_event_sata_phy_up()
3469 phy->identify.device_type = SAS_SATA_DEV; in hw_event_sata_phy_up()
3496 phy->identify.device_type = 0; in hw_event_phy_down()
Dpm80xx_hwi.c2948 phy->identify.device_type = deviceType; in hw_event_sas_phy_up()
2950 if (phy->identify.device_type == SAS_END_DEVICE) in hw_event_sas_phy_up()
2951 phy->identify.target_port_protocols = SAS_PROTOCOL_SSP; in hw_event_sas_phy_up()
2952 else if (phy->identify.device_type != SAS_PHY_UNUSED) in hw_event_sas_phy_up()
2953 phy->identify.target_port_protocols = SAS_PROTOCOL_SMP; in hw_event_sas_phy_up()
3008 phy->identify.target_port_protocols = SAS_PROTOCOL_SATA; in hw_event_sata_phy_up()
3009 phy->identify.device_type = SAS_SATA_DEV; in hw_event_sata_phy_up()
3037 phy->identify.device_type = 0; in hw_event_phy_down()
Dpm8001_sas.h255 struct sas_identify identify; member
Dpm8001_sas.c627 dev->rphy->identify.phy_identifier; in pm8001_dev_found_notify()
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-st.txt68 - Second Cell: flags to identify the type of the interrupt
Dfsl,mxs-pinctrl.txt50 and config nodes to identify a pin. The mux selection in the integer takes
Dsamsung-pinctrl.txt118 - Second Cell: flags to identify the type of the interrupt
153 - Second Cell: flags to identify the type of the interrupt
/linux-4.4.14/include/linux/
Dnvme.h524 struct nvme_identify identify; member
/linux-4.4.14/Documentation/blockdev/
Dparide.txt99 the adapter chip itself. That's usually sufficient to identify the
141 how to identify them. This requires specifying the port address, the
153 will need them to identify the devices.
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dfman.txt37 The cell-index value may be used by the SoC, to identify the
249 identify the MAC unit in the FMan (or SoC) memory map.
/linux-4.4.14/Documentation/input/
Dalps.txt22 (Compatibility ID) definition as a way to uniquely identify the
218 identify the first fragment of a bitmap packet.
Dgamepad.txt64 an alias for BTN_SOUTH/BTN_A. It can be used to identify a gamepad as such.
Dmulti-touch-protocol.txt68 Some devices identify and/or track more contacts than they can report to the
Dsentelic.txt71 so we have PACKET NUMBER to identify packets.
/linux-4.4.14/Documentation/locking/
Dlockdep-design.txt279 identify the leaking lock classes:
284 a later run of this command to identify the leakers. This same output
/linux-4.4.14/drivers/s390/char/
DKconfig110 The Component ID for Call Home is used to identify the correct
/linux-4.4.14/Documentation/video4linux/
Dsi4713.txt13 The chip also allows integrated receive power scanning to identify low signal
/linux-4.4.14/Documentation/target/
Dtcmu-design.txt201 <subtype> will be a userspace-process-unique string to identify the
222 number. This should allow userspace to identify both the UIO device and
/linux-4.4.14/arch/arm/plat-samsung/
DKconfig278 the CRC data block will take more memory, but wil identify any
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic7xxx.seq193 * Setup the DMA for sending the identify and
267 * immediately follow the identify. We test for a valid
456 * sending our identify messages.
462 * Start out with a simple identify message.
1485 * This is done to allow the host to send messages outside of an identify
1519 mov SCSIDATL, SINDEX; /* Send the identify message */
1634 * If the target never sent an identify message but instead went
Daic7xxx.h625 uint8_t identify; /* Identify message */ member
Daic79xx.h679 uint8_t identify; /* Identify message */ member
Daic79xx.seq960 * This is done to allow the host to send messages outside of an identify
990 mov SCSIDAT, SINDEX; /* Send the identify message */
1197 * If the target never sent an identify message but instead went
Daic7xxx_core.c7871 lun = (cmd->identify & MSG_IDENTIFY_LUNMASK); in ahc_handle_target_cmd()
7952 if ((cmd->identify & MSG_IDENTIFY_DISCFLAG) == 0) { in ahc_handle_target_cmd()
Daic79xx_core.c10722 lun = (cmd->identify & MSG_IDENTIFY_LUNMASK); in ahd_handle_target_cmd()
10802 if ((cmd->identify & MSG_IDENTIFY_DISCFLAG) == 0) { in ahd_handle_target_cmd()
/linux-4.4.14/fs/
DKconfig.binfmt57 identify the build ID bits in the file, without paying the i/o
/linux-4.4.14/Documentation/fb/
Dudlfb.txt13 result with a local shadow of the remote hardware framebuffer to identify
/linux-4.4.14/Documentation/device-mapper/
Dstatistics.txt84 so that userspace programs can identify the ranges they
/linux-4.4.14/sound/core/
DKconfig218 will help to identify source file and position containing
/linux-4.4.14/Documentation/powerpc/
Dcxlflash.txt151 to uniquely identify the context and its allocated resources. The
318 identify each LUN by its World Wide Node Name (WWNN).
Dfirmware-assisted-dump.txt183 This interface can be used by kdump init scripts to identify if
/linux-4.4.14/fs/reiserfs/
DREADME18 It will be a kindness if you identify whether Hans Reiser is allowed
/linux-4.4.14/Documentation/devicetree/
Dusage-model.txt97 First and foremost, the kernel will use data in the DT to identify the
101 Hardware is not perfect though, and so the kernel must identify the
/linux-4.4.14/Documentation/vm/
Dtranshuge.txt201 identify what applications are using transparent huge pages, it is
264 using the mm_page_alloc tracepoint to identify which allocations were
/linux-4.4.14/Documentation/scsi/
Dscsi_fc_transport.txt135 is registered with the switch to identify the vport. For example,
138 to identify the port.
DChangeLog.megaraid297 identify each controller.
Dncr53c8xx.txt359 revision ID identify the SCSI chip as follows:
/linux-4.4.14/drivers/nvme/host/
Dpci.c1207 c.identify.opcode = nvme_admin_identify; in nvme_identify_ctrl()
1208 c.identify.cns = cpu_to_le32(1); in nvme_identify_ctrl()
1228 c.identify.opcode = nvme_admin_identify, in nvme_identify_ns()
1229 c.identify.nsid = cpu_to_le32(nsid), in nvme_identify_ns()
/linux-4.4.14/Documentation/s390/
Ddriver-model.txt195 intparm - the intparm which allows the device driver to identify
/linux-4.4.14/Documentation/ia64/
Dmca.txt177 How do we identify the tasks that were running when MCA/INIT was
/linux-4.4.14/Documentation/block/
Ddata-integrity.txt278 'tag_size' must be set to identify how many bytes of tag space
/linux-4.4.14/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt139 to identify which mapping was used for the values within the option.
615 the system administrator to identify tag types that may safely be
/linux-4.4.14/Documentation/isdn/
DINTERFACE.CAPI95 identify the controller to operate on.
/linux-4.4.14/Documentation/gpio/
Ddriver.txt34 identify GPIOs in a bank of I2C GPIO expanders.
Dgpio-legacy.txt108 use numbers 2000-2063 to identify GPIOs in a bank of I2C GPIO expanders.
/linux-4.4.14/drivers/staging/unisys/Documentation/
Doverview.txt169 * Virtual bus numbers uniquely identify s-Par back-end service partitions.
/linux-4.4.14/drivers/acpi/
DKconfig128 and can be used to identify ACPI code or EC firmware bugs.
/linux-4.4.14/Documentation/rapidio/
Drapidio.txt272 management notification mechanism to identify a device that is reporting an
/linux-4.4.14/Documentation/thermal/
Dsysfs-api.txt466 thermal zone device will be used in the message to identify the zone. The
/linux-4.4.14/Documentation/ioctl/
Dhdio.txt260 This information is also available from /proc/ide/hdX/identify
/linux-4.4.14/arch/arm64/
DKconfig639 identify software that needs updating.
/linux-4.4.14/Documentation/development-process/
D2.Process221 and other metadata. At any given time, the maintainer can identify which
/linux-4.4.14/Documentation/spi/
Dspi-summary187 those /sys/class entries are only useful to quickly identify busses.
/linux-4.4.14/Documentation/sysctl/
Dvm.txt573 invoked, to identify the rogue task that caused it, and to determine why
/linux-4.4.14/Documentation/cgroups/
Dunified-hierarchy.txt68 of controllers which exist only to identify membership, which in turn
/linux-4.4.14/Documentation/security/
DSmack.txt565 and a category set with each packet. The DOI is intended to identify a group
/linux-4.4.14/drivers/staging/speakup/
Dspkguide.txt1243 Invariant Sections. If the Document does not identify any Invariant
1321 the back cover. Both covers must also clearly and legibly identify
/linux-4.4.14/Documentation/x86/
Dboot.txt699 to identify the contents of data; the len is the length of data
/linux-4.4.14/Documentation/kbuild/
Dmakefiles.txt661 additional line can be used to identify this.
/linux-4.4.14/lib/
DKconfig.debug389 identify kernel problems.

12