Home
last modified time | relevance | path

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

12345678910>>...31

/Linux-v6.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.
/Linux-v6.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
/Linux-v6.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",
/Linux-v6.6/Documentation/ABI/testing/
Dsysfs-platform_profile32 changes coming from a userspace write; or coming from another
/Linux-v6.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 */
/Linux-v6.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 …]
/Linux-v6.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
/Linux-v6.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
/Linux-v6.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
/Linux-v6.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.
Dmlxreg.h33 * coming after line card security signature validation;
35 * @MLXREG_HOTPLUG_LC_SYNCED: entry for line card synchronization events, coming
/Linux-v6.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
/Linux-v6.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
/Linux-v6.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
/Linux-v6.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
/Linux-v6.6/arch/powerpc/kernel/
Deeh_event.c162 * On PowerNV platform, we might have subsequent coming events
164 * coming events are totally duplicated and unnecessary, thus
/Linux-v6.6/Documentation/arch/arm/
Dmicrochip.rst150 Coming soon
158 Coming soon
/Linux-v6.6/Documentation/arch/openrisc/
Dtodo.rst7 the coming months. Here's a list of known-to-be-less-than-stellar items
/Linux-v6.6/arch/powerpc/platforms/powernv/
Dsmp.c96 * 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-v6.6/Documentation/devicetree/bindings/input/
Dinput-reset.txt8 Key sequences are global to the system but all the keys in a set must be coming
/Linux-v6.6/LICENSES/exceptions/
DGCC-exception-2.015 distribute those programs without any restriction coming from the use of
/Linux-v6.6/Documentation/devicetree/bindings/spi/
Dnvidia,tegra210-quad-peripheral-props.yaml25 Delays the clock coming in from the device with this tap value.
/Linux-v6.6/Documentation/devicetree/bindings/display/
Dallwinner,sun4i-a10-tv-encoder.yaml29 The first port should be the input endpoint, usually coming from the
/Linux-v6.6/drivers/net/phy/
Dbcm-cygnus.c118 * configurations when coming out of suspend. in bcm_cygnus_resume()
172 /* Re-apply workarounds coming out suspend/resume */ in bcm_omega_resume()
/Linux-v6.6/arch/s390/kernel/
Dabs_lowcore.c20 * request is expected coming from an atomic context, in abs_lowcore_map()

12345678910>>...31