/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-kernel-mm-ksm | 19 full_scans: how many times all mergeable areas have been 22 pages_shared: how many shared pages are being used. 24 pages_sharing: how many more sites are sharing them i.e. how 27 pages_to_scan: how many present pages to scan before ksmd goes 30 pages_unshared: how many pages unique but repeatedly checked 33 pages_volatile: how many pages changing too fast to be placed 40 sleep_millisecs: how many milliseconds ksm should sleep between
|
D | sysfs-kernel-slab | 19 The aliases file is read-only and specifies how many caches 48 The alloc_fastpath file shows how many objects have been 59 The alloc_from_partial file shows how many times a cpu slab has 71 The alloc_refill file shows how many times the per-cpu freelist 82 The alloc_slab file is shows how many times a new slab had to 93 The alloc_slowpath file shows how many objects have been 115 The cpu_slabs file is read-only and displays how many cpu slabs 124 The file cpuslab_flush shows how many times a cache's cpu slabs 147 The deactivate_empty file shows how many times an empty cpu slab 157 The deactivate_full file shows how many times a full cpu slab [all …]
|
D | sysfs-block | 80 indicates how many bytes the beginning of the device is 91 indicates how many bytes the beginning of the partition 161 parameter indicates how many bytes the beginning of the 172 parameter indicates how many bytes the beginning of the 226 configuration. write_same_max_bytes indicates how many
|
D | configfs-usb-gadget-uvc | 180 dwFrameInterval - indicates how frame interval can be 227 dwFrameInterval - indicates how frame interval can be 255 bTriggerUsage - how the host software will respond to
|
D | sysfs-block-dm | 31 Description: Allow control over how long a request that is a
|
D | sysfs-class-uwb_rc-wusbhc | 46 milliseconds that the WUSB host should use. This controls how
|
D | sysfs-firmware-gsmi | 24 for more information on how to interact with
|
/linux-4.1.27/Documentation/leds/ |
D | 00-INDEX | 8 - notes on how to use the leds-lp3944 driver. 10 - notes on how to use the leds-lp5521 driver. 12 - notes on how to use the leds-lp5523 driver. 14 - notes on how to use the leds-lp5562 driver. 18 - notes on how to use the leds-lm3556 driver.
|
D | ledtrig-oneshot.txt | 26 delay_on - specifies for how many milliseconds the LED has to stay at 30 delay_off - specifies for how many milliseconds the LED has to stay at
|
D | ledtrig-transient.txt | 6 specifying how long a state to be on, and the second for how long the state 8 in on state, followed by a delay_off value that specifies how long the LED
|
/linux-4.1.27/Documentation/ |
D | 00-INDEX | 23 - how the maintainers expect the C code in the kernel to look. 37 - the process and procedures of how to do Linux kernel development. 41 - how to select which CPU(s) handle which interrupt events on SMP. 51 - how to (attempt to) manage kernel hackers. 67 - how to change your VGA cursor from a blinking underscore. 75 - description of various trees and how to apply their patches. 89 - how to use kernel parameters to exclude bad RAM regions. 103 - info on how to use serial devices for Braille support. 105 - info on how to modify a bt8xx video card for GPIO usage. 111 - how to access I/O mapped memory from within device drivers. [all …]
|
D | HOWTO | 5 instructions on how to become a Linux kernel developer and how to learn 18 So, you want to learn how to become a Linux kernel developer? Or you 22 and hints on how to work with the community. It will also try to 46 Please remember that you are trying to learn how to work with the 74 invaluable for learning how to interact with the kernel community. When 76 documentation files are also added which explain how to use the feature. 104 These files describe in explicit detail how to successfully create 113 Other excellent descriptions of how to create patches properly are: 136 This document describes how Linux kernel maintainers operate and the 143 This file describes the rules on how the stable kernel releases [all …]
|
D | cpu-load.txt | 21 closely, however due to the nature of how/when the kernel collects 24 So how is this information collected? Whenever timer interrupt is
|
D | SubmittingDrivers | 4 This document is intended to explain how to submit device drivers to the 84 Clarity: It helps if anyone can see how to fix the driver. It helps 86 driver that intentionally obfuscates how the hardware works 157 http://www.fenrus.org/how-to-not-write-a-device-driver-paper.pdf
|
D | kobject.txt | 45 We'll look at how to create and manipulate all of these types. A bottom-up 63 this is analogous as to how "list_head" structs are rarely useful on 176 When the kobject is removed from the kernel (details on how to do that are 207 overkill. For more information on how to use struct kref, please see the 301 and default_attrs) control how objects of this type are represented in 324 - Ksets can support the "hotplugging" of kobjects and influence how 375 One might ask how, exactly, a kobject is added to a kset, given that no
|
D | BUG-HUNTING | 56 This is how to track down a bug if you know nothing about kernel hacking. 149 Nobody is going to tell you how to fix bugs. Seriously. You need to work it 150 out. But below are some hints on how to use the tools.
|
D | kernel-docs.txt | 111 What is it, how it works, operations taken when opening a file or 294 how your Operating System allows you to manage a large number of 314 understanding of what the kernel is, and how it is used. It was 335 you will see how USB devices communicate on the bus. The second 373 access them, how each lock is acquired, under what conditions it 487 Description: "This document describes how to write kernel device 489 describes how to write user-mode utilities for communicating with 514 Description: Interesting paper on how to abuse the Linux kernel in 667 it. Read it to see how to join the mailing list. Dozens of
|
D | DMA-ISA-LPC.txt | 6 This document describes how to do DMA transfers using the old ISA DMA 104 be 16-bit aligned for 16-bit transfers) and how many bytes to
|
D | preempt-locking.txt | 104 Notice how the preemption statements must encompass every reference of the 113 This code is not preempt-safe, but see how easily we can fix it by simply
|
D | applying-patches.txt | 9 A frequently asked question on the Linux Kernel Mailing List is how to apply 14 In addition to explaining how to apply and revert patches, a brief 15 description of the different kernel trees (and examples of how to apply 197 Here's how you'd go from 2.6.12.2 to 2.6.12.3 in a single step: 327 Here are 3 examples of how to apply these patches: 365 Here are some examples of how to apply these patches: 448 I hope you are now clear on how to apply the various patches and help testing
|
/linux-4.1.27/drivers/isdn/hisax/ |
D | Kconfig | 96 See <file:Documentation/isdn/README.HiSax> on how to configure it 106 See <file:Documentation/isdn/README.HiSax> on how to configure it 115 See <file:Documentation/isdn/README.HiSax> on how to configure it. 121 S0BOX. See <file:Documentation/isdn/README.HiSax> on how to 130 See <file:Documentation/isdn/README.HiSax> on how to configure it 139 See <file:Documentation/isdn/README.HiSax> on how to configure it. 145 See <file:Documentation/isdn/README.HiSax> on how to configure it. 153 See <file:Documentation/isdn/README.HiSax> on how to configure it 163 See <file:Documentation/isdn/README.HiSax> on how to configure it 173 See <file:Documentation/isdn/README.HiSax> on how to configure it [all …]
|
/linux-4.1.27/Documentation/ioctl/ |
D | 00-INDEX | 4 - how to avoid botching up ioctls 10 - how to decode the bits of an IOCTL code 12 - how to implement and register device/driver ioctl calls
|
/linux-4.1.27/drivers/staging/speakup/ |
D | varhandlers.c | 176 int spk_set_num_var(int input, struct st_var_header *var, int how) in spk_set_num_var() argument 189 if (how == E_NEW_DEFAULT) { in spk_set_num_var() 195 if (how == E_DEFAULT) { in spk_set_num_var() 199 if (how == E_SET) in spk_set_num_var() 203 if (how == E_INC) in spk_set_num_var() 205 else if (how == E_DEC) in spk_set_num_var() 273 int spk_set_mask_bits(const char *input, const int which, const int how) in spk_set_mask_bits() argument 278 if (how&1) { in spk_set_mask_bits() 299 if (how&2) { in spk_set_mask_bits()
|
D | speakup.h | 63 extern int spk_set_num_var(int val, struct st_var_header *var, int how); 66 extern int spk_set_mask_bits(const char *input, const int which, const int how);
|
/linux-4.1.27/Documentation/x86/ |
D | 00-INDEX | 12 - why and how Linux kernel uses exception tables on x86 14 - how to use x86 Memory Type Range Registers to increase performance 18 - how to fix/avoid quirks when using emulated PS/2 mouse/keyboard.
|
D | tlb.txt | 51 determine how long the flush operations are taking. 56 You can measure how expensive TLB refills are by using
|
D | early-microcode.txt | 32 The following example script shows how to generate a new combined initrd file in
|
/linux-4.1.27/Documentation/vm/ |
D | ksm.txt | 53 pages_to_scan - how many present pages to scan before ksmd goes to sleep 57 sleep_millisecs - how many milliseconds ksmd should sleep before next scan 69 compare how your system performs under each setting, before 85 pages_shared - how many shared pages are being used 86 pages_sharing - how many more sites are sharing them i.e. how much saved 87 pages_unshared - how many pages unique but repeatedly checked for merging 88 pages_volatile - how many pages changing too fast to be placed in a tree 89 full_scans - how many times all mergeable areas have been scanned
|
D | frontswap.txt | 56 failed_stores - how many store attempts have failed 57 loads - how many loads were attempted (all should succeed) 58 succ_stores - how many store attempts have succeeded 59 invalidates - how many invalidates were attempted 99 how much of the RAM is available for each of the clients! 151 3) OK, how about a quick overview of what this frontswap patch does 157 accessible by the kernel. Exactly how much memory it provides is 207 backend. In zcache, one cannot know a priori how compressible a page is.
|
D | 00-INDEX | 18 - how to use the Kernel Samepage Merging feature.
|
D | active_mm.txt | 11 > Is there a brief description someplace on how "mm" vs. "active_mm" in 50 "mm_users" counter that is how many "real address space users" there are,
|
D | transhuge.txt | 139 You can also control how many pages khugepaged should scan at each 144 and how many milliseconds to wait in khugepaged between each pass (you 149 and how many milliseconds to wait in khugepaged if there's an hugepage 162 max_ptes_none specifies how many extra small pages (that are 197 monitor how successfully the system is providing huge pages for use. 252 It is possible to establish how long the stalls were using the function 253 tracer to record how long was spent in __alloc_pages_nodemask and
|
/linux-4.1.27/samples/ |
D | Kconfig | 19 different kobject sample modules showing how to use kobjects, 46 different kfifo sample modules showing how to use the 55 Build an example of how to dynamically add the hello 62 Build an rpmsg client sample driver, which demonstrates how
|
/linux-4.1.27/arch/alpha/kernel/ |
D | process.c | 74 struct halt_info *how = (struct halt_info *)generic_ptr; in common_shutdown_1() local 102 if (how->mode == LINUX_REBOOT_CMD_RESTART) { in common_shutdown_1() 103 if (!how->restart_cmd) { in common_shutdown_1() 146 alpha_mv.kill_arch(how->mode); in common_shutdown_1() 148 if (! alpha_using_srm && how->mode != LINUX_REBOOT_CMD_RESTART) { in common_shutdown_1()
|
/linux-4.1.27/Documentation/frv/ |
D | README.txt | 22 A description of how to boot the kernel image and a summary of the kernel 28 A description of how to debug the kernel using GDB attached by serial 51 A description of how the FR-V kernel's atomic operations work.
|
/linux-4.1.27/tools/perf/util/ |
D | ordered-events.c | 226 int ordered_events__flush(struct ordered_events *oe, enum oe_flush how) in ordered_events__flush() argument 239 switch (how) { in ordered_events__flush() 268 str[how], oe->nr_events); in ordered_events__flush() 274 if (how == OE_FLUSH__ROUND) in ordered_events__flush() 277 oe->last_flush_type = how; in ordered_events__flush() 281 str[how], oe->nr_events); in ordered_events__flush()
|
D | ordered-events.h | 49 int ordered_events__flush(struct ordered_events *oe, enum oe_flush how);
|
/linux-4.1.27/Documentation/kbuild/ |
D | 00-INDEX | 4 - how to export Linux headers for use by userspace 14 - how to build modules and to install them
|
/linux-4.1.27/fs/autofs4/ |
D | expire.c | 299 int how) in autofs4_expire_direct() argument 303 int do_now = how & AUTOFS_EXP_IMMEDIATE; in autofs4_expire_direct() 347 int how) in should_expire() argument 349 int do_now = how & AUTOFS_EXP_IMMEDIATE; in should_expire() 350 int exp_leaves = how & AUTOFS_EXP_LEAVES; in should_expire() 429 int how) in autofs4_expire_indirect() argument 450 expired = should_expire(dentry, mnt, timeout, how); in autofs4_expire_indirect() 460 if (should_expire(expired, mnt, timeout, how)) { in autofs4_expire_indirect()
|
D | autofs_i.h | 165 struct autofs_sb_info *sbi, int how); 168 struct autofs_sb_info *sbi, int how);
|
D | dev-ioctl.c | 477 int how; in autofs_dev_ioctl_expire() local 479 how = param->expire.how; in autofs_dev_ioctl_expire() 482 return autofs4_do_expire_multi(sbi->sb, mnt, sbi, how); in autofs_dev_ioctl_expire()
|
/linux-4.1.27/security/selinux/ |
D | Kconfig | 9 If you are unsure how to answer this question, answer N. 23 If you are unsure how to answer this question, answer N. 38 If you are unsure how to answer this question, answer 1. 53 If you are unsure how to answer this question, answer N. 95 If you are unsure how to answer this question, answer 1. 113 If you are unsure how to answer this question, answer N. 128 If you are unsure how to answer this question, look for the
|
/linux-4.1.27/security/smack/ |
D | Kconfig | 13 If you are unsure how to answer this question, answer N. 31 If you are unsure how to answer this question, answer N. 42 If you are unsure how to answer this question, answer N.
|
/linux-4.1.27/security/ |
D | Kconfig | 19 If you are unsure how to answer this question, answer N. 32 If you are unsure how to answer this question, answer N. 41 If you are unsure how to answer this question, answer N. 50 If you are unsure how to answer this question, answer N. 63 If you are unsure how to answer this question, answer N. 72 If you are unsure how to answer this question, answer N. 99 See Documentation/intel_txt.txt for a description of how to enable
|
/linux-4.1.27/Documentation/video4linux/bttv/ |
D | THANKS | 17 components on their cards. (E.g. how the tuner type is detected) 20 - Hauppauge for telling how the sound input is selected and what components
|
D | README.freeze | 9 has a few hints how you can help to pin down the problem. 25 Read Documentation/oops-tracing.txt to learn how to get any useful
|
D | README.WINVIEW | 24 on their server are the full data-sheets, but don't ask how I found it.
|
/linux-4.1.27/arch/sh/kernel/ |
D | sh_bios.c | 63 void sh_bios_shutdown(unsigned int how) in sh_bios_shutdown() argument 65 sh_bios_call(BIOS_CALL_SHUTDOWN, how, 0, 0, 0); in sh_bios_shutdown()
|
/linux-4.1.27/Documentation/filesystems/nfs/ |
D | 00-INDEX | 4 - explanation of how to make filesystems exportable. 14 - how to install and setup the Linux NFS/RDMA client and server software
|
D | knfsd-stats.txt | 47 Counts how many NFS packets have arrived. More precisely, this 57 of how much CPU load is being placed on the sunrpc server layer 61 Counts how many times an NFS transport is enqueued to wait for 83 Counts how many times an idle nfsd thread is woken to try to 92 Counts how many times the sunrpc server layer chose not to wake an 122 Counts how many times an nfsd thread triggered an idle timeout,
|
D | nfsroot.txt | 15 filesystem mounted via NFS. The following text describes on how to use NFS 84 This parameter tells the kernel how to configure IP addresses of devices 85 and also how to set up the IP routing table. It was originally called 214 For more information on syslinux, including how to create bootdisks 239 For more information on isolinux, including how to create bootdisks 286 For more information on isolinux, including how to create bootdisks
|
D | Exporting | 19 specify how to generate an opaque (outside of the filesystem) byte 20 string for any dentry, and how to find an appropriate dentry for any 148 indicates the decode_fh how much of the filehandle is valid, and how
|
D | pnfs-block-server.txt | 25 how to translate the device into a serial number from SCSI EVPD 0x80:
|
D | nfs-rdma.txt | 21 This document describes how to install and setup the Linux NFS/RDMA client 247 Regardless of how the server was built (module or built-in), start the 268 Regardless of how the client was built (module or built-in), use this
|
/linux-4.1.27/fs/nfs/objlayout/ |
D | objlayout.h | 123 extern int objio_write_pagelist(struct nfs_pgio_header *wdata, int how); 170 int how);
|
/linux-4.1.27/tools/perf/Documentation/ |
D | perf-inject.txt | 40 Merge sched_stat and sched_switch for getting events where and how long 42 sched_stat contains a timeslice how long a task slept.
|
D | perf-diff.txt | 105 Determine how to display the overhead percentage of filtered entries. 181 relative to how entries are filtered. Use --percentage=absolute to
|
/linux-4.1.27/Documentation/powerpc/ |
D | 00-INDEX | 9 - Information on how the powerpc kernel is wrapped for boot on various 12 - info on how we support a variety of CPUs with minimal compile-time
|
D | eeh-pci-error-recovery.txt | 59 In the following discussion, a generic overview of how to detect 61 by an overview of how the current implementation in the Linux 119 infrastructure. Following is a detailed description of how this is 189 focusing on how the device driver gets shut down, and on how the
|
/linux-4.1.27/security/apparmor/ |
D | Kconfig | 15 If you are unsure how to answer this question, answer N. 31 If you are unsure how to answer this question, answer 1.
|
/linux-4.1.27/fs/nfs/ |
D | pnfs.h | 155 int how, 336 int how, 339 int how)); 407 pnfs_commit_list(struct inode *inode, struct list_head *mds_pages, int how, in pnfs_commit_list() argument 412 return NFS_SERVER(inode)->pnfs_curr_ld->commit_pagelist(inode, mds_pages, how, cinfo); in pnfs_commit_list() 623 pnfs_commit_list(struct inode *inode, struct list_head *mds_pages, int how, in pnfs_commit_list() argument
|
D | write.c | 1260 static int flush_task_priority(int how) in flush_task_priority() argument 1262 switch (how & (FLUSH_HIGHPRI|FLUSH_LOWPRI)) { in flush_task_priority() 1274 struct rpc_task_setup *task_setup_data, int how) in nfs_initiate_write() argument 1276 int priority = flush_task_priority(how); in nfs_initiate_write() 1543 int how, int flags) in nfs_initiate_commit() argument 1546 int priority = flush_task_priority(how); in nfs_initiate_commit() 1573 if (how & FLUSH_SYNC) in nfs_initiate_commit() 1651 nfs_commit_list(struct inode *inode, struct list_head *head, int how, in nfs_commit_list() argument 1665 data->mds_ops, how, 0); in nfs_commit_list() 1754 int how, struct nfs_commit_info *cinfo) in nfs_generic_commit_list() argument [all …]
|
D | pnfs_nfs.c | 235 int how, struct nfs_commit_info *cinfo, in pnfs_generic_commit_pagelist() argument 237 int how)) in pnfs_generic_commit_pagelist() 272 data->mds_ops, how, 0); in pnfs_generic_commit_pagelist() 281 initiate_commit(data, how); in pnfs_generic_commit_pagelist()
|
D | pagelist.c | 568 int how, struct nfs_commit_info *cinfo) in nfs_pgio_rpcsetup() argument 585 switch (how & (FLUSH_STABLE | FLUSH_COND_STABLE)) { in nfs_pgio_rpcsetup() 618 const struct rpc_call_ops *call_ops, int how, int flags) in nfs_initiate_pgio() argument 637 hdr->rw_ops->rw_initiate(hdr, &msg, rpc_ops, &task_setup_data, how); in nfs_initiate_pgio() 652 if (how & FLUSH_SYNC) { in nfs_initiate_pgio()
|
D | internal.h | 254 const struct rpc_call_ops *call_ops, int how, int flags); 447 int how, int flags); 464 int how, struct nfs_commit_info *cinfo);
|
/linux-4.1.27/drivers/net/ethernet/intel/ |
D | Kconfig | 51 adapters. For more information on how to identify your adapter, go 75 use the regular e1000 driver For more information on how to 96 adapters. For more information on how to identify your adapter, go 137 information on how to identify your adapter, go to the Adapter & 159 instead. For more information on how to identify your adapter, go 182 adapters. For more information on how to identify your adapter, go 238 Intel(R) ixgbe driver. For more information on how to identify your 261 devices. For more information on how to identify your adapter, go 311 For more information on how to identify your adapter, go to the 332 Interface. For more information on how to identify your adapter,
|
/linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/ |
D | brcm,bcm7120-l2-intc.txt | 11 - controls how some of the interrupts will be flowing, whether they will 63 - brcm,int-map-mask: 32-bits bit mask describing how many and which interrupts 64 are wired to this 2nd level interrupt controller, and how they match their
|
/linux-4.1.27/Documentation/cpu-freq/ |
D | index.txt | 26 governors.txt - What are cpufreq governors and how to 47 how to access the CVS repository:
|
/linux-4.1.27/tools/testing/ktest/examples/ |
D | README | 3 is broken up by task which makes it easier to understand how to set up 26 included into other configs. This is a real use example that shows how
|
/linux-4.1.27/arch/sh/include/asm/ |
D | sh_bios.h | 15 extern void sh_bios_shutdown(unsigned int how);
|
/linux-4.1.27/Documentation/networking/ |
D | generic_netlink.txt | 1 A wiki document on how to use Generic Netlink can be found here:
|
D | framerelay.txt | 11 The configuration script will ask you how many DLCIs you need, as well as 12 how many DLCIs you want to assign to each Frame Relay Access Device (FRAD).
|
D | irda.txt | 5 For more information about how to use the IrDA protocol stack, see the
|
D | i40evf.txt | 25 For more information on how to identify your adapter, go to the Adapter &
|
D | ixgbevf.txt | 30 For more information on how to identify your adapter, go to the Adapter &
|
D | gianfar.txt | 29 before the hash tables. See Linux documentation on how to join
|
D | decnet.txt | 38 start working. If you need something more complicated or are unsure how 181 tcpdump don't understand how to dump DECnet properly, so including 188 A quick FAQ on ethernet MAC addresses to explain how Linux and DECnet 189 interact and how to get the best performance from your hardware.
|
/linux-4.1.27/Documentation/gpio/ |
D | gpio.txt | 4 The documents in this directory give detailed instructions on how to access 5 GPIOs in drivers, and how to write a driver for a device that provides GPIOs 39 firmware knowing how they're used). 44 options about how that value is driven, so that for example only one 117 example, that's how I2C clocks are stretched: a slave that needs a slower clock
|
D | board.txt | 4 This document explains how GPIOs can be assigned to given devices and functions. 13 their Kconfig. Then, how GPIOs are mapped depends on what the platform uses to
|
/linux-4.1.27/Documentation/dmaengine/ |
D | 00-INDEX | 6 - how to compile, configure and use the dmatest system.
|
/linux-4.1.27/drivers/scsi/sym53c8xx_2/ |
D | sym_defs.h | 656 #define SCR_LOAD_R(reg, how, n) \ argument 657 (0xe1000000 | how | (SCR_REG_OFS2(REG(reg))) | (n)) 659 #define SCR_STORE_R(reg, how, n) \ argument 660 (0xe0000000 | how | (SCR_REG_OFS2(REG(reg))) | (n))
|
/linux-4.1.27/drivers/video/logo/ |
D | logo_m32r_clut224.ppm | 4 # Note: how to convert ppm to pnm(ascii).
|
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/ |
D | Suspend.txt | 10 powered down. For more information on how this works, please look 31 sleep and how it resumes. The default behaviour of the Linux code 105 aspects of how the S3C2410 suspend and resume support is configured
|
/linux-4.1.27/Documentation/power/ |
D | swsusp-dmcrypt.txt | 8 You know how dm-crypt works. If not, visit the following web page: 11 You did read Documentation/initrd.txt and know how an initrd works. 12 You know how to create or how to modify an initrd.
|
D | video.txt | 7 devices, this is easy, and kernel driver knows how to do 90 Model hack (or "how to do it") 175 Mainboard Graphics card hack (or "how to do it")
|
/linux-4.1.27/Documentation/development-process/ |
D | 7.AdvancedTopics | 3 At this point, hopefully, you have a handle on how the development process 23 teach the reader how to use git; that would be sufficient material for a 24 long document in its own right. Instead, the focus here will be on how git 35 understanding of how git works before trying to use it to make patches 107 useful in such situations; it remembers how merge conflicts were resolved 149 learn how to program in the kernel environment than by looking at code 159 comments as questions rather than criticisms. Asking "how does the lock
|
D | 8.Conclusion | 53 document. Hopefully it has provided a helpful understanding of how the 54 Linux kernel is developed and how you can participate in that process.
|
/linux-4.1.27/Documentation/devicetree/bindings/net/can/ |
D | m_can.txt | 22 so this property is telling driver how the shared or 31 RAM. The remain cells are used to specify how many
|
/linux-4.1.27/Documentation/filesystems/pohmelfs/ |
D | info.txt | 19 Internal timeout, expressed in milliseconds, which specifies how frequently 20 inodes marked to be dropped are freed. It also specifies how frequently 98 Number of worker threads specifies how many workers will be created for each client.
|
/linux-4.1.27/Documentation/block/ |
D | ioprio.txt | 17 CFQ implements three generic scheduling classes that determine how io is 24 there are 8 levels of class data that determine exactly how much time this 31 determines how much io bandwidth the process will get, it's directly mappable
|
D | deadline-iosched.txt | 4 This little file attempts to document how the deadline io scheduler works. 53 how many times we give preference to reads over writes. When that has been
|
D | 00-INDEX | 10 - how to specify block device partitions on kernel command line
|
D | switching-sched.txt | 6 tunables control how the io scheduler works. You can find these entries
|
/linux-4.1.27/Documentation/fmc/ |
D | fmc-trivial.txt | 6 bus and how interrupts worked.
|
D | 00-INDEX | 26 - how identification and matching works
|
D | fmc-fakedev.txt | 10 It is meant as the simplest possible example of how a driver should be
|
D | identifiers.txt | 15 This chapter explains how to create your own EEPROM image and how to 16 write it in your mezzanine, as well as how devices and drivers are
|
/linux-4.1.27/Documentation/video4linux/cx2341x/ |
D | fw-upload.txt | 1 This document describes how to upload the cx2341x firmware to the card. 7 on how to obtain the firmware.
|
/linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
D | 8xxx_gpio.txt | 8 See bindings/gpio/gpio.txt for details of how to specify GPIO 13 interrupt client nodes section) for details how to specify this GPIO
|
D | gpio-altera.txt | 27 - altr,ngpio: Width of the GPIO bank. This defines how many pins the
|
/linux-4.1.27/Documentation/devicetree/bindings/thermal/ |
D | thermal.txt | 11 not about how the system must control or which algorithm or policy 39 on how consumers refer to sensor devices. 78 on how consumers refer to cooling devices. 104 The cooling device maps node is a node to describe how cooling devices 191 Below are several examples on how to use thermal data descriptors 196 The CPU thermal zone example below describes how to setup one thermal zone 312 The example below describes how to deploy several thermal zones based off a 432 The example below illustrates how to use more than one sensor within 501 The board thermal example below illustrates how to setup one thermal zone
|
/linux-4.1.27/Documentation/devicetree/bindings/drm/i2c/ |
D | tda998x.txt | 17 - video-ports: 24 bits value which defines how the video controller
|
/linux-4.1.27/security/yama/ |
D | Kconfig | 11 If you are unsure how to answer this question, answer N.
|
/linux-4.1.27/Documentation/timers/ |
D | 00-INDEX | 18 - how to insert delays in the kernel the right (tm) way.
|
/linux-4.1.27/drivers/staging/fsl-mc/ |
D | TODO | 2 DPAA2 objects and how combine them to make a NIC, an LS2 switch, etc.
|
/linux-4.1.27/Documentation/usb/ |
D | rio.txt | 15 This README will address issues regarding how to configure the kernel 17 Before I explain how to use this to access the Rio500 please be warned: 23 are in no way responsible for any damage that may occur, no matter how
|
D | chipidea.txt | 3 To show how to demo OTG HNP and SRP functions via sys input files 75 Below is the example for how to enable USB as system wakeup source
|
D | bulk-streams.txt | 41 declares how many stream IDs it can support, and each bulk endpoint on a 42 SuperSpeed device will say how many stream IDs it can handle. Therefore,
|
D | mass-storage.txt | 21 This document describes how to use the gadget from user space, its 23 using it, and how it differs from File Storage Gadget (or FSG) 25 about how to use MSF within composite gadgets. 192 For examples of how to include mass storage function in gadgets, one
|
D | ehci.txt | 108 is 6, indicating 2^6 = 64 microframes. This controls how often 141 USB 2.0 throughput is gated by two main factors: how fast the host 142 controller can process requests, and how fast devices can respond to 210 transfers are fully scheduled, so the main issue is likely to be how
|
D | wusb-cbaf | 35 get-cdid to see how does this device report itself to us.
|
D | gadget_configfs.txt | 31 This document is about how to do it. 33 It also describes how configfs integration into gadget is designed. 294 Below the idea of how configfs works is presented.
|
/linux-4.1.27/arch/avr32/mach-at32ap/ |
D | Kconfig | 11 This is used to determine how to mangle the address and/or data
|
/linux-4.1.27/Documentation/blockdev/ |
D | 00-INDEX | 18 - short guide on how to set up and use the RAM disk.
|
/linux-4.1.27/Documentation/laptops/ |
D | 00-INDEX | 14 - how to conserve battery power using laptop-mode.
|
/linux-4.1.27/include/net/ |
D | dst_ops.h | 24 struct net_device *dev, int how);
|
D | inet_common.h | 29 int inet_shutdown(struct socket *sock, int how);
|
/linux-4.1.27/Documentation/hwmon/ |
D | tmp103 | 27 Please refer how to instantiate this driver:
|
D | smsc47b397 | 44 The following is an example of how to read the HWM temperature registers: 114 The following is an example of how to read the SIO Device ID located at 0x20 139 The following is an example of how to read the HWM Base Address located in
|
D | hih6130 | 25 Please see Documentation/i2c/instantiating-devices for details on how to
|
D | abituguru | 56 * fan_sensors: int Tell the driver how many fan speed sensors there are 58 * pwms: int Tell the driver how many fan speed controls (fan
|
D | sch5636 | 25 temperatures. Note that the driver detects how many fan headers /
|
D | w83781d | 171 how to handle them. More details below. 179 a datasheet or ideas on how to convince Asus. We can't help. 251 Kaam about how to detect these chips, and how to read their values. He 366 We don't know exactly how the temperature sensor type selection works. 395 Please contact us if you can figure out how it is supposed to work. As
|
D | k8temp | 43 There is no easy way how to measure the temperature which will correlate
|
D | lm73 | 41 The following examples show how the 'update_interval' attribute can be
|
/linux-4.1.27/include/net/bluetooth/ |
D | bluetooth.h | 303 static inline struct sk_buff *bt_skb_alloc(unsigned int len, gfp_t how) in bt_skb_alloc() argument 307 skb = alloc_skb(len + BT_SKB_RESERVE, how); in bt_skb_alloc()
|
/linux-4.1.27/arch/frv/mm/ |
D | tlb-flush.S | 61 # find out how many lines there are 102 # find out how many lines there are
|
/linux-4.1.27/arch/arm/firmware/ |
D | Kconfig | 25 on how to use it.
|
/linux-4.1.27/Documentation/s390/ |
D | 00-INDEX | 6 - how to use the IBM 3270 display system support.
|
/linux-4.1.27/Documentation/security/ |
D | 00-INDEX | 6 - how to get started with the SELinux security enhancement.
|
/linux-4.1.27/Documentation/serial/ |
D | n_gsm.txt | 8 This document give some hints on how to use this driver with GPRS and 3G 82 More practical details on the protocol and how it's supported by industrial
|
/linux-4.1.27/Documentation/networking/mac80211_hwsim/ |
D | README | 28 to select how many radios are simulated (default 2). This allows 47 This example shows how to use mac80211_hwsim to simulate two radios:
|
/linux-4.1.27/Documentation/nios2/ |
D | README | 7 system call ABI. Please see this link for more information on how compiling and booting
|
/linux-4.1.27/Documentation/namespaces/ |
D | resource-control.txt | 9 that userspace configure memory control groups to limit how much
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
D | lbc.txt | 8 - #size-cells : Either one or two, depending on how large each chipselect
|
/linux-4.1.27/net/ax25/ |
D | Kconfig | 39 radio as well as information about how to configure an AX.25 port is 87 users as well as information about how to configure an AX.25 port is 106 users as well as information about how to configure an AX.25 port is
|
/linux-4.1.27/Documentation/devicetree/bindings/mips/ |
D | cpu_irq.txt | 6 With the irq_domain in place we can describe how the 8 IRQs are wired to the
|
/linux-4.1.27/Documentation/isdn/ |
D | syncPPP.FAQ | 7 Q04: MPPP?? What's that and how can I use it ... 43 isdn4linux manual on how to configure a network device. 70 Q04: MPPP?? What's that and how can I use it ... 169 A: You must know, how the ipppd gets the addresses it wanna
|
/linux-4.1.27/Documentation/filesystems/ |
D | exofs.txt | 25 See Documentation/scsi/osd.txt for how to setup a working osd environment. 83 do-exofs start - an example of how to perform the above steps. 84 do-exofs stop - an example of how to unmount the file system. 85 do-exofs format - an example of how to format and mkfs a new exofs.
|
/linux-4.1.27/drivers/scsi/ |
D | ncr53c8xx.h | 1172 #define SCR_LOAD_R(reg, how, n) \ argument 1173 (0xe1000000 | how | (SCR_REG_OFS2(REG(reg))) | (n)) 1175 #define SCR_STORE_R(reg, how, n) \ argument 1176 (0xe0000000 | how | (SCR_REG_OFS2(REG(reg))) | (n))
|
/linux-4.1.27/drivers/staging/iio/ |
D | Kconfig | 26 Driver intended mainly as documentation for how to write
|
/linux-4.1.27/net/ceph/ |
D | Kconfig | 40 For information on how to use CONFIG_DNS_RESOLVER consult
|
/linux-4.1.27/include/linux/ |
D | net.h | 205 int sock_wake_async(struct socket *sk, int how, int band); 284 int kernel_sock_shutdown(struct socket *sock, enum sock_shutdown_cmd how);
|
D | auto_dev-ioctl.h | 69 __u32 how; member
|
D | nfs_page.h | 128 int how);
|
/linux-4.1.27/Documentation/x86/x86_64/ |
D | machinecheck | 12 mcelog knows how to decode them. 54 how hard the kernel tries to recover even at some risk of
|
/linux-4.1.27/net/ipv4/ |
D | af_inet.c | 774 int inet_shutdown(struct socket *sock, int how) in inet_shutdown() argument 782 how++; /* maps 0->1 has the advantage of making bit 1 rcvs and in inet_shutdown() 785 if ((how & ~SHUTDOWN_MASK) || !how) /* MAXINT->0 */ in inet_shutdown() 803 sk->sk_shutdown |= how; in inet_shutdown() 805 sk->sk_prot->shutdown(sk, how); in inet_shutdown() 813 if (!(how & RCV_SHUTDOWN)) in inet_shutdown()
|
/linux-4.1.27/security/integrity/evm/ |
D | Kconfig | 12 If you are unsure how to answer this question, answer N.
|
/linux-4.1.27/Documentation/arm/SA1100/ |
D | CERF | 21 evaluation kit on how to use the bootloader. This series of commands
|
D | ADSBitsy | 16 newer rev boards. See their documentation on how to load Linux.
|
D | GraphicsMaster | 16 newer rev boards. See their documentation on how to load Linux.
|
/linux-4.1.27/include/net/nfc/ |
D | nci_core.h | 295 gfp_t how) in nci_skb_alloc() argument 299 skb = alloc_skb(len + ndev->tx_headroom + ndev->tx_tailroom, how); in nci_skb_alloc()
|
/linux-4.1.27/drivers/auxdisplay/ |
D | Kconfig | 50 and execute "dmesg" or "cat /proc/ioports". You can see there how 87 For help about how to wire your LCD to the parallel port,
|
/linux-4.1.27/drivers/net/slip/ |
D | Kconfig | 25 <http://www.tldp.org/docs.html#howto>, explains how to 57 <http://www.tldp.org/docs.html#howto>, explains how to configure
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
D | qe.txt | 20 - fsl,qe-num-riscs: define how many RISC engines the QE has. 21 - fsl,qe-num-snums: define how many serial number(SNUM) the QE can use for the
|
/linux-4.1.27/fs/reiserfs/ |
D | README | 39 If you have doubts about how to properly do that, or about what is 40 fair, ask. (Last I spoke with him Richard was contemplating how best 53 Linux provider put them. There is some disagreement about how useful 127 of how we could use the hashing code in making 32 bit NFS cookies work
|
/linux-4.1.27/Documentation/devicetree/bindings/input/touchscreen/ |
D | tsc2007.txt | 22 - ti,poll-period: how much time to wait (in milliseconds) before reading again the
|
/linux-4.1.27/drivers/staging/media/bcm2048/ |
D | TODO | 8 find many examples of how to do this in drivers/media/radio.
|
/linux-4.1.27/drivers/scsi/aic7xxx/aicasm/ |
D | aicasm_symbol.h | 201 symlist_add(symlist_t *symlist, symbol_t *symbol, int how);
|
/linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
D | mfd.txt | 21 consider all subnodes of the MFD device as separate devices akin to how
|
D | twl4030-power.txt | 23 depending on how the external oscillator is wired.
|
/linux-4.1.27/Documentation/devicetree/bindings/sound/ |
D | ti,tas5086.txt | 27 The correct configuration depends on how the power
|
D | cs42l56.txt | 38 - cirrus,adaptive-pwr-cfg : Configures how the power to the Headphone and Lineout
|
/linux-4.1.27/Documentation/ABI/ |
D | README | 32 layout of the files below for details on how to do this.) 50 Description: Long description of the interface and how to use it.
|
/linux-4.1.27/fs/nfs/filelayout/ |
D | filelayout.c | 998 static int filelayout_initiate_commit(struct nfs_commit_data *data, int how) in filelayout_initiate_commit() argument 1016 data->inode->i_ino, how, atomic_read(&ds->ds_clp->cl_count)); in filelayout_initiate_commit() 1024 &filelayout_commit_call_ops, how, in filelayout_initiate_commit() 1064 int how, struct nfs_commit_info *cinfo) in filelayout_commit_pagelist() argument 1066 return pnfs_generic_commit_pagelist(inode, mds_pages, how, cinfo, in filelayout_commit_pagelist()
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | timestamping.txt | 25 - 'avail' reports how much can be written in the ring buffer 92 information on how much the application pointer can be rewound 97 ratio, the precision helps define how much smoothing/low-pass 180 shows how compensating for the delay exposes a 1ms accuracy (due to
|
/linux-4.1.27/Documentation/trace/ |
D | tracepoint-analysis.txt | 58 See Documentation/trace/events.txt for a proper description on how events 113 Documentation/trace/ftrace.txt describes how to enable events on a per-thread 137 Documentation/trace/ftrace.txt covers in-depth how to filter events in 168 Using --repeat, it is also possible to view how events are fluctuating over
|
/linux-4.1.27/fs/ |
D | Kconfig.binfmt | 163 <file:Documentation/binfmt_misc.txt> to learn how to use this 164 feature, <file:Documentation/java.txt> for information about how 166 information about how to include Mono-based .NET support.
|
/linux-4.1.27/drivers/media/radio/si470x/ |
D | Kconfig | 16 Please have a look at the documentation, especially on how
|
/linux-4.1.27/net/dccp/ |
D | Kconfig | 51 Documentation on how to use DCCP connection probing can be found
|
/linux-4.1.27/drivers/input/joystick/ |
D | Kconfig | 215 For more information on how to use the driver please read 230 For more information on how to use the driver please read 242 Amstrad CPC joystick. For more information on how to use the driver 288 For information about how to connect the X-Box pad to USB, see
|
/linux-4.1.27/drivers/spi/ |
D | spi-s3c24xx-fiq.S | 35 @ each entry starts with a word entry of how long it is
|
/linux-4.1.27/Documentation/dvb/ |
D | readme.txt | 53 how to get DVB and udev up and running.
|
/linux-4.1.27/Documentation/cgroups/ |
D | hugetlb.txt | 8 beyond its limit. This requires the application to know beforehand how much
|
/linux-4.1.27/Documentation/devicetree/bindings/net/ |
D | qca-qca7000-spi.txt | 23 This setting depends on how the QCA7000 is setup via GPIO pin strapping.
|
D | fsl-tsec-phy.txt | 6 of how to define a PHY. 100 Here is how to figure good values:
|
/linux-4.1.27/Documentation/zh_CN/ |
D | SubmittingDrivers | 161 http://www.fenrus.org/how-to-not-write-a-device-driver-paper.pdf
|
/linux-4.1.27/net/atm/ |
D | pvc.c | 21 static int pvc_shutdown(struct socket *sock, int how) in pvc_shutdown() argument
|
/linux-4.1.27/net/iucv/ |
D | af_iucv.c | 1495 static int iucv_sock_shutdown(struct socket *sock, int how) in iucv_sock_shutdown() argument 1502 how++; in iucv_sock_shutdown() 1504 if ((how & ~SHUTDOWN_MASK) || !how) in iucv_sock_shutdown() 1519 if (how == SEND_SHUTDOWN || how == SHUTDOWN_MASK) { in iucv_sock_shutdown() 1542 sk->sk_shutdown |= how; in iucv_sock_shutdown() 1543 if (how == RCV_SHUTDOWN || how == SHUTDOWN_MASK) { in iucv_sock_shutdown()
|
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
D | allwinner,sunxi-pinctrl.txt | 27 pins it needs, and how they should be configured, with regard to muxer
|
/linux-4.1.27/Documentation/i2c/ |
D | old-module-parameters | 6 control how the driver would probe i2c buses and attach to devices. These
|
/linux-4.1.27/Documentation/devicetree/bindings/pwm/ |
D | pwm-fsl-ftm.txt | 14 Please see ../regmap/regmap.txt for more detail about how to specify endian
|
/linux-4.1.27/Documentation/device-mapper/ |
D | kcopyd.txt | 8 Users of kcopyd must first create a client and indicate how many memory pages
|
/linux-4.1.27/net/caif/ |
D | Kconfig | 21 See Documentation/networking/caif for a further explanation on how to
|
/linux-4.1.27/Documentation/fb/ |
D | cmap_xfbdev.txt | 4 These notes explain how X's dix layer uses fbdev's cmap structures.
|
/linux-4.1.27/drivers/fmc/ |
D | Kconfig | 31 This is a fake mezzanine driver, to show how FMC works and test it.
|
/linux-4.1.27/drivers/nfc/ |
D | nfcwilink.c | 113 static inline struct sk_buff *nfcwilink_skb_alloc(unsigned int len, gfp_t how) in nfcwilink_skb_alloc() argument 117 skb = alloc_skb(len + NFCWILINK_HDR_LEN, how); in nfcwilink_skb_alloc()
|
/linux-4.1.27/net/ |
D | Kconfig | 91 If you are unsure how to answer this question, answer N. 104 If you are unsure how to answer this question, answer N. 307 Documentation on how to use the packet generator can be found 322 Documentation on how to use TCP connection probing can be found
|
/linux-4.1.27/Documentation/video4linux/cx88/ |
D | hauppauge-wintv-cx88-ir.txt | 50 and even a reference to how to decode a bi-phase data stream.
|
/linux-4.1.27/Documentation/devicetree/bindings/clock/ |
D | samsung,s5pv210-clock.txt | 36 documentation[1] for more information how to specify these clocks.
|
/linux-4.1.27/Documentation/video4linux/ |
D | hauppauge-wintv-cx88-ir.txt | 50 and even a reference to how to decode a bi-phase data stream.
|
/linux-4.1.27/Documentation/devicetree/bindings/memory-controllers/fsl/ |
D | ifc.txt | 12 - #size-cells : Either one or two, depending on how large each chipselect
|
/linux-4.1.27/drivers/staging/iio/Documentation/ |
D | ring.txt | 4 a buffer may supply and how it is specified within IIO. For more
|
/linux-4.1.27/Documentation/w1/masters/ |
D | omap-hdq | 24 difference between the HDQ and 1-wire mode is how the slave device responds to
|
/linux-4.1.27/Documentation/sysctl/ |
D | kernel.txt | 101 how often do we check the amount of free space (value is in 228 defends against that. It defines how many concurrent crashing 414 it's up to userspace, how to handle an object with "wrong" id. 500 numa_balancing_scan_size_mb is how many megabytes worth of pages are 591 Hints to the kernel how much CPU time it should be allowed to 603 sampling rate no matter how CPU time it takes. 611 how much CPU is consumed. 773 Linux lets you set resource limits, including how much memory one 794 Control how file position affects the behavior of updating sysctl values
|
/linux-4.1.27/sound/oss/ |
D | Kconfig | 44 <file:Documentation/sound/oss/MultiSound> for information on how to 55 <file:Documentation/sound/oss/MultiSound> for information on how to 106 <file:Documentation/sound/oss/MultiSound> for information on how to 117 <file:Documentation/sound/oss/MultiSound> for information on how to 151 <file:Documentation/sound/oss/MultiSound> for information on how to make 377 how to compile it into the kernel or as a module see the file
|
/linux-4.1.27/Documentation/scheduler/ |
D | sched-deadline.txt | 117 * scheduling theory, and how it applies to SCHED_DEADLINE. 119 * how the scheduling policy can be used. Anyway, we strongly recommend 234 figure out how we want to manage SCHED_DEADLINE bandwidth at the task group 344 and how to prevent non-root users "cheat" the system? 363 workloads (maybe mimicking real use-cases) and evaluate how the scheduler 406 showing how SCHED_DEADLINE reservations can be created by a real-time
|
/linux-4.1.27/Documentation/arm/Samsung/ |
D | Overview.txt | 9 the current kernel support, how to use it and where to find the code
|
/linux-4.1.27/tools/testing/fault-injection/ |
D | failcmd.sh | 30 specifies how many times failures may happen at most.
|
/linux-4.1.27/drivers/iio/ |
D | Kconfig | 33 no buffer events so it is up to userspace to work out how
|