| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-bus-vfio-mdev | 72 Userspace applications interested in knowing the name of
85 Userspace applications interested in knowing the details of
|
| H A D | debugfs-ec | 8 Knowing the EC GPE one can watch the amount of HW events related to
|
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mailbox/ |
| H A D | amlogic,meson-gxbb-mhu.yaml | 17 received data. However, there is no specified way of knowing if the sent
|
| H A D | arm,mhu.yaml | 16 However, there is no specified way of knowing if the sent data has been read
|
| /OK3568_Linux_fs/kernel/include/linux/platform_data/ |
| H A D | pcf857x.h | 28 * inferred by reading the chip's value and knowing the last value written
|
| /OK3568_Linux_fs/kernel/include/net/ |
| H A D | cls_cgroup.h | 62 * disable bh. Knowing this, it is possible to detect softirq based in task_get_classid()
|
| /OK3568_Linux_fs/kernel/drivers/leds/ |
| H A D | TODO | 41 Userspace is interested in knowing "this LED can produce arbitrary
|
| /OK3568_Linux_fs/u-boot/drivers/core/ |
| H A D | syscon-uclass.c | 33 * With OF_PLATDATA we really have no way of knowing the format of in syscon_pre_probe()
|
| /OK3568_Linux_fs/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | gpio-pcf857x.txt | 8 low/high value, without knowing the last value written since the chip came out
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio-pcf857x.txt | 8 low/high value, without knowing the last value written since the chip came out
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-gnome/librsvg/ |
| H A D | librsvg_2.52.7.bb | 42 # This breaks here because the linker isn't going to work without at least knowing where
|
| /OK3568_Linux_fs/u-boot/scripts/dtc/ |
| H A D | srcpos.h | 101 * created without otherwise knowing a true source position.
|
| /OK3568_Linux_fs/kernel/drivers/net/arcnet/ |
| H A D | Kconfig | 77 have always used the old ARCnet driver without knowing what type of
|
| /OK3568_Linux_fs/kernel/Documentation/arm/ |
| H A D | porting.rst | 10 The following symbol definitions rely on you knowing the translation that
|
| /OK3568_Linux_fs/kernel/arch/m68k/include/asm/ |
| H A D | mcfintc.h | 23 * related to) the actual interrupt number they use. So knowing the IRQ
|
| /OK3568_Linux_fs/u-boot/drivers/usb/musb-new/ |
| H A D | musb_dma.h | 30 * - Knowing the correlation between dma channels and the
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/drm/ |
| H A D | v3d_drm.h | 150 * means that tools like valgrind end up knowing about the mapped
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/licenses/ |
| H A D | GPL-2.0-with-lmbench-restriction | 64 than required). The art lies in knowing which operations are
|
| /OK3568_Linux_fs/kernel/Documentation/ |
| H A D | index.rst | 71 knowing how things are done will make the process of getting your changes
|
| /OK3568_Linux_fs/kernel/drivers/input/ |
| H A D | input-poller.c | 77 * printed backtrace as knowing what instance of input in input_setup_polling()
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/as.html/ |
| H A D | Constants.html | 74 inspection, without knowing any context. Like this:
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/as.html/ |
| H A D | Constants.html | 74 inspection, without knowing any context. Like this:
|
| /OK3568_Linux_fs/kernel/arch/m68k/coldfire/ |
| H A D | sltimers.c | 136 /* initialize mcfslt_cnt knowing that slice timers count down */ in hw_timer_init()
|
| /OK3568_Linux_fs/u-boot/drivers/gpio/ |
| H A D | pcf8575_gpio.c | 40 * value ... without knowing the last value written since the chip
|