Home
last modified time | relevance | path

Searched full:know (Results 1 – 25 of 1877) sorted by relevance

12345678910>>...76

/linux/arch/riscv/
H A DKconfig.errata22 If you don't know what to do here, say "Y".
66 If you don't know what to do here, say "Y".
77 If you don't know what to do here, say "Y".
118 If you don't know what to do here, say "Y".
131 If you don't know what to do here, say "Y".
144 If you don't know what to do here, say "Y".
155 If you don't know what to do here, say "Y".
H A DKconfig.vendor16 If you don't know what to do here, say Y.
29 If you don't know what to do here, say Y.
42 If you don't know what to do here, say Y.
55 If you don't know what to do here, say Y.
68 If you don't know what to do here, say Y.
H A DKconfig451 If you don't know what to do here, say N.
565 If you don't know what to do here, say Y.
595 If you don't know what to do here, say Y.
630 If you don't know what to do here, say Y.
651 If you don't know what to do here, say Y.
662 If you don't know what to do here, say Y.
713 If you don't know what to do here, say Y.
730 If you don't know what to do here, say Y.
765 If you don't know what to do here, say Y.
780 If you don't know what to do here, say Y.
[all …]
/linux/arch/microblaze/
H A DKconfig134 Unless you know what you are doing, say N here.
162 Say N here unless you know what you are doing.
188 Say N here unless you know what you are doing.
202 Say N here unless you know what you are doing.
216 Say N here unless you know what you are doing.
/linux/include/linux/
H A Damd-pmf-io.h19 * @MT_HPD: Message ID to know the Human presence info from MP2 FW
20 * @MT_ALS: Message ID to know the Ambient light info from MP2 FW
21 * @MT_SRA: Message ID to know the SRA data from MP2 FW
22 * @MT_OP_MODE: Message ID to know the operating-mode (tablet/laptop) info
/linux/tools/testing/selftests/bpf/progs/
H A Dverifier_var_off.c26 * &skb->pkt_type, but we don't know which \ in variable_offset_ctx_access()
52 * we don't know which \ in stack_read_priv_vs_unpriv()
185 * we don't know which \ in variable_offset_stack_read_uninitialized()
217 * fp-16, but we don't know which \ in stack_write_priv_vs_unpriv()
230 * were in the range of that write (even if the verifier doesn't actually know if
256 * we don't know which \ in stack_write_followed_by_read()
298 * we don't know which. \ in stack_write_clobbers_spilled_regs()
364 * we don't know which \ in access_max_out_of_bound()
422 * we don't know which \ in access_min_out_of_bound()
451 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know\ in access_min_off_min_initialized()
[all …]
/linux/Documentation/devicetree/bindings/
H A Dcommon-properties.txt15 know the peripheral always needs to be accessed in big endian (BE) mode.
17 unconditionally (e.g. readl/writel). Use this if you know the
71 by all of its devices. The driver needs to know how many devices the
/linux/Documentation/sound/cards/
H A Dbt87x.rst34 The driver is now stable. However, it doesn't know about many TV cards,
35 and it refuses to load for cards it doesn't know.
45 or not, so that future versions of this driver know about your card.
/linux/Documentation/power/
H A Dswsusp-dmcrypt.rst10 You know how dm-crypt works. If not, visit the following web page:
13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
14 You know how to create or how to modify an initrd.
119 Please don't mind the weird loop above, busybox's msh doesn't know
/linux/Documentation/i2c/
H A Dinstantiating-devices.rst6 level. Instead, the software must know which devices are connected on each
113 main chip by the means of an I2C bus. You won't know the number of the I2C
138 A variant of this is when you don't know for sure if an I2C device is
232 In general, the kernel should know which I2C devices are connected and
263 device is not officially supported yet but you know it is compatible.
272 available, and you don't need to know what driver the device needs.
/linux/arch/nios2/
H A DKconfig150 Say N here unless you know what you are doing.
164 Say N here unless you know what you are doing.
176 Say N here unless you know what you are doing.
/linux/sound/soc/bcm/
H A DKconfig21 If you don't know what to do here, say N.
30 If you don't know what to do here, say N
/linux/tools/usb/usbip/libsrc/
H A Dlist.h14 * sometimes we already know the next/prev entries and we can
37 * This is only for internal list manipulation where we know
67 * This is only for internal list manipulation where we know
/linux/Documentation/process/
H A Dmanagement-style.rst45 manage had better know the details better than you, so if they come to
49 (Corollary:if the people you manage don't know the details better than
56 makes you look like you know what you're doing, so what a kernel manager
118 Remember: they'd better know more about the details than you do, and
229 Then make the developer who really screwed up (if you can find them) know
231 future, but so that they know they owe you one. And, perhaps even more
/linux/drivers/auxdisplay/
H A DKconfig180 If you don't know, put '40' here.
193 If you don't know what your LCD uses, in doubt let 16 here for a 2x16, and
210 If you don't know, use the normal one (0).
219 port. But before assigning signals, the driver needs to know if it will
401 If you don't know what I'm talking about, load the parport module,
420 If you don't know what I'm talking about, ignore it.
465 If you don't know what I'm talking about, ignore it.
/linux/Documentation/fb/
H A Dmetronomefb.rst30 originally labeled 23P01201_60_WT0107_MTC. I do not know what it stands for.
33 I neither have access to nor know exactly what the waveform does in terms of
/linux/Documentation/scsi/
H A D53c700.rst37 driver, you need to know three things about the way the chip is wired
44 Optionally, you may also need to know other things, like how to read
69 This will be a standard SCSI driver (I don't know of a good document
/linux/drivers/uio/
H A DKconfig12 If you don't know what to do here, say N.
39 If you don't know what to do here, say N.
56 If you don't know what to do here, say N.
/linux/Documentation/core-api/
H A Ddma-attributes.rst87 - You know that the accesses to this memory won't thrash the TLB.
88 You might know that the accesses are likely to be sequential or
92 - You know that the penalty of TLB misses while accessing the
96 - You know that the DMA mapping is fairly transitory. If you expect
/linux/drivers/gpu/drm/i915/gt/
H A Dintel_timeline_types.h77 * global_seqno. When we know that all tracked fences are completed
78 * (i.e. when the driver is idle), we know that the syncmap is
/linux/Documentation/devicetree/bindings/power/supply/
H A Dmediatek,mt6370-charger.yaml23 We need to use the IRQ "MT6370_IRQ_OVPCTRL_UVP_D" to know when USB
26 IRQ "MT6370_IRQ_ATTACH" will be triggered, and the driver will know
/linux/Documentation/userspace-api/gpio/
H A Dsysfs.rst24 know for example that GPIO #23 controls the write protect line used to
29 and the kernel would have no need to know about it.
33 standard kernels won't know about. And for some tasks, simple userspace
/linux/Documentation/locking/
H A Dspinlocks.rst35 sequences that you **know** need to be split up: avoid it at all cost if you
109 cheaper versions of the spinlocks. IFF you know that the spinlocks are
118 This is useful if you know that the data in question is only ever
/linux/Documentation/usb/
H A Dacm.rst38 Many modems do, here is a list of those I know of:
48 I know of one ISDN TA that does work with the acm driver:
52 Some cell phones also connect via USB. I know the following phones work:
/linux/drivers/usb/gadget/
H A Depautoconf.c48 * about how to use the USB controller, and it can't know all
89 * and wants to know the maximum possible, provide the info. in usb_ep_autoconfig_ss()
137 * USB controller, and it can't know all the restrictions that may apply.

12345678910>>...76