Searched full:know (Results 1 – 25 of 444) sorted by relevance
12345678910>>...18
| /Documentation/devicetree/bindings/ |
| D | common-properties.txt | 15 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
|
| /Documentation/sound/cards/ |
| D | bt87x.rst | 34 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.
|
| /Documentation/fb/ |
| D | metronomefb.rst | 30 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
|
| /Documentation/power/ |
| D | swsusp-dmcrypt.rst | 10 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
|
| /Documentation/core-api/ |
| D | dma-attributes.rst | 87 - 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
|
| /Documentation/filesystems/ |
| D | hpfs.rst | 95 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV"
105 chgrp symlinks but I don't know what is it good for. chmoding symlink results
110 extended attributes and partly in OS2SYS.INI. I don't want (and don't know how)
146 should work. If you have OS/2 server, use only read-only mode. I don't know how
148 list, I don't know how to delete them when file is deleted and how to not
180 reasons. If you extremely wish to update them, let me know, I'll write it (but
187 anybody know what does it mean?
201 whole created by this driver, it is BUG - let me know about it.
259 1.93 Modified, so that it works with kernels >= 2.1.131, I don't know if it
|
| /Documentation/mm/damon/ |
| D | design.rst | 19 To know how user-space can do the configurations and start/stop DAMON, refer to
77 To know how user-space can do the configuration via :ref:`DAMON sysfs interface
154 To know how user-space can set the attributes via :ref:`DAMON sysfs interface
306 To know how user-space can set ``apply_interval`` via :ref:`DAMON sysfs
358 To know how user-space can set the action via :ref:`DAMON sysfs interface
375 To know how user-space can set the access pattern via :ref:`DAMON sysfs
398 To know how user-space can set the basic quotas via :ref:`DAMON sysfs interface
429 To know how user-space can set the prioritization weights via :ref:`DAMON sysfs
462 To know how user-space can set the tuning goal metric, the target value, and/or
488 To know how user-space can set the watermarks via :ref:`DAMON sysfs interface
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | mediatek,mt6370-charger.yaml | 23 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
|
| /Documentation/i2c/ |
| D | instantiating-devices.rst | 6 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.
|
| D | dma-considerations.rst | 25 flag with it. Then, the I2C core and drivers know they can safely operate DMA
36 know their buffers are DMA safe. Users of i2c_transfer() must set the
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-w1 | 11 Users: any user space application which wants to know bus scanning
|
| /Documentation/ABI/removed/ |
| D | o2cb | 6 removed when new versions of ocfs2-tools which know to look
|
| /Documentation/scsi/ |
| D | 53c700.rst | 37 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
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-tee | 14 of this variable is to let systemd know whether
|
| D | sysfs-bus-rpmsg | 69 to the other processor, in order to let it know about the
70 creation of the channel (this way remote clients know they
|
| D | debugfs-ec | 18 Do not write to the Embedded Controller if you don't know
|
| /Documentation/process/ |
| D | management-style.rst | 45 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
|
| D | 7.AdvancedTopics.rst | 44 own terminology and concepts; a new user of git should know about refs,
124 need to know that you know what you're doing, and I need to be able
192 maintainers will not know that the reviewer has looked at the patch at all!
|
| /Documentation/i2c/muxes/ |
| D | i2c-mux-gpio.rst | 69 If you don't know the absolute GPIO pin numbers at registration time,
84 assign a dynamic ID to your device. If you do not know the absolute
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 12 good. But appreciate beauty when you see it - and let people know.
67 issue is that we don't know where the issue is because we can't see what's
92 have to rely on tracing, we have to know which tracepoints we're looking for,
131 wait for its proper time - but you won't know if it's the proper time for an
|
| /Documentation/userspace-api/media/dvb/ |
| D | intro.rst | 12 What you need to know
18 you should know what a program/transport stream (PS/TS) is and what is
27 It is also necessary to know how to access Linux devices and how to
|
| /Documentation/userspace-api/gpio/ |
| D | sysfs.rst | 24 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
|
| /Documentation/locking/ |
| D | spinlocks.rst | 35 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
|
| /Documentation/networking/ |
| D | 6pack.rst | 73 don't know anything about it. I used a textual description of the 6pack
149 so the 6pack driver doesn't know anything about connects or data that
163 with the serial driver of 2.0.3x kernels. I don't know yet if the problem
170 occur when there is a bare AX.25 connection still running. I don't know if
|
| /Documentation/usb/ |
| D | acm.rst | 38 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:
|
12345678910>>...18