Home
last modified time | relevance | path

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

123

/Linux-v5.4/drivers/gpu/drm/amd/amdgpu/
Damdgpu_discovery.c182 adev->discovery = kzalloc(BINARY_MAX_SIZE, GFP_KERNEL); in amdgpu_discovery_init()
183 if (!adev->discovery) in amdgpu_discovery_init()
186 r = amdgpu_discovery_read_binary(adev, adev->discovery); in amdgpu_discovery_init()
192 bhdr = (struct binary_header *)adev->discovery; in amdgpu_discovery_init()
205 if (!amdgpu_discovery_verify_checksum(adev->discovery + offset, in amdgpu_discovery_init()
215 ihdr = (struct ip_discovery_header *)(adev->discovery + offset); in amdgpu_discovery_init()
223 if (!amdgpu_discovery_verify_checksum(adev->discovery + offset, in amdgpu_discovery_init()
233 ghdr = (struct gpu_info_header *)(adev->discovery + offset); in amdgpu_discovery_init()
235 if (!amdgpu_discovery_verify_checksum(adev->discovery + offset, in amdgpu_discovery_init()
245 kfree(adev->discovery); in amdgpu_discovery_init()
[all …]
/Linux-v5.4/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.4/include/net/bluetooth/
Dhci_core.h384 struct discovery_state discovery; member
616 hdev->discovery.state = DISCOVERY_STOPPED; in discovery_init()
617 INIT_LIST_HEAD(&hdev->discovery.all); in discovery_init()
618 INIT_LIST_HEAD(&hdev->discovery.unknown); in discovery_init()
619 INIT_LIST_HEAD(&hdev->discovery.resolve); in discovery_init()
620 hdev->discovery.report_invalid_rssi = true; in discovery_init()
621 hdev->discovery.rssi = HCI_RSSI_INVALID; in discovery_init()
626 hdev->discovery.result_filtering = false; in hci_discovery_filter_clear()
627 hdev->discovery.report_invalid_rssi = true; in hci_discovery_filter_clear()
628 hdev->discovery.rssi = HCI_RSSI_INVALID; in hci_discovery_filter_clear()
[all …]
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-bus-fcoe12 'start' attribute to begin the kernel's discovery and login
30 discovery and login. The FCoE Controller is destroyed by
41 is started in 'Fabric' mode then FIP FCF discovery is
44 FIP VN2VN discovery and login is performed. A FCoE
Dsysfs-class-rapidio31 (yet). Normally, before enumeration/discovery have been executed
35 After enumeration or discovery was performed for a given mport device,
Dsysfs-bus-rapidio125 set by the switch initialization routine during enumeration or discovery
189 (WO) Allows to trigger enumeration discovery process from user
190 space. To initiate an enumeration or discovery process on
196 initiate RapidIO enumeration/discovery on all available mports a
/Linux-v5.4/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.4/net/bluetooth/
Dhci_request.c406 if (hdev->discovery.state != DISCOVERY_STOPPED) in __hci_update_background_scan()
2337 if (req->hdev->discovery.limited) in bredr_inquiry()
2369 hdev->discovery.scan_start = 0; in le_scan_disable_work()
2379 if (hdev->discovery.type == DISCOV_TYPE_LE) in le_scan_disable_work()
2382 if (hdev->discovery.type != DISCOV_TYPE_INTERLEAVED) in le_scan_disable_work()
2387 hdev->discovery.state != DISCOVERY_RESOLVING) in le_scan_disable_work()
2458 !hdev->discovery.scan_start) in le_scan_restart_work()
2466 duration = hdev->discovery.scan_duration; in le_scan_restart_work()
2467 scan_start = hdev->discovery.scan_start; in le_scan_restart_work()
2553 BT_DBG("%s type %u", hdev->name, hdev->discovery.type); in start_discovery()
[all …]
Dmgmt.c3858 if (hdev->discovery.state != DISCOVERY_STOPPED || in start_discovery_internal()
3876 hdev->discovery.type = cp->type; in start_discovery_internal()
3877 hdev->discovery.report_invalid_rssi = false; in start_discovery_internal()
3879 hdev->discovery.limited = true; in start_discovery_internal()
3881 hdev->discovery.limited = false; in start_discovery_internal()
3944 if (hdev->discovery.state != DISCOVERY_STOPPED || in start_service_discovery()
3996 hdev->discovery.result_filtering = true; in start_service_discovery()
3997 hdev->discovery.type = cp->type; in start_service_discovery()
3998 hdev->discovery.rssi = cp->rssi; in start_service_discovery()
3999 hdev->discovery.uuid_count = uuid_count; in start_service_discovery()
[all …]
/Linux-v5.4/drivers/bus/fsl-mc/
DKconfig14 architecture. The fsl-mc bus driver handles discovery of
/Linux-v5.4/drivers/nvme/target/
DMakefile13 discovery.o io-cmd-file.o io-cmd-bdev.o
/Linux-v5.4/Documentation/scsi/
Dbnx2fc.txt38 discovery and log into the targets.
62 6. Verify the vlan discovery is performed by running ifconfig and notice
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 …]
/Linux-v5.4/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.4/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.4/Documentation/ABI/removed/
Dvideo139410 asynchronous I/O for device discovery and configuration.
/Linux-v5.4/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.4/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.4/Documentation/arm/
Dmarvel.rst81 …- Product Brief : http://www.marvell.com/embedded-processors/discovery-innovation/assets/MV78100-…
82 …- Hardware Spec : http://www.marvell.com/embedded-processors/discovery-innovation/assets/HW_MV781…
83 …- Functional Spec: http://www.marvell.com/embedded-processors/discovery-innovation/assets/FS_MV761…
86 …- Product Brief : http://www.marvell.com/embedded-processors/discovery-innovation/assets/MV78200-…
87 …- Hardware Spec : http://www.marvell.com/embedded-processors/discovery-innovation/assets/HW_MV782…
88 …- Functional Spec: http://www.marvell.com/embedded-processors/discovery-innovation/assets/FS_MV761…
/Linux-v5.4/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.4/Documentation/power/
Dsuspend-and-cpuhotplug.rst198 image for each CPU (after appropriate CPU type/model discovery using
212 doesn't have the microcode image, it does the CPU type/model discovery
221 discovery is performed and the right microcode is applied to the CPU after
248 CPUs, it just applies them to the CPUs, avoiding any re-discovery of CPU
/Linux-v5.4/arch/arm/mach-sti/
DKconfig23 STiH418 family SoCs using the Device Tree for discovery. More
/Linux-v5.4/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.4/drivers/net/wireless/realtek/rtlwifi/rtl8192ee/
Dfw.c840 p2p_ps_offload->discovery = 0; in rtl92ee_set_p2p_ps_offload_cmd()
845 p2p_ps_offload->discovery = 1; in rtl92ee_set_p2p_ps_offload_cmd()
849 p2p_ps_offload->discovery = 0; in rtl92ee_set_p2p_ps_offload_cmd()
/Linux-v5.4/Documentation/devicetree/bindings/slimbus/
Dbus.txt16 discovery (slave device reporting itself present).

123