Home
last modified time | relevance | path

Searched refs:discovery (Results 1 – 25 of 79) sorted by relevance

1234

/linux/Documentation/driver-api/rapidio/
A Drapidio.rst107 an enumeration and/or discovery routine may be called automatically or
120 discovery methods as statically linked components or loadable modules.
126 several methods to initiate an enumeration and/or discovery process:
128 (a) Statically linked enumeration and discovery process can be started
132 'rio-scan.scan' for existing basic enumeration/discovery method.
197 they must be loaded before enumeration/discovery process starts.
216 When automatic enumeration/discovery start is selected, basic method's
218 discovery for all known mport devices.
221 enumeration/discovery start method may be difficult to use due to the
293 passive discovery of the network.
[all …]
/linux/include/net/bluetooth/
A Dhci_core.h514 struct discovery_state discovery; member
811 INIT_LIST_HEAD(&hdev->discovery.all); in discovery_init()
812 INIT_LIST_HEAD(&hdev->discovery.unknown); in discovery_init()
815 hdev->discovery.rssi = HCI_RSSI_INVALID; in discovery_init()
822 hdev->discovery.rssi = HCI_RSSI_INVALID; in hci_discovery_filter_clear()
823 hdev->discovery.uuid_count = 0; in hci_discovery_filter_clear()
824 kfree(hdev->discovery.uuids); in hci_discovery_filter_clear()
825 hdev->discovery.uuids = NULL; in hci_discovery_filter_clear()
826 hdev->discovery.scan_start = 0; in hci_discovery_filter_clear()
827 hdev->discovery.scan_duration = 0; in hci_discovery_filter_clear()
[all …]
/linux/Documentation/ABI/testing/
A Dsysfs-bus-fcoe14 'start' attribute to begin the kernel's discovery and login
33 discovery and login. The FCoE Controller is destroyed by
46 is started in 'Fabric' mode then FIP FCF discovery is
49 FIP VN2VN discovery and login is performed. A FCoE
A Dsysfs-class-rapidio35 (yet). Normally, before enumeration/discovery have been executed
39 After enumeration or discovery was performed for a given mport device,
A Dsysfs-bus-rapidio128 set by the switch initialization routine during enumeration or discovery
192 (WO) Allows to trigger enumeration discovery process from user
193 space. To initiate an enumeration or discovery process on
199 initiate RapidIO enumeration/discovery on all available mports a
/linux/drivers/rapidio/
A DKconfig23 Amount of time a discovery node waits for a host to complete
67 There are different enumeration and discovery mechanisms offered
77 This option includes basic RapidIO fabric enumeration and discovery
/linux/net/bluetooth/
A Dhci_request.c1151 old_state = hdev->discovery.state; in hci_req_prepare_suspend()
2604 if (req->hdev->discovery.limited) in bredr_inquiry()
2636 hdev->discovery.scan_start = 0; in le_scan_disable_work()
2730 !hdev->discovery.scan_start) in le_scan_restart_work()
2738 duration = hdev->discovery.scan_duration; in le_scan_restart_work()
2739 scan_start = hdev->discovery.scan_start; in le_scan_restart_work()
2836 switch (hdev->discovery.type) { in start_discovery()
2890 hdev->discovery.result_filtering) { in start_discovery()
2891 hdev->discovery.scan_start = jiffies; in start_discovery()
2892 hdev->discovery.scan_duration = timeout; in start_discovery()
[all …]
/linux/Documentation/scsi/
A DChangeLog.lpfc14 discovery lists.
310 discovery) to 32
508 discovery state machine as well.
742 * Expand INFO for discovery sysfs shost entries.
745 * Added initial sysfs discovery shost attributes.
761 discovery.
800 * Fixed misc discovery problems.
804 * Fix discovery NPort to NPort pt2pt problem.
849 * Updates to discovery processing.
1324 discovery state machine running. Fix this by exiting discovery
[all …]
A Dbnx2fc.rst42 discovery and log into the targets.
68 6. Verify the vlan discovery is performed by running ifconfig and notice
/linux/Documentation/arm/
A Dmarvell.rst90 …chive.org/web/20120616194711/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
91 …chive.org/web/20141005120451/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
92 …chive.org/web/20111110081125/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
95 …chive.org/web/20140801121623/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
96 …chive.org/web/20141005120458/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
97 …chive.org/web/20111110081125/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
101 …chive.org/web/20140722064429/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
102 …chive.org/web/20140722064425/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
103 …chive.org/web/20111110081125/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
108 …web.archive.org/web/20110924171043/http://www.marvell.com/embedded-processors/discovery-innovation/
/linux/arch/arm64/boot/dts/qcom/
A Dsdm630-sony-xperia-nile-discovery.dts13 compatible = "sony,discovery-row", "qcom,sdm630";
/linux/include/net/
A Damt.h197 struct amt_header_discovery discovery; member
208 struct amt_header_discovery discovery; member
/linux/drivers/net/wireless/realtek/rtlwifi/rtl8723ae/
A Dfw.c563 p2p_ps_offload->discovery = 0; in rtl8723e_set_p2p_ps_offload_cmd()
568 p2p_ps_offload->discovery = 1; in rtl8723e_set_p2p_ps_offload_cmd()
572 p2p_ps_offload->discovery = 0; in rtl8723e_set_p2p_ps_offload_cmd()
/linux/Documentation/driver-api/driver-model/
A Doverview.rst26 of common callbacks, such as device discovery during bus probing, bus
56 statically allocated. This means only one allocation on device discovery.
107 This directory may be populated at each layer of discovery - the global layer,
/linux/drivers/net/wireless/realtek/rtlwifi/rtl8723be/
A Dfw.c667 p2p_ps_offload->discovery = 0; in rtl8723be_set_p2p_ps_offload_cmd()
672 p2p_ps_offload->discovery = 1; in rtl8723be_set_p2p_ps_offload_cmd()
676 p2p_ps_offload->discovery = 0; in rtl8723be_set_p2p_ps_offload_cmd()
/linux/drivers/nvme/target/
A DMakefile13 discovery.o io-cmd-file.o io-cmd-bdev.o
/linux/drivers/bus/fsl-mc/
A DKconfig14 architecture. The fsl-mc bus driver handles discovery of
/linux/Documentation/admin-guide/aoe/
A Daoe.rst41 however, because AoE discovery takes a few seconds. It can be
117 It's helpful to trigger discovery after setting the list of allowed
145 target based on the order of its discovery. With dynamic minor
/linux/drivers/firmware/smccc/
A DKconfig14 to add SMCCC discovery mechanism though the PSCI firmware
/linux/drivers/staging/r8188eu/include/
A Drtl8188e_cmd.h70 u8 discovery:1; member
/linux/Documentation/ABI/removed/
A Dvideo139410 asynchronous I/O for device discovery and configuration.
/linux/drivers/net/wireless/realtek/rtlwifi/rtl8188ee/
A Dfw.c702 p2p_ps_offload->discovery = 0; in rtl88e_set_p2p_ps_offload_cmd()
707 p2p_ps_offload->discovery = 1; in rtl88e_set_p2p_ps_offload_cmd()
711 p2p_ps_offload->discovery = 0; in rtl88e_set_p2p_ps_offload_cmd()
/linux/Documentation/power/
A Dsuspend-and-cpuhotplug.rst199 image for each CPU (after appropriate CPU type/model discovery using
213 doesn't have the microcode image, it does the CPU type/model discovery
222 discovery is performed and the right microcode is applied to the CPU after
249 CPUs, it just applies them to the CPUs, avoiding any re-discovery of CPU
/linux/drivers/net/wireless/realtek/rtlwifi/rtl8192c/
A Dfw_common.c750 p2p_ps_offload->discovery = 0; in rtl92c_set_p2p_ps_offload_cmd()
755 p2p_ps_offload->discovery = 1; in rtl92c_set_p2p_ps_offload_cmd()
760 p2p_ps_offload->discovery = 0; in rtl92c_set_p2p_ps_offload_cmd()
/linux/drivers/net/wireless/realtek/rtlwifi/rtl8192ee/
A Dfw.c837 p2p_ps_offload->discovery = 0; in rtl92ee_set_p2p_ps_offload_cmd()
842 p2p_ps_offload->discovery = 1; in rtl92ee_set_p2p_ps_offload_cmd()
846 p2p_ps_offload->discovery = 0; in rtl92ee_set_p2p_ps_offload_cmd()

Completed in 54 milliseconds

1234