Home
last modified time | relevance | path

Searched full:somehow (Results 1 – 25 of 402) sorted by relevance

12345678910>>...17

/kernel/linux/linux-5.10/drivers/gpu/drm/msm/adreno/
Da2xx_gpu.h9 /* arrg, somehow fb.h is getting pulled in: */
Da4xx_gpu.h9 /* arrg, somehow fb.h is getting pulled in: */
Da3xx_gpu.h12 /* arrg, somehow fb.h is getting pulled in: */
/kernel/linux/linux-4.19/net/ax25/
DTODO12 The ax25_rt_find_route synopsys is pervert but I somehow had to deal with
/kernel/linux/linux-5.10/net/ax25/
DTODO12 The ax25_rt_find_route synopsys is pervert but I somehow had to deal with
/kernel/linux/linux-4.19/drivers/gpu/drm/msm/adreno/
Da4xx_gpu.h18 /* arrg, somehow fb.h is getting pulled in: */
Da3xx_gpu.h23 /* arrg, somehow fb.h is getting pulled in: */
/kernel/linux/linux-5.10/arch/mips/ralink/
Dill_acc.c53 /* somehow this driver breaks on RT5350 */ in ill_acc_of_setup()
/kernel/linux/linux-4.19/arch/mips/ralink/
Dill_acc.c55 /* somehow this driver breaks on RT5350 */ in ill_acc_of_setup()
/kernel/linux/linux-4.19/drivers/media/rc/keymaps/
Drc-kworld-plus-tv-analog.c53 Somehow, the original driver has a way to know,
/kernel/linux/linux-5.10/drivers/leds/
DTODO30 microcode. Split the drivers somehow.
/kernel/linux/linux-5.10/drivers/media/rc/keymaps/
Drc-kworld-plus-tv-analog.c57 Somehow, the original driver has a way to know,
/kernel/linux/linux-5.10/arch/hexagon/include/asm/
Dthread_info.h42 * used for syscalls somehow;
/kernel/linux/linux-4.19/Documentation/driver-api/firmware/
Drequest_firmware.rst5 You would typically load firmware and then load it into your device somehow.
/kernel/linux/linux-4.19/include/uapi/linux/
Dagpgart.h78 * The "prot" down below needs still a "sleep" flag somehow ...
/kernel/linux/linux-4.19/arch/hexagon/include/asm/
Dthread_info.h55 * used for syscalls somehow;
/kernel/linux/linux-5.10/include/uapi/linux/
Dagpgart.h78 * The "prot" down below needs still a "sleep" flag somehow ...
/kernel/linux/linux-5.10/Documentation/driver-api/firmware/
Drequest_firmware.rst5 You would typically load firmware and then load it into your device somehow.
/kernel/linux/linux-5.10/sound/aoa/codecs/
Dtoonie.c63 /* can we turn it off somehow? */ in toonie_suspend()
/kernel/linux/linux-4.19/tools/perf/util/
Dstrbuf.h38 * even if it's true in the current implementation. Alloc is somehow a
/kernel/linux/linux-4.19/include/linux/
Dagpgart.h51 * The "prot" down below needs still a "sleep" flag somehow ...
/kernel/linux/linux-5.10/tools/perf/util/
Dstrbuf.h38 * even if it's true in the current implementation. Alloc is somehow a
/kernel/linux/linux-4.19/sound/aoa/codecs/
Dtoonie.c65 /* can we turn it off somehow? */ in toonie_suspend()
/kernel/linux/linux-5.10/include/linux/
Dagpgart.h49 * The "prot" down below needs still a "sleep" flag somehow ...
/kernel/linux/linux-4.19/Documentation/
Dntb.txt56 3) somehow notify a peer device of performed initialization, 4) peer device
72 1) allocate a memory region, 2) somehow deliver a translated address to a peer

12345678910>>...17