Searched full:knowing (Results 1 – 25 of 315) sorted by relevance
12345678910>>...13
| /kernel/linux/linux-5.10/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-bus-pci | 191 Userspace applications interested in knowing the
203 Userspace applications interested in knowing the
219 Userspace applications interested in knowing the
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-bus-vfio-mdev | 71 Userspace applications interested in knowing the name of
84 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-bus-pci | 185 Userspace applications interested in knowing the
197 Userspace applications interested in knowing the
213 Userspace applications interested in knowing the
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mailbox/ |
| D | meson-mhu.txt | 7 received data. However, there is no specified way of knowing if the sent
|
| D | arm-mhu.txt | 7 received data. However, there is no specified way of knowing if the sent
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/include/linux/platform_data/ |
| D | pcf857x.h | 28 * inferred by reading the chip's value and knowing the last value written
|
| /kernel/linux/linux-4.19/include/linux/platform_data/ |
| D | pcf857x.h | 28 * inferred by reading the chip's value and knowing the last value written
|
| /kernel/linux/linux-5.10/include/net/ |
| D | cls_cgroup.h | 62 * disable bh. Knowing this, it is possible to detect softirq based in task_get_classid()
|
| /kernel/linux/linux-4.19/include/net/ |
| D | cls_cgroup.h | 62 * disable bh. Knowing this, it is possible to detect softirq based in task_get_classid()
|
| /kernel/linux/linux-5.10/drivers/leds/ |
| D | TODO | 41 Userspace is interested in knowing "this LED can produce arbitrary
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/gpio/ |
| D | gpio-pcf857x.txt | 8 low/high value, without knowing the last value written since the chip came out
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/ |
| D | gpio-pcf857x.txt | 8 low/high value, without knowing the last value written since the chip came out
|
| /kernel/linux/linux-4.19/scripts/dtc/ |
| D | srcpos.h | 101 * created without otherwise knowing a true source position.
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | index.rst | 59 knowing how things are done will make the process of getting your changes
|
| /kernel/linux/linux-4.19/drivers/net/arcnet/ |
| D | Kconfig | 76 have always used the old ARCnet driver without knowing what type of
|
| /kernel/linux/linux-5.10/drivers/net/arcnet/ |
| D | Kconfig | 77 have always used the old ARCnet driver without knowing what type of
|
| /kernel/linux/linux-4.19/Documentation/arm/ |
| D | Porting | 6 The following symbol definitions rely on you knowing the translation that
|
| /kernel/linux/linux-5.10/arch/m68k/include/asm/ |
| D | mcfintc.h | 23 * related to) the actual interrupt number they use. So knowing the IRQ
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | porting.rst | 10 The following symbol definitions rely on you knowing the translation that
|
| /kernel/linux/linux-4.19/arch/m68k/include/asm/ |
| D | mcfintc.h | 23 * related to) the actual interrupt number they use. So knowing the IRQ
|
12345678910>>...13