Home
last modified time | relevance | path

Searched full:knowing (Results 1 – 25 of 213) sorted by relevance

123456789

/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-bus-vfio-mdev72 Userspace applications interested in knowing the name of
85 Userspace applications interested in knowing the details of
Ddebugfs-ec8 Knowing the EC GPE one can watch the amount of HW events related to
Dsysfs-platform-dell-privacy-wmi44 consumed by various applications interested in knowing the Privacy
/linux-6.14.4/tools/testing/selftests/rseq/
Drseq-s390.h58 * explicitly defined as additional exit points. Knowing all exit points is
85 * explicitly defined as additional exit points. Knowing all exit points is
Drseq-x86.h80 * explicitly defined as additional exit points. Knowing all exit points is
167 * explicitly defined as additional exit points. Knowing all exit points is
Drseq-ppc.h81 * explicitly defined as additional exit points. Knowing all exit points is
117 * explicitly defined as additional exit points. Knowing all exit points is
Drseq-mips.h106 * explicitly defined as additional exit points. Knowing all exit points is
Drseq-or1k.h54 * explicitly defined as additional exit points. Knowing all exit points is
/linux-6.14.4/Documentation/devicetree/bindings/mailbox/
Damlogic,meson-gxbb-mhu.yaml17 received data. However, there is no specified way of knowing if the sent
Darm,mhu.yaml16 However, there is no specified way of knowing if the sent data has been read
/linux-6.14.4/include/net/
Dcls_cgroup.h62 * disable bh. Knowing this, it is possible to detect softirq based in task_get_classid()
/linux-6.14.4/tools/memory-model/Documentation/
Daccess-marking.txt103 to generate false positives because KCSAN will have no way of knowing
127 to generate false positives because KCSAN will have no way of knowing
148 to generate false positives because KCSAN will have no way of knowing
165 because KCSAN will have no way of knowing that the resulting data race
/linux-6.14.4/Documentation/arch/powerpc/
Dkasan.txt54 requires knowing how much contiguous physical memory a system has _at compile
/linux-6.14.4/drivers/pwm/
Dpwm-lpss-platform.c45 * knowing about this. On devices where the controller is unused in pwm_lpss_probe_platform()
/linux-6.14.4/drivers/leds/
DTODO41 Userspace is interested in knowing "this LED can produce arbitrary
/linux-6.14.4/Documentation/devicetree/bindings/gpio/
Dnxp,pcf8575.yaml18 input and reporting a low/high value, without knowing the last value written
/linux-6.14.4/drivers/gpu/drm/i915/gt/
Dintel_gt_sysfs.c30 * We are interested at knowing from where the interface in intel_gt_sysfs_get_drvdata()
/linux-6.14.4/arch/riscv/include/asm/
Dthread_info.h71 * Used in handle_exception() to save a0, a1 and a2 before knowing if we
/linux-6.14.4/drivers/net/arcnet/
DKconfig77 have always used the old ARCnet driver without knowing what type of
/linux-6.14.4/arch/m68k/include/asm/
Dmcfintc.h23 * related to) the actual interrupt number they use. So knowing the IRQ
/linux-6.14.4/Documentation/arch/arm/
Dporting.rst10 The following symbol definitions rely on you knowing the translation that
/linux-6.14.4/arch/arm64/boot/dts/qcom/
Dipq9574-rdp-common.dtsi98 * During regulator registration, kernel not knowing the initial voltage,
/linux-6.14.4/arch/sh/mm/
Dcache-sh7705.c95 * number, knowing this would reduce the number of cache entries to be in __flush_dcache_page()
/linux-6.14.4/drivers/input/
Dinput-poller.c77 * printed backtrace as knowing what instance of input in input_setup_polling()
/linux-6.14.4/arch/m68k/coldfire/
Dsltimers.c135 /* initialize mcfslt_cnt knowing that slice timers count down */ in hw_timer_init()

123456789