Searched full:knowing (Results 1 – 25 of 189) sorted by relevance
12345678
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-bus-vfio-mdev | 72 Userspace applications interested in knowing the name of
85 Userspace applications interested in knowing the details of
|
| D | debugfs-ec | 8 Knowing the EC GPE one can watch the amount of HW events related to
|
| D | sysfs-platform-dell-privacy-wmi | 41 consumed by various applications interested in knowing the Privacy
|
| D | sysfs-bus-pci | 208 Userspace applications interested in knowing the
223 Userspace applications interested in knowing the
239 Userspace applications interested in knowing the
|
| /Linux-v5.15/Documentation/devicetree/bindings/mailbox/ |
| D | amlogic,meson-gxbb-mhu.yaml | 17 received data. However, there is no specified way of knowing if the sent
|
| D | arm,mhu.yaml | 16 However, there is no specified way of knowing if the sent data has been read
|
| /Linux-v5.15/include/linux/platform_data/ |
| D | pcf857x.h | 28 * inferred by reading the chip's value and knowing the last value written
|
| /Linux-v5.15/tools/memory-model/Documentation/ |
| D | access-marking.txt | 97 to generate false positives because KCSAN will have no way of knowing
121 to generate false positives because KCSAN will have no way of knowing
142 to generate false positives because KCSAN will have no way of knowing
159 because KCSAN will have no way of knowing that the resulting data race
|
| /Linux-v5.15/include/net/ |
| D | cls_cgroup.h | 62 * disable bh. Knowing this, it is possible to detect softirq based in task_get_classid()
|
| /Linux-v5.15/drivers/leds/ |
| D | TODO | 41 Userspace is interested in knowing "this LED can produce arbitrary
|
| /Linux-v5.15/Documentation/devicetree/bindings/gpio/ |
| D | nxp,pcf8575.yaml | 18 input and reporting a low/high value, without knowing the last value written
|
| /Linux-v5.15/drivers/pwm/ |
| D | pwm-lpss-platform.c | 68 * knowing about this. On devices where the controller is unused in pwm_lpss_probe_platform()
|
| /Linux-v5.15/drivers/net/arcnet/ |
| D | Kconfig | 77 have always used the old ARCnet driver without knowing what type of
|
| /Linux-v5.15/arch/m68k/include/asm/ |
| D | mcfintc.h | 23 * related to) the actual interrupt number they use. So knowing the IRQ
|
| /Linux-v5.15/Documentation/arm/ |
| D | porting.rst | 10 The following symbol definitions rely on you knowing the translation that
|
| /Linux-v5.15/Documentation/ |
| D | index.rst | 71 knowing how things are done will make the process of getting your changes
|
| /Linux-v5.15/arch/sh/mm/ |
| D | cache-sh7705.c | 95 * number, knowing this would reduce the number of cache entries to be in __flush_dcache_page()
|
| /Linux-v5.15/drivers/input/ |
| D | input-poller.c | 77 * printed backtrace as knowing what instance of input in input_setup_polling()
|
| /Linux-v5.15/arch/m68k/coldfire/ |
| D | sltimers.c | 135 /* initialize mcfslt_cnt knowing that slice timers count down */ in hw_timer_init()
|
| /Linux-v5.15/Documentation/dev-tools/ |
| D | testing-overview.rst | 8 There are a number of different tools for testing the Linux kernel, so knowing
|
| /Linux-v5.15/include/uapi/drm/ |
| D | panfrost_drm.h | 119 * means that tools like valgrind end up knowing about the mapped
|
| /Linux-v5.15/include/uapi/linux/ |
| D | rfkill.h | 167 * 2. accept short reads, knowing that this means it's running on an
|
| /Linux-v5.15/Documentation/driver-api/gpio/ |
| D | intro.rst | 44 firmware knowing how they're used).
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 103 Another key information point in forensic analysis is knowing who the metadata
105 and/or corrupted, and how long ago that it was last modified. Knowing the owner
|
| /Linux-v5.15/drivers/usb/musb/ |
| D | musb_dma.h | 29 * - Knowing the correlation between dma channels and the
|
12345678
