Searched full:coming (Results 1 – 25 of 688) sorted by relevance
12345678910>>...28
| /Linux-v5.10/arch/powerpc/platforms/8xx/ |
| D | Kconfig | 131 Help not implemented yet, coming soon.
139 Help not implemented yet, coming soon.
144 Help not implemented yet, coming soon.
149 Help not implemented yet, coming soon.
|
| /Linux-v5.10/drivers/i3c/ |
| D | device.c | 75 * i3c_device_disable_ibi() - Disable IBIs coming from a specific device
78 * This function disable IBIs coming from a specific device and wait for
100 * i3c_device_enable_ibi() - Enable IBIs coming from a specific device
103 * This function enable IBIs coming from a specific device and wait for
134 * process IBIs coming from @dev. When this function returns, the IBI is not
|
| /Linux-v5.10/drivers/gpu/drm/amd/amdkfd/ |
| D | kfd_dbgmgr.c | 118 /* Is the requests coming from the already registered process? */ in kfd_dbgmgr_unregister()
135 /* Is the requests coming from the already registered process? */ in kfd_dbgmgr_wave_control()
148 /* Is the requests coming from the already registered process? */ in kfd_dbgmgr_address_watch()
|
| /Linux-v5.10/arch/arm/include/asm/hardware/ |
| D | cache-aurora-l2.h | 99 * the distinction between a number coming from hardware and a number
100 * coming from the device tree */
|
| /Linux-v5.10/tools/testing/selftests/bpf/ |
| D | test_flow_dissector.sh | 107 # Drops all IP/UDP packets coming from port 9
143 # Drops all IP/UDP packets coming from port 8-10
157 # Drops all IPv6/UDP packets coming from port 9
|
| /Linux-v5.10/Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 19 HCI registers as an nfc device with NFC Core. Requests coming from userspace are
118 - event_received() is called to handle an event coming from the chip. Driver
146 Data coming from the chip shall be sent directly to nfc_hci_recv_frame().
177 handle data coming from the chip, going to HCI
|
| /Linux-v5.10/Documentation/networking/ |
| D | nf_flowtable.rst | 21 netfilter hooks coming after the ingress). In case of flowtable miss, the packet
101 flowtable for the TCP syn-ack packet coming in the reply direction. Once the
|
| /Linux-v5.10/drivers/usb/serial/ |
| D | aircable.c | 16 * The device simply need some stuff to understand data coming from the usb
24 * if there is data coming that does not contain any header, then that is data
|
| /Linux-v5.10/drivers/net/wireless/ath/ath11k/ |
| D | ce.h | 35 * "coming IN over air through Target to Host" as with a WiFi Rx operation.
38 * Target since things that are "PIPEDIR_OUT" are coming IN to the Target
|
| /Linux-v5.10/include/linux/platform_data/ |
| D | cros_ec_sensorhub.h | 127 * @fifo_info: Copy of FIFO information coming from the EC.
136 * by feature bits coming from the EC or userspace.
|
| /Linux-v5.10/Documentation/admin-guide/pm/ |
| D | intel_idle.rst | 21 processor model and may also depend on information coming from the platform
81 coming from the ACPI tables. [This step is skipped if ``intel_idle`` is
98 preliminary list of idle states coming from the ACPI tables. In that case user
106 supports ``MWAIT``, the preliminary list of idle states coming from the ACPI
|
| /Linux-v5.10/Documentation/openrisc/ |
| D | todo.rst | 7 the coming months. Here's a list of known-to-be-less-than-stellar items
|
| /Linux-v5.10/arch/powerpc/kernel/ |
| D | eeh_event.c | 162 * On PowerNV platform, we might have subsequent coming events
164 * coming events are totally duplicated and unnecessary, thus
|
| /Linux-v5.10/kernel/ |
| D | tracepoint.c | 411 * register_tracepoint_notifier - register tracepoint coming/going notifier
415 * coming/going with the tracepoint_module_list_mutex held.
437 * unregister_tracepoint_notifier - unregister tracepoint coming/going notifier
525 * In the case of modules that were tainted at "coming", we'll simply in tracepoint_module_going()
|
| /Linux-v5.10/arch/powerpc/platforms/powernv/ |
| D | smp.c | 96 * Already started, just kick it, probably coming from in pnv_smp_kick_cpu()
221 * for coming online, which are handled via in pnv_cpu_offline_self()
293 DBG("CPU%d coming online...\n", cpu); in pnv_cpu_offline_self()
|
| /Linux-v5.10/Documentation/devicetree/bindings/input/ |
| D | input-reset.txt | 8 Key sequences are global to the system but all the keys in a set must be coming
|
| /Linux-v5.10/LICENSES/exceptions/ |
| D | GCC-exception-2.0 | 15 distribute those programs without any restriction coming from the use of
|
| /Linux-v5.10/drivers/net/wimax/i2400m/ |
| D | op-rfkill.c | 14 * indications coming through hardware reports]. We also do it on
18 * switch (coming from sysfs, the wimax stack or user space).
|
| /Linux-v5.10/Documentation/devicetree/bindings/display/ |
| D | allwinner,sun4i-a10-tv-encoder.yaml | 31 first port should be the input endpoint, usually coming from the
|
| /Linux-v5.10/include/uapi/linux/ |
| D | netfilter_bridge.h | 25 /* Packets coming from a local process. */
|
| /Linux-v5.10/arch/x86/include/asm/ |
| D | kexec.h | 70 * This function is responsible for capturing register states if coming
71 * via panic otherwise just fix up the ss and sp if coming via kernel
|
| /Linux-v5.10/drivers/net/phy/ |
| D | bcm-cygnus.c | 118 * configurations when coming out of suspend. in bcm_cygnus_resume()
172 /* Re-apply workarounds coming out suspend/resume */ in bcm_omega_resume()
|
| /Linux-v5.10/drivers/clk/baikal-t1/ |
| D | Kconfig | 37 between AXI-bus and system devices coming from CCU PLLs of Baikal-T1
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-y10b.rst | 17 with no padding between them and with the most significant bits coming
|
| /Linux-v5.10/arch/x86/boot/ |
| D | string.h | 5 /* Undef any of these macros coming from string_32.h. */
|
12345678910>>...28
