Home
last modified time | relevance | path

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

12345678910>>...59

/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-6.6/arch/powerpc/platforms/8xx/
DKconfig132 Help not implemented yet, coming soon.
140 Help not implemented yet, coming soon.
145 Help not implemented yet, coming soon.
150 Help not implemented yet, coming soon.
/kernel/linux/linux-6.6/drivers/i3c/
Ddevice.c95 * i3c_device_disable_ibi() - Disable IBIs coming from a specific device
98 * This function disable IBIs coming from a specific device and wait for
120 * i3c_device_enable_ibi() - Enable IBIs coming from a specific device
123 * This function enable IBIs coming from a specific device and wait for
154 * process IBIs coming from @dev. When this function returns, the IBI is not
/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-6.6/Documentation/ABI/testing/
Dsysfs-platform_profile32 changes coming from a userspace write; or coming from another
/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-6.6/tools/perf/pmu-events/arch/x86/broadwellde/
Duncore-interconnect.json547 "PublicDescription": "Events coming from Uncore can be sent to one or all cores",
556 … "PublicDescription": "Events coming from Uncore can be sent to one or all cores; Filter by core",
565 … "PublicDescription": "Events coming from Uncore can be sent to one or all cores; Filter by core",
574 … "PublicDescription": "Events coming from Uncore can be sent to one or all cores; Filter by core",
583 … "PublicDescription": "Events coming from Uncore can be sent to one or all cores; Filter by core",
592 …"PublicDescription": "Events coming from Uncore can be sent to one or all cores; PREQ, PSMI, P2U, …
601 "PublicDescription": "Events coming from Uncore can be sent to one or all cores",
610 "PublicDescription": "Events coming from Uncore can be sent to one or all cores",
/kernel/linux/linux-6.6/arch/arm/include/asm/hardware/
Dcache-aurora-l2.h96 * the distinction between a number coming from hardware and a number
97 * coming from the device tree */
/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-6.6/tools/perf/pmu-events/arch/x86/sapphirerapids/
Duncore-cache.json450 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
459 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
468 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
476 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
485 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
493 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
501 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
510 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
519 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
527 …es the LLC was accessed - this includes code, data, prefetches and hints coming from L2. This has…
[all …]
/kernel/linux/linux-6.6/tools/testing/selftests/bpf/
Dtest_flow_dissector.sh109 # Drops all IP/UDP packets coming from port 9
153 # Drops all IP/UDP packets coming from port 8-10
167 # 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-6.6/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-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-6.6/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-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-6.6/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-6.6/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-6.6/drivers/net/wireless/ath/ath12k/
Dce.h29 * "coming IN over air through Target to Host" as with a WiFi Rx operation.
32 * Target since things that are "PIPEDIR_OUT" are coming IN to the Target
/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-6.6/Documentation/admin-guide/pm/
Dintel_idle.rst21 processor model and may also depend on information coming from the platform
82 coming from the ACPI tables. [This step is skipped if ``intel_idle`` is
99 preliminary list of idle states coming from the ACPI tables. In that case user
108 supports ``MWAIT``, the preliminary list of idle states coming from the ACPI
/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-6.6/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/
Dcounters.rst947 cannot absorb the traffic coming from to the adapter.
953 cannot absorb the traffic coming from the network.
964 is congested and cannot absorb the traffic coming from the network.
1134 cannot absorb the traffic coming from the adapter. Note: This counter is
1142 cannot absorb the traffic coming from the adapter. Note: This counter is
1149 cannot absorb the traffic coming from the network. Note: This counter is
1201 and cannot absorb the traffic coming from the adapter. Note: This counter
1209 the network is congested and cannot absorb the traffic coming from the
1223 and cannot absorb the traffic coming from the network. Note: This counter

12345678910>>...59