| /linux-6.1.9/Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 107 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-6.1.9/Documentation/ABI/testing/ |
| D | sysfs-bus-fcoe | 14 '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
|
| D | sysfs-class-rapidio | 35 (yet). Normally, before enumeration/discovery have been executed
39 After enumeration or discovery was performed for a given mport device,
|
| D | sysfs-bus-rapidio | 128 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-6.1.9/drivers/rapidio/ |
| D | Kconfig | 23 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-6.1.9/include/net/bluetooth/ |
| D | hci_core.h | 550 struct discovery_state discovery; member
882 hdev->discovery.state = DISCOVERY_STOPPED; in discovery_init()
883 INIT_LIST_HEAD(&hdev->discovery.all); in discovery_init()
884 INIT_LIST_HEAD(&hdev->discovery.unknown); in discovery_init()
885 INIT_LIST_HEAD(&hdev->discovery.resolve); in discovery_init()
886 hdev->discovery.report_invalid_rssi = true; in discovery_init()
887 hdev->discovery.rssi = HCI_RSSI_INVALID; in discovery_init()
892 hdev->discovery.result_filtering = false; in hci_discovery_filter_clear()
893 hdev->discovery.report_invalid_rssi = true; in hci_discovery_filter_clear()
894 hdev->discovery.rssi = HCI_RSSI_INVALID; in hci_discovery_filter_clear()
[all …]
|
| /linux-6.1.9/arch/arm64/boot/dts/qcom/ |
| D | sdm630-sony-xperia-nile-discovery.dts | 13 compatible = "sony,discovery-row", "qcom,sdm630";
|
| /linux-6.1.9/Documentation/arm/ |
| D | marvell.rst | 90 …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-6.1.9/drivers/nvme/target/ |
| D | Makefile | 13 discovery.o io-cmd-file.o io-cmd-bdev.o
|
| /linux-6.1.9/drivers/bus/fsl-mc/ |
| D | Kconfig | 14 architecture. The fsl-mc bus driver handles discovery of
|
| /linux-6.1.9/Documentation/scsi/ |
| D | ChangeLog.lpfc | 14 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 …]
|
| D | bnx2fc.rst | 42 discovery and log into the targets.
68 6. Verify the vlan discovery is performed by running ifconfig and notice
|
| /linux-6.1.9/include/net/ |
| D | amt.h | 209 struct amt_header_discovery discovery; member
220 struct amt_header_discovery discovery; member
|
| /linux-6.1.9/drivers/net/wireless/realtek/rtlwifi/rtl8723ae/ |
| D | fw.c | 563 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-6.1.9/Documentation/driver-api/driver-model/ |
| D | overview.rst | 26 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-6.1.9/drivers/firmware/smccc/ |
| D | Kconfig | 14 to add SMCCC discovery mechanism though the PSCI firmware
|
| /linux-6.1.9/drivers/staging/r8188eu/include/ |
| D | rtl8188e_cmd.h | 70 u8 discovery:1; member
|
| /linux-6.1.9/Documentation/ABI/removed/ |
| D | video1394 | 10 asynchronous I/O for device discovery and configuration.
|
| /linux-6.1.9/drivers/net/wireless/realtek/rtlwifi/rtl8723be/ |
| D | fw.c | 667 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-6.1.9/Documentation/admin-guide/aoe/ |
| D | aoe.rst | 41 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-6.1.9/drivers/net/wireless/realtek/rtlwifi/rtl8188ee/ |
| D | fw.c | 702 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-6.1.9/Documentation/devicetree/bindings/perf/ |
| D | arm,cmn.yaml | 39 discovery node (see TRM definition of ROOTNODEBASE). Not
|
| /linux-6.1.9/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 199 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-6.1.9/arch/arm/mach-sti/ |
| D | Kconfig | 23 STiH418 family SoCs using the Device Tree for discovery. More
|
| /linux-6.1.9/drivers/staging/r8188eu/hal/ |
| D | rtl8188e_cmd.c | 679 p2p_ps_offload->discovery = 0; in rtl8188e_set_p2p_ps_offload_cmd()
683 p2p_ps_offload->discovery = 1; in rtl8188e_set_p2p_ps_offload_cmd()
686 p2p_ps_offload->discovery = 0; in rtl8188e_set_p2p_ps_offload_cmd()
|