| /linux-4.4.14/drivers/staging/media/ |
| D | Kconfig | 7 Most of them don't follow properly the V4L, DVB and/or RC API's,
12 If you wish to work on these drivers, to help improve them, or
13 to report problems you have with them, please use the
21 # Please keep them in alphabetic order
|
| /linux-4.4.14/drivers/pinctrl/intel/ |
| D | Kconfig | 27 allows configuring of SoC pins and using them as GPIOs.
43 configuring of SoC pins and using them as GPIOs.
52 using them as GPIOs.
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | vexpress | 21 from a wide range of boards, each of them containing (apart of the main
26 temperature and power usage. Some of them also calculate consumed energy
33 Tree passed to the kernel. Details of the DT binding for them can be found
|
| D | userspace-tools | 16 setup monitoring limits etc. You can get them on their homepage
29 3) load them and run "sensors" command, you should see some results.
|
| D | adm1021 | 71 ADM1021-clones implement two temperature sensors. One of them is internal,
96 within them, with two temperature sensors. Other Xeon processors of this
111 FSB and faster) lost them, until the Core-based generation which
|
| D | max1619 | 27 other second; reading them more often will do no harm, but will return
|
| D | w83781d | 50 chips, and the Asus AS99127F chips. We will refer to them collectively as
54 enough that it was sensible to put them together in one driver.
66 of the chip, use a 'force' parameter; this will put them into a more
151 The chips only update values each 1.5 seconds; reading them more often
171 how to handle them. More details below.
223 them and obtain 32-byte data, and you can fill the 32-byte data to the
229 > How do I program them for diode inputs? I can't find any register
393 fans run at low speed, and 0x7F or 0x80 to make them run at full speed.
|
| D | smsc47m192 | 49 Reading them more often repeats the same values.
85 Writing a non-zero number to one of them will reset the other
|
| D | ibmpowernv | 16 for sensor devices during the __init phase and registers them with the 'hwmon'.
|
| D | g760a | 35 other second; reading them more often will do no harm, but will return
|
| D | pc87360 | 30 all temperature channels, because some of them share pins with each other,
127 external thermal diode channels, so you (physically) can't use them all at
139 external. Some of them (in7:Vsb, in8:Vdd and in10:AVdd) are divided by two
|
| D | w83l785ts | 29 every other second; reading them more often will do no harm, but will
|
| D | max6650 | 63 understand the meaning of these parameters before you attempt to change them.
|
| D | acpi_power_meter | 28 When both of them are set, an ACPI event will be broadcast on the ACPI netlink
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | README.modules | 21 but not .midi. As the help for them says, set them unless you know your
45 set. They will not work without them. Change as appropriate for your card.
79 deallocate them during close(). Linux can often have problems allocating
85 them when the module is unloaded. For this to be effective we need to load
87 init script, and keep them around until we shut down. This is a little
106 hints, send them to me, Jim Bray, jb@as220.org, http://as220.org/jb.
|
| D | PSS | 22 machines and will cause a crash on them.
|
| /linux-4.4.14/Documentation/i2c/ |
| D | ten-bit-addresses | 4 address 0x10 (though a single device could respond to both of them).
16 hardware doesn't support them (SMBus doesn't require 10-bit address
28 needs them to be fixed.
|
| D | instantiating-devices | 122 on cheap variants of a board but you have no way to tell them apart), or
185 destroyed automatically when the driver which detected them is removed,
197 them (by the means of the class bitfield), while all I2C buses were
215 must write the right parameters to them in order to properly instantiate,
|
| /linux-4.4.14/drivers/media/usb/ttusb-dec/ |
| D | Kconfig | 18 download/extract them, and then copy them to /usr/lib/hotplug/firmware
|
| /linux-4.4.14/arch/score/ |
| D | Kconfig.debug | 15 some command-line options at build time by entering them here. In
17 to set them up in board prom initialization routines.
|
| /linux-4.4.14/drivers/staging/rdma/ |
| D | Kconfig | 15 If you wish to work on these drivers, to help improve them, or
16 to report problems you have with them, please use the
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 18 but not explicitly acknowledged them to firmware and
24 entries, read them out and acknowledge them.
|
| D | vdso | 7 your platform's ABI. Call them from a sensible context. (For example,
|
| D | sysfs-firmware-efi-vars | 13 associated with them.
|
| /linux-4.4.14/drivers/staging/ |
| D | Kconfig | 8 them. Please note that these drivers are under heavy
17 If you wish to work on these drivers, to help improve them, or
18 to report problems you have with them, please see the
|
| /linux-4.4.14/arch/ia64/hp/sim/boot/ |
| D | bootloader.lds | 20 can access them all, and initialized data all before uninitialized, so
42 of the section so we begin them at 0. */
|
| /linux-4.4.14/Documentation/x86/ |
| D | intel_mpx.txt | 105 them somewhere. It has two special instructions for this which allow
117 the instructions for moving bounds in and out of them are extremely
124 are a few ways this could be done. We don't think any of them are practical
128 never have to allocate them?
132 even if we clean them up aggressively. In the worst-case scenario, the
136 If we were to preallocate them for the 128TB of user virtual address
160 bounds tables that we could think of, we create them on demand in
200 knowledge, it is also responsible for freeing them when the associated
233 directory at them through XSAVE instruction, and then set valid bit
238 them at the same bounds table.
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-firmware-efi-runtime-map | 12 can reassemble them and pass them into the kexec kernel.
|
| D | sysfs-firmware-sfi | 12 can observe them this way:
|
| D | sysfs-bus-rpmsg | 24 dispatches them to the listening entity (a kernel driver).
42 dispatches them to the listening entity.
|
| D | sysfs-devices-power_state | 18 some other devices using them at the moment.
|
| D | sysfs-firmware-dmi-tables | 14 through sysfs as an alternative to utilities reading them
|
| D | debugfs-ec | 15 or writing to them.
|
| D | sysfs-devices-real_power_state | 21 other devices using them at the moment.
|
| D | sysfs-bus-fcoe | 74 (Ethernet) packets, unpack them, and forward the embedded
76 outbound FC frames and pack them in Ethernet packets to
|
| D | configfs-stp-policy | 32 them.
|
| D | sysfs-driver-samsung-laptop | 8 of sense, but some users like to modify them to keep
|
| D | sysfs-block-dm | 39 them.
|
| D | sysfs-kernel-mm-ksm | 24 pages_sharing: how many more sites are sharing them i.e. how
|
| /linux-4.4.14/Documentation/input/ |
| D | gamepad.txt | 40 differently labeled on most devices so we define them as NORTH,
52 Analog-sticks may also provide a digital button if you press them.
55 Not all devices provide them, but the upper buttons are normally named
68 Legacy drivers often don't comply to these rules. As we cannot change them
70 user-space yourself. Some of them might also provide module-options that
79 and one analog stick. It reports them as if it were a gamepad with only one
|
| D | userio.txt | 9 easier by allowing them to test various serio devices (mainly the various
11 of them. userio accomplishes this by allowing any privileged userspace program
|
| D | input.txt | 48 These modules get events from input and pass them where needed via
55 you'll have to load the following modules (or have them built in to the
103 handles all HID devices, and because there is a very wide variety of them,
163 x86), and passes them into the handle_scancode function of the
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | tmio_mmc.txt | 6 describe hardware capabilities, known to them, or are obtained by them from
|
| /linux-4.4.14/drivers/memstick/core/ |
| D | Kconfig | 12 normal behaviour is to remove them at suspend and
13 redetecting them at resume. Breaking this assumption will
|
| /linux-4.4.14/Documentation/acpi/ |
| D | scan_handlers.txt | 22 information from the device objects represented by them and populating them with
23 appropriate data, but some of them require additional handling after they have
50 to match a scan handler against each of them using the ids arrays of the
|
| D | gpio-properties.txt | 59 them.
68 mapping between those names and the ACPI GPIO resources corresponding to them.
|
| D | enumeration.txt | 26 I2C), creates the physical devices and binds them to their ACPI handle in
142 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
307 we need to translate them to the corresponding Linux GPIO descriptors.
340 parts of the ACPI namespace that relate to them. In the Linux MFD subsystem
383 Section 6.1.2 of ACPI 6.0 for details) and the DT namespace is not one of them.
|
| /linux-4.4.14/Documentation/parisc/ |
| D | registers | 94 r1,r2,r19-r26,r28,r29 & r31 can be used without saving them first. And of
95 course, you need to save them if you care about them, before calling
113 r23-r26: these are arg3-arg0, i.e. you can use them if you
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | README.WINVIEW | 18 use this driver, send an email insult to them, and tell them you won't
|
| /linux-4.4.14/fs/ufs/ |
| D | Kconfig | 9 these partitions; if you also want to write to them, say Y to the
21 When accessing NeXTstep files, you may need to convert them from the
|
| /linux-4.4.14/Documentation/usb/ |
| D | wusb-cbaf | 45 (connection key). Device saves them for the next time it wants to
46 connect wireless. We save them for that next time also so we can
|
| D | dma.txt | 15 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
132 calls (where the underlying DMA primitives have changed), most of them can
133 easily be commented back in if you want to use them.
|
| D | misc_usbsevseg.txt | 10 can be obtained from the device to tell them apart.
|
| D | WUSB-Design-overview.txt | 66 other, so you could consider them different "busses". Initially this
67 driver considers them all a single one.
154 are in radio proximity to allow drivers to connect to them. As well, it
204 connect to them, but this is policy stuff and should be driven
294 among them are the bandwidth allocations that tell each device
321 has seen the port status changes, as we have been toggling them. It will
349 Each HC has a number of rpipes and buffers that can be assigned to them;
|
| /linux-4.4.14/Documentation/timers/ |
| D | hrtimers.txt | 49 them becomes necessary. Thus the users of these timeouts can accept
52 Accurate timing for them is not a core purpose - in fact most of the
53 timeout values used are ad-hoc. For them it is at most a necessary
109 time-changing code had to fix them up one by one, and all of them had to
122 1:1 mapping between them on the algorithmical level, and thus no real
|
| D | NO_HZ.txt | 105 task implies also omitting them for idle CPUs.
111 it allows them to improve their worst-case response times by the maximum
167 all of them over time. Adaptive-tick mode may prevent this
228 scheduler will decide where to run them, which might or might not be
229 where you want them to run.
260 dyntick-idle mode, an option that most of them take. However,
313 simply offloading RCU callbacks from all CPUs and pinning them
314 where you want them whenever you want them pinned.
|
| /linux-4.4.14/Documentation/ |
| D | email-clients.txt | 137 patches so do not GPG sign them. Signing patches that have been inserted
138 as inlined text will make them tricky to extract from their 7-bit encoding.
141 them as text, right click on the attachment and select properties, and
151 as read-write for user only so you will have to chmod them to make them
152 group and world readable if you copy them elsewhere.
180 to send them:
|
| D | VGA-softcursor.txt | 14 where 1, 2 and 3 are parameters described below. If you omit any of them,
24 (by simply XORing them with the value of this parameter). On standard VGA,
|
| D | ManagementStyle | 42 competent to make that decision for them.
108 sure as hell shouldn't encourage them by promising them that what they
109 work on will be included. Make them at least think twice before they
143 is fairly easy, and un-alienating them is hard. Thus "alienating"
183 Some people react badly to smart people. Others take advantage of them.
186 Suck up to them, because they are the people who will make your job
202 are doing something irreversible when you _do_ prod them in some
273 by trying to keep up with everybody else and running after them as fast
|
| D | intel_txt.txt | 106 instruction had put them in and place them into a wait-for-SIPI
123 or simply logging them and continuing.
139 them for correctness. The VT-d code will detect if the kernel was
182 which to find them are BIOS-specific.
|
| D | CodingStyle | 11 and NOT read it. Burn them, it's a great symbolic gesture.
87 printk messages, because that breaks the ability to grep for them.
127 special anyway (you can't nest them in C).
252 GLOBAL variables (to be used only if you _really_ need them) need to
297 The reason we have them for things like pte_t etc. is that there
363 descriptive names (you can ask the compiler to in-line them if you think
400 using GW-BASIC names like "err1:" and "err2:". Also don't name them after the
593 to worry about the structure suddenly going away from under them just
701 you have them, they can be a huge help for remote troubleshooting. However
721 about them.
[all …]
|
| D | SubmittingDrivers | 73 maintain them just once separate them out nicely and note
105 the author then patches will be redirected to them unless
|
| D | magic-number.txt | 150 memory management. See include/sound/sndmagic.h for complete list of them. Many
155 include/net/irda/irda.h for a complete list of them.
157 HFS is another larger user of magic numbers - you can find them in
|
| D | bt8xxgpio.txt | 14 find them used for low prices on the net.
|
| D | rpmsg.txt | 56 arrive, the rpmsg core dispatches them to the appropriate driver according
164 assigned for them).
167 is already created for them when they are probed by the rpmsg bus
177 additional rpmsg addresses, and bind them to different rx callbacks.
184 dynamically assign them an available rpmsg address (drivers should have
|
| D | HOWTO | 43 definitive reference for them. Please check the gcc info pages (`info
44 gcc`) for some information on them.
110 subject to scrutiny for content and style), but not following them
309 of them can be browsed at http://git.kernel.org/.
387 Many of the lists are hosted on kernel.org. Information on them can be
434 them at a technical level and either rework your patches or provide
500 English before sending them.
512 community feel that you are working with them, and not simply using them
532 and simplify (or simply re-order) patches before submitting them.
|
| D | unshare.txt | 132 shared by explicit request to share them when creating a process
190 that are being unshared, before associating them with the
204 appropriate context structures and then associate them with the
277 them individually as well as in combination with each
|
| /linux-4.4.14/scripts/ |
| D | module-common.lds | 4 * combine them automatically.
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | 00-INDEX | 14 - how to build modules and to install them
|
| /linux-4.4.14/Documentation/ABI/ |
| D | README | 16 them will be guaranteed for at least 2 years. Most interfaces
25 errors or security problems are found in them. Userspace
31 notify them if any changes occur (see the description of the
|
| /linux-4.4.14/tools/perf/ |
| D | Makefile | 65 # and thus won't rebuilt them once they are in place.)
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | smsc-lan87xx.txt | 3 Some boards require special tuning values. Configure them
|
| /linux-4.4.14/Documentation/networking/ |
| D | atm.txt | 6 If you encounter problems with ATM, please report them on the ATM
|
| D | tuntap.txt | 15 instead of receiving packets from physical media, receives them from
17 writes them to the user space program.
46 If you want to create persistent devices and give ownership of them to
204 media, receives them from user space program and instead of sending
205 packets via physical media sends them to the user space program.
|
| D | phy.txt | 23 accessed are, in fact, busses, the PHY Abstraction Layer treats them as such.
48 time, so it is safe for them to block, waiting for an interrupt to signal
118 and perform specific operations based on them.
127 values pruned from them which don't make sense for your controller (a 10/100
163 might need to avoid them).
186 Requests the IRQ for the PHY interrupts, then enables them for
187 start, or disables then frees them for stop.
|
| D | alias.txt | 34 refer to them as usual (ifconfig, route, etc).
|
| D | netdev-features.txt | 15 splitting packets, classifying them. Those capabilities and their state
101 This section describes semantics of some of them.
130 stack. Driver should not change behaviour based on them.
|
| D | regulatory.txt | 14 Due to the dynamic nature of regulatory domains we keep them
83 can use this to review the changes made and also review who made them
90 do not need a callback as the channels registered by them are
|
| D | de4x5.txt | 110 remove them for Alphas since the Tulip hardware only does longword
112 longword aligned data copies (which makes them really slow). No comment.
142 linux/drivers/net/Space.c to make room for them. Hence, module loading
|
| D | ltpc.txt | 24 the driver will try to determine them itself.
28 them as options in a configuration file in /etc/modprobe.d/ directory:
|
| D | ray_cs.txt | 29 will find them all.
133 sent up by the card, so you will never see them (ack, rts, cts, probe
|
| D | spider_net.txt | 37 buffers, and marks them "full". The OS follows up, taking the full
38 buffers, processing them, and re-marking them empty.
115 the hardware can fill them, there is no problem. If, for some reason,
|
| D | openvswitch.txt | 81 them as comma-separated strings, with parentheses indicating arguments
131 some but not all of them. However, this behavior may change in future versions.
198 and therefore will not misinterpret them. (Also, the outer eth_type
212 handle them individually.
|
| /linux-4.4.14/Documentation/block/ |
| D | null_blk.txt | 19 - Directly accepts bio data structure and returns them.
21 All of them have a completion queue for each core in the system.
|
| D | data-integrity.txt | 49 encouraged them to allow separation of the data and integrity metadata
52 The controller will interleave the buffers on write and split them on
76 them within the Storage Networking Industry Association.
242 It is up to the receiver to process them and verify data
|
| /linux-4.4.14/drivers/usb/ |
| D | README | 24 them.
34 the various gadget drivers which talk to them.
|
| D | Kconfig | 64 them all if you are not certain.
161 LEDs and you want to use them as activity indicators for USB host or
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | ppc-pv.txt | 6 instructions and can emulate them accordingly.
13 and transforms them into unprivileged ones with some help from the hypervisor.
82 registers. Only if the host supports the additional features, make use of them.
100 feature before using them!
204 them are handled in the kernel, some are handled in user space. This is only
|
| D | review-checklist.txt | 15 5. New features must default to off (userspace should explicitly request them).
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | arndale.txt | 13 Arndale Boards has many audio daughter cards, one of them is
|
| /linux-4.4.14/Documentation/dvb/ |
| D | opera-firmware.txt | 20 Copy them into /lib/firmware/ .
|
| D | udev.txt | 32 like you know them. All real distributions out there scan the /etc/udev/rules.d
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | hpfs.txt | 43 What to do with extended attributes. 'no' - ignore them and use always
45 attributes but do not create them. 'rw' - create extended attributes
135 list, I don't know how to delete them when file is deleted and how to not
136 overwrite them with extended attributes. Send me some info on these structures
138 structures, remount read-only and not destroy them (I hope).
166 reasons. If you extremely wish to update them, let me know, I'll write it (but
182 correctly and writes warning if it finds them. If you see this message, this is
199 marks them as short (and writes "minor fs error corrected"). This bug is not in
245 not 100% ok, I have no info on it and OS/2 doesn't want to create them)
|
| D | dlmfs.txt | 57 destroyed and locks within them accessed.
89 domain directory. Locking against them is done via the open(2) system
116 supported locally as well. This means you can use them to restrict
|
| D | directory-locking | 21 lock both, lock them in inode pointer order.
92 Otherwise the set of contended objects would be infinite - each of them
126 either to make sure that link(2) doesn't work for them or to make changes
|
| D | sysfs-pci.txt | 59 The read only files are informational, writes to them will be ignored, with
93 underlying platform supports them. They're located in the PCI class hierarchy,
|
| D | gfs2.txt | 7 simultaneously use a block device that is shared between them (with FC,
|
| D | affs.txt | 8 hard disks and normally not used on them, either.
130 are some, not always subtle, differences. One of them becomes apparent
135 can be used to access them. Thus, symbolic links can point to a
|
| /linux-4.4.14/Documentation/hid/ |
| D | hid-transport.txt | 13 devices and register them with the HID bus. HID core then loads generic device
57 They allocate HID device objects and register them with HID core. Transport
92 will describe them as two bi-directional channels as they have several
125 and never reported spontaneously. A host can read and/or write them to access
158 specification does not allow them.
163 if the specification does not allow them.
232 devices are already set up before transport drivers register them to HID core
241 destroyed them via hid_destroy_device().
|
| /linux-4.4.14/Documentation/devicetree/bindings/rtc/ |
| D | armada-380-rtc.txt | 11 * "rtc-soc" for the SoC related registers and among them the one
|
| /linux-4.4.14/net/packet/ |
| D | Kconfig | 10 protocol implemented in the kernel, e.g. tcpdump. If you want them
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | delay.txt | 5 and maps them to different devices.
|
| D | linear.txt | 35 # Split a device into 4M chunks and then join them together in reverse order.
|
| D | dm-flakey.txt | 13 which can delay reads and writes and/or send them to different
|
| /linux-4.4.14/drivers/uwb/ |
| D | Kconfig | 21 below. It is ok to select all of them, no harm done.
37 them come with a Wireless USB host controller also.
|
| /linux-4.4.14/Documentation/vm/ |
| D | unevictable-lru.txt | 94 system - which means we get to use the same code to manipulate them, the
95 same code to isolate them (for migrate, etc.), the same code to keep track
195 the pages in the region and "rescue" them from the unevictable list if no other
196 condition is keeping them unevictable. If an unevictable region is destroyed,
198 freeing them.
256 were not migratable as isolate_lru_page() could not find them, and the LRU list
260 attempting to isolate them, thus abandoning the count of VM_LOCKED VMAs. When
326 do end up getting faulted into this VM_LOCKED VMA, we'll handle them in the
360 these mappings are inherently pinned, so we don't need to mark them as
363 so there is no sense in attempting to visit them.
[all …]
|
| D | ksm.txt | 15 by sharing the data common between them. But it can be useful to any
86 pages_sharing - how many more sites are sharing them i.e. how much saved
|
| /linux-4.4.14/fs/affs/ |
| D | Changes | 65 - disable link to directories until we can properly support them.
124 systems, since you can't run programs on them.
210 be smart about them, but the result is worth the
234 bitmap pointers read only, also allows them
265 them (e. g. the loopback device does this).
|
| /linux-4.4.14/drivers/staging/rtl8723au/ |
| D | TODO | 8 of them will require refactoring
|
| /linux-4.4.14/drivers/md/bcache/ |
| D | Kconfig | 25 interface to list them, which makes it possible to see asynchronous
|
| /linux-4.4.14/Documentation/power/ |
| D | notifiers.txt | 46 PM_POST_HIBERNATION if one of them fails for PM_HIBERNATION_PREPARE, and
47 all of the notifiers are called for PM_POST_SUSPEND if one of them fails for
|
| D | basic-pm-debugging.txt | 68 To use one of them it is necessary to write the corresponding string to
118 them), you have to unload it every time before hibernation. In that case please
165 before hibernation, and please report the problem with it(them).
190 hibernation, so please refer to Section 1 for more information about them. In
204 you will have to unload them every time before an STR transition (ie. before
205 you run s2ram), and please report the problems with them.
|
| D | power_supply_class.txt | 15 power supply, specific monitoring hardware may not be able to provide them
16 all, so any of them may be skipped.
38 kind of power supply, and can process/present them to a user in consistent
62 ~ of battery, this class distinguish these terms. Don't mix them! ~
|
| D | freezing-of-tasks.txt | 102 metadata on disks, we cannot bring them back to the state from before the
107 making them almost impossible to repair). We therefore freeze tasks that might
115 devices are deactivated, because we generally need them for swapping out. Then,
117 additional memory and we prevent them from doing that by freezing them earlier.
199 If keeping them is not practical, for example due to their size, they must be
|
| D | suspend-and-interrupts.txt | 18 block interrupts from them anyway. Also, in the past we had problems with
19 interrupt handlers for shared IRQs that device drivers implementing them were
25 resume, was the only practical way to mitigate them.
|
| /linux-4.4.14/Documentation/fmc/ |
| D | carrier.txt | 208 called before reprogramming and the carrier should refuse them
259 #define FMC_GPIO_RAW(x) (x) /* 4096 of them */
260 #define FMC_GPIO_IRQ(x) ((x) + 0x1000) /* 256 of them */
261 #define FMC_GPIO_LED(x) ((x) + 0x1100) /* 256 of them */
262 #define FMC_GPIO_KEY(x) ((x) + 0x1200) /* 256 of them */
263 #define FMC_GPIO_TP(x) ((x) + 0x1300) /* 256 of them */
264 #define FMC_GPIO_USER(x) ((x) + 0x1400) /* 256 of them */
|
| /linux-4.4.14/fs/hpfs/ |
| D | Kconfig | 10 option in order to be able to read them. Read
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer-sunxi.txt | 9 firmware / bootloader use, and the OS should ignore them.
|
| /linux-4.4.14/arch/parisc/math-emu/ |
| D | README | 3 Linux coding style, please leave them in their funny format just in case
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | bfticu.txt | 5 them to a single controller.
|
| /linux-4.4.14/Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets | 7 assign them to cpusets and their attached tasks. This is a way of limiting the
50 available to them according to the fake nodes assigned as mems:
|
| /linux-4.4.14/Documentation/scsi/ |
| D | osst.txt | 8 get them started using (and maybe debugging) it.
35 devices. If those are not present, you may create them by calling
45 So you could only have either of them being present in the kernel. This has
171 Note that most of them did mostly spend their spare time for the creation of
177 time for them and by integrating the driver into their distro.
|
| D | wd719x.txt | 12 d719x-wcs.bin files. Put them in /lib/firmware/.
|
| D | scsi-parameters.txt | 106 discovered. async scans them in kernel threads,
107 allowing boot to proceed. none ignores them, expecting
|
| /linux-4.4.14/arch/mips/sibyte/ |
| D | Platform | 2 # These are all rather similar so we consider them a single platform
|
| /linux-4.4.14/net/mpls/ |
| D | Kconfig | 22 that have had MPLS stack entries pushed onto them and thus
|
| /linux-4.4.14/drivers/staging/rtl8188eu/ |
| D | TODO | 8 of them will require refactoring
|
| /linux-4.4.14/Documentation/devicetree/bindings/iio/adc/ |
| D | xilinx-xadc.txt | 3 This binding document describes the bindings for both of them since the
9 interface. This binding document describes the bindings for both of them since
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | lpc32xx-mlc.txt | 11 Hz, to make them independent of actual clock speed and to provide for good
|
| D | lpc32xx-slc.txt | 13 (The following values are specified in Hz, to make them independent of actual
|
| D | nxp-spifi.txt | 27 none of them
|
| /linux-4.4.14/Documentation/devicetree/bindings/serial/ |
| D | fsl-lpuart.txt | 18 Note: Optional properties for DMA support. Write them both or both not.
|
| /linux-4.4.14/Documentation/devicetree/bindings/opp/ |
| D | opp.txt | 10 This document contain multiple versions of OPP binding and only one of them
49 phandles here. But only *one* of them should be chosen at runtime. This must be
59 tables are present), to uniquely identify them. The same list must be present
112 for few regulators, then this should be marked as zero for them. If it isn't
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | st,sti-irq-syscfg.txt | 6 This driver is used to unmask them prior to use.
|
| D | nvidia,tegra-ictlr.txt | 17 Each controller must be described separately (Tegra20 has 4 of them,
|
| /linux-4.4.14/fs/coda/ |
| D | Kconfig | 6 enables you to mount file systems of a remote server and access them
|
| /linux-4.4.14/drivers/gpu/vga/ |
| D | Kconfig | 27 to switch between them. This adds support for dynamic switching when
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-pca954x.txt | 21 multiplexers on the bus and the devices behind them use same I2C addresses.
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-fan.txt | 10 control value that should be set to achieve them. This array
|
| D | spear_spics.txt | 10 Chipselects can be controlled by software by turning them as GPIOs. SPEAr
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei-client-bus.txt | 11 stack and expose them through existing kernel subsystems.
50 In order for drivers to be notified of pending events waiting for them (e.g.
|
| /linux-4.4.14/arch/m68k/q40/ |
| D | README | 19 When something blocks interrupts (HD) it will lose some of them, so far
44 Various other PC drivers can be enabled simply by adding them to
112 because only irq's 4-15 can be disabled - and only all of them at once.
|
| /linux-4.4.14/fs/nilfs2/ |
| D | Kconfig | 15 and can change them into snapshots which will be preserved for long
|
| /linux-4.4.14/Documentation/pcmcia/ |
| D | driver-changes.txt | 35 dev_info_t and a few other typedefs are removed. No longer use them
75 exports for them were removed.
123 driver was reported to rely on them:
|
| /linux-4.4.14/arch/mips/ |
| D | Kconfig.debug | 64 build time by entering them here. In other cases you can specify
65 kernel args so that you don't have to set them up in board prom
135 it to make use of compact branch instructions where it deems them
|
| /linux-4.4.14/Documentation/locking/ |
| D | mutex-design.txt | 81 makes them more practically a hybrid type. By simply not interrupting a
109 list of all locks held in the system, printout of them.
156 region prevents the lock from being shared, always prefer them to any other
|
| /linux-4.4.14/Documentation/laptops/ |
| D | sonypi.txt | 29 Another option to intercept the events is to get them directly through the
42 specs for its laptops. If someone convinces them to do so, drop me a note.
131 continue to use them, don't use this driver.
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | fs.txt | 101 dynamically, but not to free them again. The three values in
126 dynamically, but can't free them yet.
131 need an inode struct to handle them. When you regularly run
143 Linux allocates them one pageful at a time.
178 limit total memory usage, and trying to increase them using fcntl() will be
|
| /linux-4.4.14/fs/befs/ |
| D | ChangeLog | 59 they work. I had forgotten all about them. (inode.c, symlink.c) [WD]
180 private portions to use them. (many files) [WD]
184 with kmalloc(). put_super and put_inode free them. This allows us not
192 * Removed fsync() hooks, since a read-only filesystem doesn't need them.
268 Made befs_readdir() use them them instead of the cruft in index.c.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 6.Followthrough | 29 will not keep them from asking a fundamental question: what will it be
56 thank them, and describe how you will answer their questions.
62 your explanations make sense, the reviewer will accept them. Should your
82 raised issues and how you dealt with them; the patch changelog is a good
85 time; if you help them get a running start, they will be in a better mood
141 the patch before. It may be tempting to ignore them, since there is no
|
| /linux-4.4.14/ |
| D | .gitignore | 3 # subdirectories here. Add them in the ".gitignore" file
|
| /linux-4.4.14/arch/frv/ |
| D | Kconfig.debug | 46 that GDB prints them as program output, say 'Y'.
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | paride.txt | 91 the PARIDE drivers into your kernel, or to build them as modules.
103 subsystem to try them all for you.
126 configure them as loadable modules, before attempting to compile a
141 how to identify them. This requires specifying the port address, the
153 will need them to identify the devices.
180 if you use them as loadable kernel modules.
368 While a lot of testing has gone into these drivers to make them work
|
| /linux-4.4.14/Documentation/security/ |
| D | apparmor.txt | 6 them run in an unconfined state which is equivalent to standard Linux DAC
|
| /linux-4.4.14/fs/gfs2/ |
| D | Kconfig | 11 that is shared between them (with FC, iSCSI, NBD, etc...). GFS reads
|
| /linux-4.4.14/Documentation/virtual/ |
| D | paravirt_ops.txt | 32 them are very performance critical.
|
| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-bus-usb | 24 devices to support suspend/resume, many of them do not.
|
| /linux-4.4.14/arch/mn10300/ |
| D | Kconfig.debug | 20 accesses to make sure the misalignment handler deals them with
70 that GDB prints them as program output, say 'Y'.
|
| /linux-4.4.14/arch/um/ |
| D | Kconfig.char | 86 which brings them up in xterms.
97 command line. The default value is "pty", which attaches them to
|
| D | Kconfig.net | 47 Slip Transport. You'll need at least one of them, but may choose
107 transports. You'll need at least one of them, but may choose
141 bridge if any of them need to be able to talk to their hosts or any
|
| /linux-4.4.14/Documentation/gpio/ |
| D | gpio-legacy.txt | 21 several dozen of them. Programmable logic devices (like FPGAs) can easily
87 use them; drivers don't need to add them explicitly.
100 numbers passed to them from that setup code, using platform_data to hold
141 a task context. However, for spinlock-safe GPIOs it's OK to use them
188 output, value) are constant. It's normal for them to need only a couple
202 Platforms that support this type of GPIO distinguish them from other GPIOs
383 map between them using calls like:
494 pulldowns integrated on some platforms. Not all platforms support them,
495 or support them in the same way; and any given board might use external
594 are normally integrated into platform initialization to make them always be
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | brcm,bus-axi.txt | 13 them manually through device tree. Use an interrupt-map to specify the
|
| D | simple-pm-bus.txt | 25 one of them is required):
|
| /linux-4.4.14/drivers/ras/ |
| D | Kconfig | 7 and help them stay available for long periods of time without
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | index.txt | 27 implement them?
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/st/ |
| D | st,quadfs.txt | 29 clock outputs but not all of them in a specific instance
|
| D | st,clkgen-vcc.txt | 26 clock outputs but not all of them in a specific instance
|
| /linux-4.4.14/Documentation/devicetree/bindings/hwlock/ |
| D | hwlock.txt | 21 Consumers that require specific hwlock(s) should specify them using the
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | changesets.txt | 3 will be applied, or none of them will be. If an error occurs partway
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | nfsd-admin-interfaces.txt | 34 fs/nfsd/nfsctl.c; most of them have detailed comments.
|
| /linux-4.4.14/fs/jffs2/ |
| D | LICENCE | 22 files and link them with other works to produce a work based on these
|
| /linux-4.4.14/arch/arm/mm/ |
| D | proc-v6.S | 226 bic r0, r0, r5 @ clear bits them
227 orr r0, r0, r6 @ set them
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | fw-memory.txt | 83 buffer area used for encoding, have to shift them by <<1 first.
91 buffer area used for decoding, have to shift them by <<1 first.
|
| /linux-4.4.14/arch/mn10300/kernel/ |
| D | head.S | 140 # them
170 # set up the registers with recognisable rubbish in them
|
| /linux-4.4.14/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 30 * Write requests are replicated to multiple servers and completed only when all of them are acked.
59 operations (like lookups or directory listings) between them according to IO priorities.
|
| /linux-4.4.14/arch/nios2/ |
| D | Kconfig | 110 some command-line options at build time by entering them here. In
112 to set them up in board prom initialization routines.
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | gen_except.S | 83 orl %d1,%d0 |put them in the right place
202 orl %d1,%d0 |put them in the right place
314 orl %d1,%d0 |put them in the right place
361 bfins %d0,NMCEXC(%a1){#4:#4} |and insert them in nmcexc
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.pcbit | 25 to my knowledge, very little use. If you want to see them implemented
|
| /linux-4.4.14/Documentation/s390/ |
| D | 3270.ChangeLog | 6 they affect work as right as 3270 can get them. Also, set
|
| /linux-4.4.14/Documentation/leds/ |
| D | leds-blinkm.txt | 10 the controller and run them. Also fading is an option.
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | cpm.txt | 13 others have them in the following order
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/uniphier/ |
| D | cache-uniphier.txt | 4 All of them have a level 2 cache controller, and some have a level 3 cache
|
| /linux-4.4.14/Documentation/devicetree/bindings/pci/ |
| D | xilinx-pcie.txt | 36 the four INTx interrupts in ISR and route them to this domain.
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-list.txt | 92 details. Some of them are referenced in the SEE ALSO section below.
97 Some pmu events listed by 'perf-list' will be displayed with '?' in them. For
|
| /linux-4.4.14/arch/m68k/math-emu/ |
| D | fp_movem.S | 51 | get register list and count them
205 | get register list and count them
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | si470x.txt | 96 After loading the module, you still have access to some of them in the sysfs
108 If you get any errors from snd_usb_audio, please report them to the ALSA people.
|
| D | README.cpia2 | 15 module was getting out of hand, so I separated them. It is not likely that
71 If the driver is compiled into the kernel, at boot time specify them
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | cachefiles.txt | 164 mountpoints, but the daemon can't avoid them.
179 permissions to prevent random users being able to access them directly.
226 their atimes have changed or if the kernel module says it is still using them.
242 to the graveyard from which the daemon will actually delete them.
303 or retire them.
456 then it will gather certain statistics and display them through a proc file.
|
| /linux-4.4.14/Documentation/arm/ |
| D | firmware.txt | 8 operations and call them when needed.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,saw2.txt | 8 system, notifying them when a low power state is entered or exited.
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | S3C2412.txt | 35 and reading or writing to them.
|
| D | GPIO.txt | 9 information about them.
89 of GPIO pins, and the configuration values for them. This
|
| /linux-4.4.14/drivers/pci/pcie/ |
| D | Kconfig | 77 Disable PCI Express ASPM L0s and L1, even if the BIOS enabled them.
|
| /linux-4.4.14/arch/arc/boot/dts/ |
| D | axc003.dtsi | 79 * So here we mimic a direct connection betwen them, ignoring the
|
| /linux-4.4.14/arch/arm/mach-sa1100/ |
| D | sleep.S | 136 @ Wow, now the hardware suspend request pins can be used, that makes them functional for
|
| /linux-4.4.14/drivers/media/ |
| D | Kconfig | 38 will disable support for them.
60 disable support for them.
|
| /linux-4.4.14/fs/reiserfs/ |
| D | README | 8 files are licensed under the GPL. The portions of them owned by Hans
53 Linux provider put them. There is some disagreement about how useful
56 distributors wanting them out of sync.:-) Please try to remember to
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
| D | crossbar.txt | 20 so crossbar bar driver should not consider them as free
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | cpm.txt | 46 mapping can cover them all while maintaining the ability to determine
|
| /linux-4.4.14/Documentation/devicetree/bindings/pwm/ |
| D | pwm-samsung.txt | 5 PWM timer block provides 5 PWM channels (not all of them can drive physical
|