Home
last modified time | relevance | path

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

12345678

/linux/Documentation/ABI/testing/
H A Dsysfs-bus-vfio-mdev72 Userspace applications interested in knowing the name of
85 Userspace applications interested in knowing the details of
H A Ddebugfs-ec8 Knowing the EC GPE one can watch the amount of HW events related to
H A Dsysfs-platform-dell-privacy-wmi44 consumed by various applications interested in knowing the Privacy
/linux/tools/testing/selftests/rseq/
H A Drseq-s390.h56 * explicitly defined as additional exit points. Knowing all exit points is
H A 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
H A 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
H A Drseq-mips.h106 * explicitly defined as additional exit points. Knowing all exit points is
H A Drseq-arm.h103 * explicitly defined as additional exit points. Knowing all exit points is
/linux/Documentation/devicetree/bindings/mailbox/
H A Damlogic,meson-gxbb-mhu.yaml17 received data. However, there is no specified way of knowing if the sent
/linux/tools/memory-model/Documentation/
H A 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/Documentation/arch/powerpc/
H A Dkasan.txt54 requires knowing how much contiguous physical memory a system has _at compile
/linux/drivers/pwm/
H A Dpwm-lpss-platform.c45 * knowing about this. On devices where the controller is unused in pwm_lpss_probe_platform()
/linux/drivers/leds/
H A DTODO41 Userspace is interested in knowing "this LED can produce arbitrary
/linux/drivers/gpu/drm/i915/gt/
H A Dintel_gt_sysfs.c30 * We are interested at knowing from where the interface in intel_gt_sysfs_get_drvdata()
/linux/arch/riscv/include/asm/
H A Dthread_info.h71 * Used in handle_exception() to save a0, a1 and a2 before knowing if we
/linux/Documentation/devicetree/bindings/gpio/
H A Dnxp,pcf8575.yaml18 input and reporting a low/high value, without knowing the last value written
/linux/include/linux/
H A Dannotate.h57 * Annotate away the various 'relocation to !ENDBR` complaints; knowing that
/linux/drivers/net/arcnet/
H A DKconfig77 have always used the old ARCnet driver without knowing what type of
/linux/arch/m68k/include/asm/
H A Dmcfintc.h23 * related to) the actual interrupt number they use. So knowing the IRQ
/linux/Documentation/arch/arm/
H A Dporting.rst10 The following symbol definitions rely on you knowing the translation that
/linux/arch/m68k/coldfire/
H A Dsltimers.c135 /* initialize mcfslt_cnt knowing that slice timers count down */ in hw_timer_init()
/linux/Documentation/driver-api/gpio/
H A Dintro.rst32 firmware knowing how they're used).
/linux/arch/sh/mm/
H A Dcache-sh7705.c95 * number, knowing this would reduce the number of cache entries to be in __flush_dcache_page()
/linux/drivers/usb/musb/
H A Dmusb_dma.h29 * - Knowing the correlation between dma channels and the
/linux/Documentation/networking/
H A Dphy-link-topology.rst41 Knowing that some modules embed a PHY, the actual link is more like ::

12345678