Home
last modified time | relevance | path

Searched full:coming (Results 1 – 25 of 1176) sorted by relevance

12345678910>>...48

/kernel/linux/linux-4.19/arch/powerpc/platforms/8xx/
DKconfig140 Help not implemented yet, coming soon.
148 Help not implemented yet, coming soon.
153 Help not implemented yet, coming soon.
158 Help not implemented yet, coming soon.
/kernel/linux/linux-5.10/arch/powerpc/platforms/8xx/
DKconfig131 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.
/kernel/linux/linux-5.10/drivers/i3c/
Ddevice.c75 * 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
/kernel/linux/linux-4.19/arch/arm/mm/
Dcache-aurora-l2.h51 * the distinction between a number coming from hardware and a number
52 * coming from the device tree */
/kernel/linux/linux-4.19/drivers/gpu/drm/amd/amdkfd/
Dkfd_dbgmgr.c118 /* 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()
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/amdkfd/
Dkfd_dbgmgr.c118 /* 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()
/kernel/linux/linux-5.10/arch/arm/include/asm/hardware/
Dcache-aurora-l2.h99 * the distinction between a number coming from hardware and a number
100 * coming from the device tree */
/kernel/linux/linux-5.10/tools/testing/selftests/bpf/
Dtest_flow_dissector.sh107 # 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
/kernel/linux/linux-5.10/Documentation/driver-api/nfc/
Dnfc-hci.rst19 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
/kernel/linux/linux-4.19/Documentation/nfc/
Dnfc-hci.txt17 HCI registers as an nfc device with NFC Core. Requests coming from userspace are
115 - event_received() is called to handle an event coming from the chip. Driver
140 Data coming from the chip shall be sent directly to nfc_hci_recv_frame().
166 - rcv_from_drv() : handle data coming from the chip, going to HCI
/kernel/linux/linux-5.10/Documentation/networking/
Dnf_flowtable.rst21 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
/kernel/linux/linux-4.19/Documentation/networking/
Dnf_flowtable.txt18 netfilter hooks coming after the ingress). In case of flowtable miss, the packet
96 flowtable for the TCP syn-ack packet coming in the reply direction. Once the
/kernel/linux/linux-5.10/include/linux/platform_data/
Dcros_ec_sensorhub.h127 * @fifo_info: Copy of FIFO information coming from the EC.
136 * by feature bits coming from the EC or userspace.
/kernel/linux/linux-5.10/drivers/usb/serial/
Daircable.c16 * 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
/kernel/linux/linux-4.19/drivers/usb/serial/
Daircable.c16 * 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
/kernel/linux/linux-5.10/drivers/net/wireless/ath/ath11k/
Dce.h35 * "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
/kernel/linux/linux-4.19/Documentation/openrisc/
DTODO3 the coming months. Here's a list of known-to-be-less-than-stellar items
/kernel/linux/linux-5.10/Documentation/admin-guide/pm/
Dintel_idle.rst21 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
/kernel/linux/linux-5.10/Documentation/openrisc/
Dtodo.rst7 the coming months. Here's a list of known-to-be-less-than-stellar items
/kernel/linux/linux-5.10/arch/powerpc/kernel/
Deeh_event.c162 * On PowerNV platform, we might have subsequent coming events
164 * coming events are totally duplicated and unnecessary, thus
/kernel/linux/linux-4.19/arch/powerpc/kernel/
Deeh_event.c155 * On PowerNV platform, we might have subsequent coming events
157 * coming events are totally duplicated and unnecessary, thus
/kernel/linux/linux-4.19/Documentation/scsi/
Dlink_power_management_policy.txt9 when coming out of lower power states.
/kernel/linux/linux-4.19/kernel/
Dtracepoint.c397 * register_tracepoint_notifier - register tracepoint coming/going notifier
401 * coming/going with the tracepoint_module_list_mutex held.
423 * unregister_tracepoint_notifier - unregister tracepoint coming/going notifier
511 * In the case of modules that were tainted at "coming", we'll simply in tracepoint_module_going()
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/input/
Dinput-reset.txt8 Key sequences are global to the system but all the keys in a set must be coming
/kernel/linux/linux-5.10/LICENSES/exceptions/
DGCC-exception-2.015 distribute those programs without any restriction coming from the use of

12345678910>>...48