Searched full:deeply (Results 1 – 25 of 25) sorted by relevance
/linux-6.8/Documentation/devicetree/bindings/clock/ |
D | arm,syscon-icst.yaml | 14 Devices Technology (IDT). ARM integrated these oscillators deeply into their
|
/linux-6.8/Documentation/process/ |
D | clang-format.rst | 91 useful when moving code around, for complex code that is deeply intended,
|
D | maintainer-tip.rst | 745 Restricting line length to 80 characters makes deeply indented code hard to
|
/linux-6.8/lib/ |
D | test_linear_ranges.c | 12 /* First things first. I deeply dislike unit-tests. I have seen all the hell
|
/linux-6.8/scripts/dtc/ |
D | fdtget.c | 127 #define MAX_LEVEL 32 /* how deeply nested we will go */
|
D | srcpos.c | 177 die("Includes nested too deeply"); in srcfile_push()
|
/linux-6.8/drivers/perf/ |
D | arm_pmu_acpi.c | 376 * without tying this too deeply into the "real" PMU driver. in arm_pmu_acpi_probe()
|
D | arm_spe_pmu.c | 702 /* This is, of course, deeply driver-specific */ in arm_spe_pmu_event_init()
|
/linux-6.8/Documentation/gpu/ |
D | drm-vm-bind-async.rst | 121 deeply pipelined behind other VM_BIND operations and workloads
|
/linux-6.8/Documentation/power/ |
D | basic-pm-debugging.rst | 102 one and the "core" level tests the hardware and drivers as deeply as possible
|
/linux-6.8/mm/ |
D | vmpressure.c | 53 * reclaimer will try to scan LRUs more deeply.
|
/linux-6.8/drivers/usb/gadget/legacy/ |
D | ether.c | 125 * hardware that's not deeply broken ... even on hardware that can't talk
|
/linux-6.8/arch/arm/mach-at91/ |
D | pm.c | 520 * Call this from platform driver suspend() to see how deeply to suspend. 643 * suspend more deeply, the master clock switches to the clk32k and turns off
|
/linux-6.8/Documentation/bpf/ |
D | bpf_devel_QA.rst | 582 infrastructure and it ties deeply into verification of programs from the
|
/linux-6.8/drivers/usb/host/ |
D | ehci-hcd.c | 603 // this is deeply broken on almost all architectures in ehci_run()
|
/linux-6.8/Documentation/ |
D | memory-barriers.txt | 1376 Multicopy atomicity is a deeply intuitive notion about ordering that is 2554 Interfacing with peripherals via I/O accesses is deeply architecture and device
|
/linux-6.8/arch/arm64/kvm/ |
D | mmu.c | 830 * deeply wrong... in get_user_mapping_size()
|
/linux-6.8/drivers/media/i2c/ |
D | ov7670.c | 657 * is deeply tied into the format, so keep the relevant values here.
|
/linux-6.8/fs/iomap/ |
D | buffered-io.c | 1901 * This avoids stack overflows when called from deeply used stacks in in iomap_do_writepage()
|
/linux-6.8/Documentation/RCU/Design/Requirements/ |
D | Requirements.rst | 1496 in fact may be nested arbitrarily deeply. In practice, as with all 1502 ``CONFIG_PREEMPTION=n``, can be nested arbitrarily deeply. After all, there
|
/linux-6.8/drivers/net/usb/ |
D | usbnet.c | 982 * is deeply engrained into the networking layer. in usbnet_get_link_ksettings_internal()
|
/linux-6.8/fs/ |
D | buffer.c | 694 * deeply under spinlocking. It may not sleep.
|
/linux-6.8/tools/memory-model/Documentation/ |
D | explanation.txt | 661 expectation of cache coherence is so deeply ingrained that violations
|
/linux-6.8/drivers/pci/controller/ |
D | pci-hyperv.c | 3461 * is deeply expecting to scan an emulated PCI configuration
|
/linux-6.8/kernel/trace/ |
D | trace.c | 3333 * This allows for lockless recording. If we're nested too deeply, then
|