Home
last modified time | relevance | path

Searched full:discover (Results 1 – 25 of 351) sorted by relevance

12345678910>>...15

/freebsd/sys/dev/isci/scil/
H A Dscif_sas_smp_remote_device.c164 * continue the smp discover process.
232 //decode discover response in scif_sas_smp_remote_device_decode_smp_response()
240 //decode discover response as a polling result for a remote device in scif_sas_smp_remote_device_decode_smp_response()
250 //decode discover response in scif_sas_smp_remote_device_decode_smp_response()
284 //decode discover response as a polling result for a remote device in scif_sas_smp_remote_device_decode_smp_response()
329 * and then continue the smp discover process.
408 * @brief This method decodes a smp Discover response to this smp device
409 * and then continue the smp discover process. This is only ever
410 * called for the very first discover stage during a given domain
413 * @param[in] fw_device The framework device that the DISCOVER command
[all …]
H A Dscif_domain.h94 * on which to discover devices.
109 * @brief This method will attempt to discover the supplied domain.
124 * on which to discover devices.
135 * @return Indicate if the discover operation started successfully.
136 * @retval SCI_SUCCESS This value is returned if the discover operation
171 * @param[in] domain The handle to the domain whose discover activity is to
174 * @return The suggested timeout value for domain discover in milli-seconds.
H A Dscif_sas_domain.c111 "Domain:0x%x State:0x%x DISCOVER timeout!\n", in scif_sas_domain_operation_timeout_handler()
253 // The status of the discover operation takes priority. in scif_domain_discover()
427 //if there is smp device on this domain that is in the middle of discover in scic_cb_port_bc_change_primitive_recieved()
791 //kick off the smp discover process if this expander is direct attached. in scif_sas_domain_remote_device_start_complete()
794 //mark this device, the discover process of this device will start after in scif_sas_domain_remote_device_start_complete()
795 //its containing smp device finish discover. in scif_sas_domain_remote_device_start_complete()
810 * least one smp device in discover or target reset activity, this
963 //config route table activity has higher priority than discover activity. in scif_sas_domain_find_device_has_scheduled_activity()
991 * is_discover_scheduled and start the smp discover process on them.
993 * @param[in] fw_domain The framework domain that to start smp discover process.
[all …]
H A Dscif_sas_smp_phy.h111 * This field records the attached sas address, retrieved from a DISCOVER
117 * This field records the attached device type, retrieved from a DISCOVER
123 * This field records the routing attribute, retrieved from a DISCOVER
130 * DISCOVER response.
136 * route table activity on a smp phy within one DISCOVER process.
H A Dscif_sas_design.h314 smp request for expander device discover process, or stp request for NCQ
333 its SMP discover activities. The discover procedure includes a initial discover
338 @image latex Discover Process.eps "SMP Discover Activity Diagram" width=10cm
339 @image html Discover Process.jpg "SMP Discover Activity Diagram"
H A Dscif_sas_smp_io_request.c278 * @brief construct a smp Discover command to the fw_device.
280 * @param[in] fw_device the framework smp device that DISCOVER command targets
282 * @param[in] phy_identifier The phy index the DISCOVER command targets to.
303 smp_discover.request.discover.phy_identifier = phy_identifier; in scif_sas_smp_request_construct_discover()
308 "SMP DISCOVER - Device:0x%x PhyId:0x%x\n", in scif_sas_smp_request_construct_discover()
322 * @param[in] fw_device the framework smp device that DISCOVER command targets
324 * @param[in] phy_identifier The phy index the DISCOVER command targets to.
362 * @param[in] phy_identifier The phy index the DISCOVER command targets to.
H A Dscif_sas_smp_remote_device.h127 * This field indicates a smp device is either in the middle of normal discover
134 * DISCOVER request.
146 * since a DISCOVER process starts.
172 * to be started (not yet). The scheduled activity could be Discover or Config
179 * sending Discover request after Phy Control during Target Reset.
H A Dscif_sas_smp_phy.c131 * @brief This routine save a smp phy information based on discover response.
136 * @param[in] discover_response The smp DISCOVER response for this_smp_phy.
162 //the attached expander finish its discover on attached_phy. in scif_sas_smp_phy_save_information()
171 * @param[in] discover_response The smp DISCOVER response for this_smp_phy.
H A Dscif_sas_domain_state_handlers.c63 * - The discover method must be synchronized with the
111 * when a user attempts to discover a domain.
114 * on which the user is attempting to perform a discover
117 * @return This method returns an indication of whether the discover operation
119 * @retval SCI_SUCCESS This value is returned when the discover operation
466 // a smp Phy Control or Discover request sent to parent device of in scif_sas_domain_ready_start_high_priority_io_handler()
987 * a task on a domain in DISCOVER state, only hard reset is allowed.
1017 //If the domain is in the middle of smp DISCOVER process, in scif_sas_domain_discovering_start_task_handler()
1085 * when a user attempts to discover a domain and a discovery
1089 * on which the user is attempting to perform an discover
[all …]
H A Dintel_sas.h393 * @brief This structure depicts the contents of the SAS SMP DISCOVER
528 SMP_REQUEST_PHY_IDENTIFIER_T discover; member
661 * @brief This structure depicts the discover response where the
693 * @brief This structure defines the SMP phy discover response format.
903 SMP_RESPONSE_DISCOVER_T discover; member
H A Dscif_sas_remote_device.c550 //from discover response. in scif_sas_remote_device_save_report_phy_sata_information()
670 //if the domain is in the DISCOVER state, we should resume the DISCOVER. in scif_sas_remote_device_target_reset_complete()
683 //Tell driver to kick off Discover process. If the domain is already in scif_sas_remote_device_target_reset_complete()
692 //Tell driver to kick off Discover process. If the domain is already in scif_sas_remote_device_target_reset_complete()
H A Dsci_base_domain.h122 * discover what remote devices are contained in it. In this state no
207 * to discover a domain.
/freebsd/contrib/ofed/libibnetdisc/man/
H A Dibnd_discover_fabric.315 Discover the fabric connected to the port specified by ibmad_port, using a timeout specified. The …
45 .B Discover the entire fabric connected to device "mthca0", port 1.
54 .B Discover only a single node and those nodes connected to it.
/freebsd/sys/contrib/edk2/Include/Protocol/
H A DPxeBaseCode.h117 // Discover() definitions
167 /// Discover() server list structure.
177 /// Discover() information override structure.
405 Attempts to complete a DHCPv4 D.O.R.A. (discover / offer / request / acknowledge) or DHCPv6
469 …@param Layer The pointer to the boot server layer number to discover, which must …
701 Dhcp(), Discover(), and Mtftp() set the IP filter, and return with the IP receive
840 Updates the contents of the cached DHCP and Discover packets.
858 @param NewDhcpDiscover The pointer to the new cached DHCP Discover packet contents.
861 @param NewPxeDiscover The pointer to the new cached PXE Discover packet contents.
916 EFI_PXE_BASE_CODE_DISCOVER Discover; member
/freebsd/sys/contrib/device-tree/Bindings/connector/
H A Dusb-connector.yaml126 chapter 6.4.4.3.1 Discover Identity. User can specify the VDO array via
137 "USB Power Delivery Specification Revision 2.0, Version 1.3" chapter 6.4.4.3.1 Discover
147 is only necessary if there are no other means to discover supported
153 is only necessary if there are no other means to discover supported
160 discover supported alternative modes (e.g. through the UCSI firmware
180 description: VDO returned by Discover Modes USB PD command.
/freebsd/stand/efi/include/
H A Defi_nii.h68 // and Boot Server discover packets.
75 // Information to be placed into the PXE DHCP and Discover packets.
/freebsd/sys/dev/pms/RefTisa/tisa/sassata/sas/ini/
H A Ditddefs.h42 …_UP_STREAM 1 /**< status indicates discover upstream */
43 …OWN_STREAM 2 /**< status indicates discover downstream */
/freebsd/sys/dev/pms/RefTisa/tisa/sassata/sas/tgt/
H A Dttdsmp.c203 tdSMPFrameHeader.smpFunction = SMP_DISCOVER; /* discover */ in ttdsaDiscoverRespSend()
209 //agSMPFrame->frameHeader.smpFunction = SMP_DISCOVER; /* discover */ in ttdsaDiscoverRespSend()
224 /* temp, hardcode smp discover response */ in ttdsaDiscoverRespSend()
433 TI_DBG1(("ttdsaSMPReqReceived: DISCOVER\n")); in ttdsaSMPReqReceived()
/freebsd/contrib/llvm-project/lld/docs/
H A DPartitions.rst78 In order to allow a program to discover the names of its loadable partitions
97 The program may discover the location of the partition index using the
/freebsd/contrib/ntp/html/
H A Dassoc.html32 …preempted by a &quot;better&quot; server, as described on the <a href="discover.html">Automatic S…
34 …n NTP: broadcast/multicast, manycast and pool described on the <a href="discover.html">Automatic S…
55 …, multicast mode can be used. Additional information is on the <a href="discover.html">Automatic N…
58 …s should one or another fail. Additional information is on the <a href="discover.html">Automatic S…
/freebsd/contrib/ncurses/ncurses/tinfo/
H A Dlib_win32util.c53 character device. But we can discover we are at the end of an
56 For now we terminate the program if we discover that situation.
/freebsd/contrib/ntp/html/scripts/
H A Dconfig.txt3 <li class='inline'><a href='discover.html'>Automatic Server Discovery Schemes</a></li>\
H A Dhand.txt7 <li class='inline'><a href='discover.html'>Automatic Server Discovery Schemes Timekeeping</a></li>\
/freebsd/cddl/contrib/opensolaris/lib/libdtrace/common/
H A Ddrti.c123 dbg_printf(1, "couldn't discover module name or address\n"); in dtrace_dof_init()
129 dbg_printf(1, "couldn't discover link map ID\n"); in dtrace_dof_init()
/freebsd/release/packages/ucl/
H A Dnvme-tools-all.ucl23 and configure NVMe devices connected to the local system, and to discover

12345678910>>...15