Home
last modified time | relevance | path

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

123

/Linux-v5.15/Documentation/driver-api/rapidio/
Drapidio.rst107 an enumeration and/or discovery routine may be called automatically or
120 discovery methods as statically linked components or loadable modules.
121 An enumeration/discovery method implementation and available input parameters
125 Depending on selected enumeration/discovery build configuration, there are
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.
133 When automatic start of enumeration/discovery is used a user has to ensure
138 expires the discovery process is terminated without obtaining RapidIO network
139 information. NOTE: a timed out discovery process may be restarted later using
[all …]
/Linux-v5.15/Documentation/ABI/testing/
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
Dsysfs-class-rapidio35 (yet). Normally, before enumeration/discovery have been executed
39 After enumeration or discovery was performed for a given mport device,
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-v5.15/include/net/bluetooth/
Dhci_core.h503 struct discovery_state discovery; member
791 hdev->discovery.state = DISCOVERY_STOPPED; in discovery_init()
792 INIT_LIST_HEAD(&hdev->discovery.all); in discovery_init()
793 INIT_LIST_HEAD(&hdev->discovery.unknown); in discovery_init()
794 INIT_LIST_HEAD(&hdev->discovery.resolve); in discovery_init()
795 hdev->discovery.report_invalid_rssi = true; in discovery_init()
796 hdev->discovery.rssi = HCI_RSSI_INVALID; in discovery_init()
801 hdev->discovery.result_filtering = false; in hci_discovery_filter_clear()
802 hdev->discovery.report_invalid_rssi = true; in hci_discovery_filter_clear()
803 hdev->discovery.rssi = HCI_RSSI_INVALID; in hci_discovery_filter_clear()
[all …]
/Linux-v5.15/drivers/rapidio/
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-v5.15/arch/arm64/boot/dts/qcom/
Dsdm630-sony-xperia-nile-discovery.dts13 compatible = "sony,discovery-row", "qcom,sdm630";
/Linux-v5.15/net/bluetooth/
Dhci_request.c461 if (hdev->discovery.state != DISCOVERY_STOPPED) in __hci_update_background_scan()
1324 old_state = hdev->discovery.state; in hci_req_prepare_suspend()
2987 if (req->hdev->discovery.limited) in bredr_inquiry()
3019 hdev->discovery.scan_start = 0; in le_scan_disable_work()
3029 if (hdev->discovery.type == DISCOV_TYPE_LE) in le_scan_disable_work()
3032 if (hdev->discovery.type != DISCOV_TYPE_INTERLEAVED) in le_scan_disable_work()
3037 hdev->discovery.state != DISCOVERY_RESOLVING) in le_scan_disable_work()
3113 !hdev->discovery.scan_start) in le_scan_restart_work()
3121 duration = hdev->discovery.scan_duration; in le_scan_restart_work()
3122 scan_start = hdev->discovery.scan_start; in le_scan_restart_work()
[all …]
/Linux-v5.15/drivers/nvme/target/
DMakefile13 discovery.o io-cmd-file.o io-cmd-bdev.o
/Linux-v5.15/drivers/bus/fsl-mc/
DKconfig14 architecture. The fsl-mc bus driver handles discovery of
/Linux-v5.15/Documentation/scsi/
DChangeLog.lpfc14 discovery lists.
216 * Moved discovery timeout handler to worker thread. There are
289 * Renamed discovery thread to lpfc_worker thread. Moved handling
310 discovery) to 32
361 on a per-target basis driven by the discovery engine.
372 * Fixed potential discovery bug, nlp list corrutpion fix potential
380 initial discovery, and IO not starting to disks). Backs out
388 * Fixed bug introduced when discovery thread implementation was
508 discovery state machine as well.
538 * Fixed discovery bug: plogi cmpl uses ndlp after its freed.
[all …]
Dbnx2fc.rst42 discovery and log into the targets.
68 6. Verify the vlan discovery is performed by running ifconfig and notice
/Linux-v5.15/Documentation/arm/
Dmarvell.rst89 …chive.org/web/20120616194711/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
90 …chive.org/web/20141005120451/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
91 …chive.org/web/20111110081125/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
94 …chive.org/web/20140801121623/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
95 …chive.org/web/20141005120458/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
96 …chive.org/web/20111110081125/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
100 …chive.org/web/20140722064429/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
101 …chive.org/web/20140722064425/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
102 …chive.org/web/20111110081125/http://www.marvell.com/embedded-processors/discovery-innovation/asset…
/Linux-v5.15/Documentation/driver-api/driver-model/
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-v5.15/drivers/net/wireless/realtek/rtlwifi/rtl8723ae/
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-v5.15/drivers/firmware/smccc/
DKconfig14 to add SMCCC discovery mechanism though the PSCI firmware
/Linux-v5.15/Documentation/ABI/removed/
Dvideo139410 asynchronous I/O for device discovery and configuration.
/Linux-v5.15/drivers/net/wireless/realtek/rtlwifi/rtl8723be/
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-v5.15/drivers/staging/r8188eu/include/
Drtl8188e_cmd.h83 u8 discovery:1; member
/Linux-v5.15/Documentation/admin-guide/aoe/
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-v5.15/drivers/net/wireless/realtek/rtlwifi/rtl8188ee/
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-v5.15/Documentation/power/
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-v5.15/arch/arm/mach-sti/
DKconfig23 STiH418 family SoCs using the Device Tree for discovery. More
/Linux-v5.15/drivers/net/wireless/realtek/rtlwifi/rtl8192c/
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-v5.15/drivers/net/wireless/realtek/rtlwifi/rtl8192ee/
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()

123