by (reference) in projects: linux-4.4.14

Searched refs:by (Results 1 – 200 of 4062) sorted by relevance

/linux-4.4.14/Documentation/ja_JP/
D	SubmittingPatches	3 This document is maintained by Keiichi KII <k-keiichi@bx.jp.nec.com> 336 Signed-off-by: Random J Developer <random@developer.example.org> 352 Signed-off-by とあなたがその末尾に追加する Signed-off-by の間に、修正を 358 Signed-off-by: Random J Developer <random@developer.example.org> 360 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org> 388 13) いつ Acked-by: と Cc: を使うのか 390 「 Signed-off-by: 」タグはその署名者がパッチの開発に関わっていたことやパッチ 394 る承認を記録し、示したいとします。その場合、その人を示すのに Acked-by: が使 395 えます。Acked-by: はパッチのチェンジログにも追加されます。 398 の伝播パスにいなかった時にも、メンテナは Acked-by: をしばしば利用します。 [all …]
/linux-4.4.14/arch/arm/boot/dts/
D	axm5516-cpus.dtsi	7 * it under the terms of the GNU General Public License as published by 81 cpu-release-addr = <0>; // Fixed by the boot loader 89 cpu-release-addr = <0>; // Fixed by the boot loader 97 cpu-release-addr = <0>; // Fixed by the boot loader 105 cpu-release-addr = <0>; // Fixed by the boot loader 113 cpu-release-addr = <0>; // Fixed by the boot loader 121 cpu-release-addr = <0>; // Fixed by the boot loader 129 cpu-release-addr = <0>; // Fixed by the boot loader 137 cpu-release-addr = <0>; // Fixed by the boot loader 145 cpu-release-addr = <0>; // Fixed by the boot loader [all …]
D	alpine.dtsi	`6 * version 2, as published by the Free Software Foundation. 44 clock-frequency = <0>; /* Filled by loader / 51 clock-frequency = <0>; / Filled by loader / 58 clock-frequency = <0>; / Filled by loader / 65 clock-frequency = <0>; / Filled by loader / 84 clock-frequency = <0>; / Filled by loader / 126 clock-frequency = <0>; / Filled by loader / 135 clock-frequency = <0>; / Filled by loader */`
D	xenvm-4.2.dts	`19 /* this field is going to be adjusted by the hypervisor / 49 / this field is going to be adjusted by the hypervisor / 72 / this field is going to be adjusted by the hypervisor / 74 / this field is going to be adjusted by the hypervisor */`
D	hisi-x5hd2-dkb.dts	`7 * publishhed by the Free Software Foundation. 60 /* Placeholder, overwritten by bootloader / 74 / Placeholder, overwritten by bootloader */`
/linux-4.4.14/arch/mn10300/mm/
D	Makefile	`11 cacheflush-$(CONFIG_MN10300_CACHE_INV_BY_TAG) += cache-inv-by-tag.o 12 cacheflush-$(CONFIG_MN10300_CACHE_INV_BY_REG) += cache-inv-by-reg.o 13 cacheflush-$(CONFIG_MN10300_CACHE_FLUSH_BY_TAG) += cache-flush-by-tag.o 14 cacheflush-$(CONFIG_MN10300_CACHE_FLUSH_BY_REG) += cache-flush-by-reg.o 17 cache-dbg-flush-by-tag.o cache-dbg-inv-by-tag.o 19 cache-dbg-flush-by-reg.o 21 cache-dbg-inv-by-tag.o cache-dbg-inv.o 23 cache-dbg-inv-by-reg.o cache-dbg-inv.o`
/linux-4.4.14/Documentation/devicetree/bindings/power/
D	power_domain.txt	4 used for power gating of selected IP blocks for power saving by reduced leakage 8 their PM domains provided by PM domain providers. A PM domain provider can be 9 represented by any node in the device tree and can provide one or more PM 10 domains. A consumer node can refer to the provider by a phandle and a set of 11 phandle arguments (so called PM domain specifiers) of length specified by the 20 as specified by device tree binding documentation of particular provider. 23 - power-domains : A phandle and PM domain specifier as defined by bindings of 24 the power controller specified by phandle. 28 created by the given provider should be subdomains of the domain 29 specified by this binding. More details about power domain specifier are [all …]
/linux-4.4.14/arch/arm/nwfpe/
D	softfloat-macros	8 Written by John R. Hauser. This work was made possible in part by the 10 Street, Berkeley, California 94704. Funding was partially provided by the 14 overseen by Profs. Nelson Morgan and John Wawrzynek. More information 34 Shifts `a' right by the number of bits given in `count'. If any nonzero 36 the result by setting the least significant bit to 1. The value of `count' 39 The result is stored in the location pointed to by `zPtr'. 59 Shifts `a' right by the number of bits given in `count'. If any nonzero 61 the result by setting the least significant bit to 1. The value of `count' 64 The result is stored in the location pointed to by `zPtr'. 87 Shifts the 128-bit value formed by concatenating `a0' and `a1' right by 64 [all …]
/linux-4.4.14/arch/x86/crypto/
D	aes_ctrby8_avx-x86_64.S	`159 .set by, \b define 170 .rept (by - 1) 186 club DDQ_DATA, by 194 .rept (by - 1) 203 .rept by 218 .rept by 224 add $(16*by), p_in 235 .rept by 249 .rept by 269 .rept by [all …]`
/linux-4.4.14/arch/m68k/fpsp040/
D	binstr.S	16 \| bit 63. The fraction is multiplied by 10 using a mul by 2 17 \| shift and a mul by 8 shift. The bits shifted out of the 28 \| A3. Multiply the fraction in d2:d3 by 8 using bit-field 32 \| A4. Multiply the fraction in d4:d5 by 2 using shifts. The msb 33 \| will be collected by the carry. 51 \| d2: upper 32-bits of fraction for mul by 8 52 \| d3: lower 32-bits of fraction for mul by 8 53 \| d4: upper 32-bits of fraction for mul by 2 54 \| d5: lower 32-bits of fraction for mul by 2 87 \| A3. Multiply d2:d3 by 8; extract msbs into d1. [all …]
D	decbin.S	4 \| Description: Converts normalized packed bcd value pointed to by 24 \| A1. Convert the bcd exponent to binary by successive adds and muls. 30 \| A2. Convert the bcd mantissa to binary by successive 56 \| A5. Form the final binary number by scaling the mantissa by 57 \| the exponent factor. This is done by multiplying the 58 \| mantissa in FP0 by the factor in FP1 if the adjusted 59 \| exponent sign is positive, and dividing FP0 by FP1 if 125 \| 2. Calculate absolute value of exponent in d1 by mul and add. 153 mulul #TEN,%d1 \|mul partial product by one digit place 464 fmulx (%a1,%d3),%fp1 \|mul by 10**(d3_bit_no) [all …]
D	satanh.S	`10 \| by address register a0. 26 \| 2. (\|X\| < 1) Calculate atanh(X) by 36 \| divide-by-zero by 41 \| 5. (\|X\| > 1) Generate an invalid operation by 0 * infinity.`
/linux-4.4.14/Documentation/virtual/kvm/
D	s390-diag.txt	8 Note that bits are numbered as by the usual s390 convention (most significant 15 DIAGNOSE calls by the guest cause a mandatory intercept. This implies 16 all supported DIAGNOSE calls need to be handled by either KVM or its 19 All DIAGNOSE calls supported by KVM use the RS-a format: 26 The second-operand address (obtained by the base/displacement calculation) 30 The supported DIAGNOSE function codes vary by the userspace used. For 50 Handled by userspace. 53 Handled by userspace. 56 Handled by userspace. 59 Handled by either userspace or KVM (ioeventfd case). [all …]
D	nested-vmx.txt	13 hypervisors (which use VMX) with their own nested guests. It does so by 48 The nested VMX feature is disabled by default. It can be enabled by giving 53 explicitly enabled, by giving qemu one of the following options: 69 which are used in practice by popular hypervisors (KVM and others). 72 As mandated by the spec, other than the two fields revision_id and abort, 96 u32 launch_state; /* set to 0 by VMCLEAR, to 1 by VMLAUNCH */ 233 These patches were written by: 240 With contributions by: 246 And valuable reviews by:
/linux-4.4.14/drivers/char/mwave/
D	README	5 are not saved by the BIOS and so do not persist after unload and reload. 18 If the dsp irq has not been setup and stored in bios by the 20 irq used by the dsp to be configured. 23 If the dsp io range has not been setup and stored in bios by the 25 io range used by the dsp to be configured. 28 If the mwave's uart irq has not been setup and stored in bios by the 30 irq used by the mwave uart to be configured. 33 If the uart io range has not been setup and stored in bios by the 35 io range used by the mwave uart to be configured.
/linux-4.4.14/Documentation/sound/alsa/soc/
D	jack.txt	10 to be present on a single jack but handled by separate bits of 17 This is done by splitting the jacks up into three things working 18 together: the jack itself represented by a struct snd_soc_jack, sets of 32 user space. The jack itself is completely passive, it is set up by the 33 machine driver and updated by jack detection methods. 35 Jacks are created by the machine driver calling snd_soc_jack_new(). 41 bits supported by the jack. Each snd_soc_jack has zero or more of these 42 which are updated automatically. They are created by the machine driver 51 Actual jack detection is done by code which is able to monitor some 52 input to the system and update a jack by calling snd_soc_jack_report(), [all …]
/linux-4.4.14/Documentation/
D	media-framework.txt	31 other entities. Data (not restricted to video) produced by an entity 43 A media device is represented by a struct media_device instance, defined in 44 include/media/media-device.h. Allocation of the structure is handled by the 45 media device driver, usually by embedding the media_device instance in a 48 Drivers register media device instances by calling 69 "PCI:" (or "PCIe:") followed by the value of pci_name(). For USB devices, 70 the usb_make_path() function must be used. This field is used by 87 Drivers unregister media device instances by calling 99 Entities are represented by a struct media_entity instance, defined in 104 Drivers initialize entities by calling [all …]
D	printk-formats.txt	76 Passed by reference. 84 the width of the CPU data path. Passed by reference. 91 regardless of the width of the CPU data path. Passed by reference. 156 Passed by reference. 172 Passed by reference. 185 print a compressed IPv6 address as described by 188 Passed by reference. 204 flowinfo a '/' and scope a '%', each followed by the actual value. 206 In case of an IPv6 address the compressed IPv6 address as described by 208 specifier 'c' is given. The IPv6 address is surrounded by '[', ']' in [all …]
D	memory-hotplug.txt	20 4.2 Notify memory hot-add event by hand 50 (A) is required by highly virtualized environments and (B) is required by 72 "probe" operation by system administration is used instead. 77 changed by this phase. The kernel makes all memory in it as free pages 82 Logical Memory Hotplug phase is triggered by write of sysfs file by system 84 phase by hand. 141 For the memory block covered by the sysfs directory. It is expected that all 178 can be onlined to ZONE_NORMAL by default and to ZONE_MOVABLE 179 by online_movable. 181 can be onlined to ZONE_MOVABLE by default and to ZONE_NORMAL [all …]
D	rtc.txt	14 the Gregorian calendar and 24 hour time, as reported by gmtime(3). 19 * /dev/rtc ... is the RTC provided by PC compatible systems, 23 supported by a wide variety of RTC chips on all systems. 49 are reported by interrupt number 8. (Oh! So that is what IRQ 8 is 66 A user process can monitor these interrupts by doing a read(2) or a 70 burn up 100% CPU by polling gettimeofday etc. etc. 82 only allowed by root. This is perhaps a bit conservative, but we don't want 84 a negative impact on performance. This 64Hz limit can be changed by writing 105 (The original /dev/rtc driver was written by Paul Gortmaker.) 124 rtc0 is used by default. More information is (currently) shown [all …]
D	svga.txt	8 allows the use of various special video modes supported by the video BIOS. Due 17 The video mode to be used is selected by a kernel parameter which can be 18 specified in the kernel Makefile (the SVGA_MODE=... line) or by the "vga=..." 19 option of LILO (or some other boot loader you use) or by the "vidmode" utility 62 of chipsets is turned off by default (see CONFIG_VIDEO_SVGA in chapter 4 to see 82 the standard modes (80x25 and 80x50) followed by "special" modes (80x28 and 91 all consistent video modes supported by your BIOS will appear (plus maybe some 96 modes are not listed at all and the modes revealed by `scan' are shown before 104 by entering its mode directly if you know it even if it isn't shown on the menu. 113 (as presented to INT 10, function 00) increased by 0x0100. [all …]
D	robust-futex-ABI.txt	1 Started by Paul Jackson <pj@sgi.com> 18 by the exiting thread. 22 call, and handles contested locking by maintaining a list of waiting 74 entry', at an offset from the 'lock entry' specified by the 'offset' 78 lock variable used by the futex mechanism, in conjunction with 83 For each futex lock currently held by a thread, if it wants this 93 pointer for that task. The task may retrieve that value later on by 104 robust_futexes used by that thread. The thread should link those locks 115 entirely by user level code in the contending threads, and by the 119 still held by the departing thread, as described below. [all …]
D	VGA-softcursor.txt	`1 Software cursor for VGA by Pavel Machek <pavel@atrey.karlin.mff.cuni.cz> 13 The cursor appearance is controlled by a "<ESC>[?1;2;3c" escape sequence 24 (by simply XORing them with the value of this parameter). On standard VGA, 26 groups, low three bits set color (as in normal color codes used by the console) 31 Bit setting takes place before bit toggling, so you can simply clear a bit by`
D	lzo.txt	2 LZO stream format as understood by Linux's LZO decompressor 21 opcode and on the number of literals copied by previous instruction. The 39 length, up to 255 may be added in increments by consuming more bytes with a 97 Depends on the number of literals copied by the last instruction. 116 Always followed by exactly one byte : H H H H H H H H 119 If last instruction used to copy 4 or more literals (as detected by 126 Always followed by exactly one byte : H H H H H H H H 132 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S 140 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S 148 Always followed by exactly one byte : H H H H H H H H [all …]
D	SubmittingPatches	53 If you must generate your patches by hand, use "diff -up" or "diff -uprN" 54 to create patches. Git generates patches in this form by default; if 58 generated by diff(1). When creating your patch, make sure to create it 59 in "unified diff" format, as supplied by the '-u' argument to diff(1). 87 "dontdiff" is a list of files which are generated by the kernel during 97 #3. This will facilitate review by other kernel developers, 160 If the patch fixes a logged bug entry, refer to that bug entry by 216 change that can be verified by reviewers. Each patch should be justifiable 298 toward the stable maintainers by putting a line like this: 328 Non-portable code replaced by portable code (even in arch-specific, [all …]
D	nommu-mmap.txt	9 mapping is actually performed by the binfmt drivers, which call back into the 21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write 24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of 36 In the MMU case: VM regions backed by pages read from file; changes to 43 even if this was created by another process. 64 the mapping's backing pages. The page is then backed by swap instead. 71 In the MMU case: VM regions backed by pages read from file; changes to 83 sequence by providing a contiguous sequence of pages to map. In that 102 the mmap() by providing direct access to the underlying device if it 122 (*) The memory allocated by a request for an anonymous mapping will normally [all …]
D	debugging-via-ohci1394.txt	2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging 11 a "Physical Response Unit" which executes specific requests by employing 12 PCI-Bus master DMA after applying filters defined by the OHCI-1394 driver. 19 With that, it is possible to debug issues by reading interesting memory 31 physical addresses above 4 GB, but this feature is currently not enabled by 44 DMA by default, which is more secure but not suitable for remote debugging. 59 firescope - Originally developed by Benjamin Herrenschmidt, Andi Kleen ported 71 data which can be referenced from symbols found by gdb in vmlinux: 89 Step-by-step instructions for using firescope with early OHCI initialization: 108 required for physical DMA above 4 GB (but not utilized by Linux yet). [all …]
D	rfkill.txt	24 - hard block: read-only radio block that cannot be overridden by software 25 - soft block: writable radio block (need not be readable) that is set by 37 replaced by userspace policy code) and 49 When the device is hard-blocked (either by a call to rfkill_set_hw_state() 78 case all rfkill API can still be used but will be provided by static inlines 106 devices. Changes can be either obtained by either polling the descriptor for 107 hotplug or state change events or by listening for uevents emitted by the
D	module-signing.txt	24 allows increased kernel security by disallowing the loading of unsigned modules 25 or modules signed with an invalid key. Module signing increases security by 27 signature checking is done by the kernel so that it is not necessary to have 35 SHA-512 (the algorithm is selected by data in the signature). 42 The module signing facility is enabled by going to the "Enable Loadable Module 60 signature that can be verified by a public key in the kernel's possession 99 the OpenSSL ENGINE_pkcs11 is functional — a PKCS#11 URI as defined by 104 PKCS#11 token requries a PIN, this can be provided at build time by 111 additional certificates which will be included in the system keyring by 176 The kernel contains a ring of public keys that can be viewed by root. They're [all …]
/linux-4.4.14/Documentation/virtual/kvm/devices/
D	vm.txt	26 as unused are again used any may not be reclaimed by the host. 39 2048 MB, 4096 GB, 8192 TB respectively, as this limit is governed by 51 __u32 ibc; # IBC level range offered by host 53 __u64 fac_mask[256]; # set of cpu facilities enabled by KVM 54 __u64 fac_list[256]; # set of cpu facilities offered by host 68 __u64 cpuid; # CPUID currently (to be) used by this vcpu 69 __u16 ibc; # IBC level currently (to be) used by this vcpu 72 # by this vcpu 76 retrieved by means of KVM_S390_VM_CPU_MACHINE as hint for reasonable configuration 77 setups. Instruction interceptions triggered by additionally set facility bits that [all …]
D	vfio.txt	`8 tracks VFIO groups in use by the VM and features of those groups 10 are enabled and disabled for use by the VM, KVM should be updated 12 VFIO-group is held by KVM.`
/linux-4.4.14/Documentation/pcmcia/
D	locking.txt	`53 protected by pcmcia_socket_list_rwsem; 58 The resource_ops and their data are protected by ops_mutex. 63 - by pcmcia_socket_list_rwsem: 66 - by thread_lock: 69 - by skt_mutex: 75 - by ops_mutex: 103 - by pcmcia_socket->ops_mutex: 114 - by the PCMCIA driver:`
/linux-4.4.14/Documentation/fmc/
D	API.txt	1 Functions Exported by fmc.ko 26 allocated by the caller, but must not be released after unregistering. 31 by carriers that host more than one mezzanine. The devices must all be 35 are already driven by a reprogrammed FPGA. 37 If a carrier hosts slots that are driven by different FPGA devices, it 38 should register as a group only mezzanines that are driven by the same 42 *note The API Offered by Carriers:: and also scans the memory area for 45 entry point. The function is meant to factorize common code, and by 46 the time you read this it is already used by the spec-sw and fine-delay
D	mezzanine.txt	6 being used: it will perform I/O accesses only by means of 10 EEPROM (as mandated by the FMC standard) or by the actual cores 15 FPGA registers, by means of the `fpga_base' field of the device 18 by means of Etherbone), the `fpga_base' pointer will be NULL. 32 expected to be performed by the driver. If you depend on specific 41 which it is able to drive. This is usually done by means of a device 56 identified by an array of cores (it matches if all of the cores are 58 pointer-and-length. Several similar devices can be driven by the same 79 package includes support to implement common parameters by means of 96 matches). This is accomplished by the validate carrier method. [all …]
D	carrier.txt	5 registered by the carrier driver. For example, the PCI driver for the 43 __iomem void slot_base; / Set by the driver / 44 struct fmc_device devarray; / Allocated by the bus / 52 uint32_t device_id; / Filled by the device / 59 The following fields must be filled by the carrier driver before 95 later by either the bus or the device driver: 99 fru_id: filled by the bus, parsing the eeprom. 101 * slot_base: filled and used by the driver, if useful to it. 103 * devarray: an array og all mezzanines driven by a singe FPGA. 105 * nr_slots: set by the core at registration time. [all …]
D	fmc-fakedev.txt	`5 is able to register up to 4 mezzanines (by default it registers one). 12 described in *note FMC Identification::),, which by default is 15 You can also use this device to verify the match algorithms, by asking 16 it to test your own EEPROM image. You can provide the image by means of 18 by means of the firmware loader. This example shows the defaults and a`
/linux-4.4.14/Documentation/isdn/
D	README.concap	4 The "concap" interface is intended to be used by network device 6 It is assumed that the protocol interacts with a linux network device by 28 encapsulation protocols. The encapsulation protocol is configured by a 35 encapsulation is usually done by just sticking a header on the data. Thus, 37 encapsulation protocol directly (usually by just providing a hard_header() 62 isdn_net.c harder to maintain. Thus, by identifying an abstract 68 Likewise, a similar encapsulation protocol will frequently be needed by 70 synchronous ppp implementation used by the isdn driver and the 71 asynchronous ppp implementation used by the ppp driver have a lot of 98 - process (xmit) data handed down by upper protocol layer [all …]
D	INTERFACE.fax	`17 conversion by itself. 19 (specified by +FBOR) 23 This structure stores the values (set by AT-commands), the remote- 27 is in this struct set by the LL. 45 Local faxmachine's parameters, set by +FDIS, +FDCS, +FLID, ... 56 Remote faxmachine's parameters. To be set by HL-driver. 59 Defines the actual state of fax connection. Set by HL or LL 117 ISDN_TTY_FAX_HNG output of the +FHNG and value set by code and 132 Set by HL in receive-mode for +FET message. 135 ID-string, set by +FCIG`
D	INTERFACE.CAPI	26 CAPI drivers optionally register themselves with Kernel CAPI by calling the 30 registration can be revoked by calling the function unregister_capi_driver() 34 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a 37 pointers which are subsequently used by Kernel CAPI for communicating with the 38 driver. The registration can be revoked by calling the function 43 structure of the device, and signal its readiness by calling capi_ctr_ready(). 49 callback functions by Kernel CAPI. 55 operation CAPI_REGISTER) to an appropriate hardware driver by calling its 57 allocated by Kernel CAPI and passed to register_appl() along with the 58 parameter structure provided by the application. This is analogous to the [all …]
D	README.pcbit	`5 The PCBIT is a Euro ISDN adapter manufactured in Portugal by Octal and 8 originally developed by Fritz Elfert in the isdn4linux project. 11 distributed (and copyrighted) by the manufacturer. To load this 29 manufacturer believe to be caused by bugs in the firmware. The current`
D	README.diversion	5 document. The diversion services may be used with all cards supported by 8 by Werner Cornelius (werner@isdn4linux.de or werner@titro.de) under the 12 it under the terms of the GNU General Public License as published by 45 only supported by isdn phones. Incoming calls may be diverted 49 as normally done by isdn phones. In this case all incoming calls 55 but dynamically activated by i4l. 56 In this case all incoming calls are checked by rules that may be 64 Actions that may be invoked by a rule are ignore, proceed, reject, 106 dynamically created by the diversion module and removed when the module is 116 your network incoming calls and reactions by the module may be shown on
/linux-4.4.14/Documentation/filesystems/nfs/
D	nfsd-admin-interfaces.txt	`4 Note that normally these interfaces are used only by the utilities in 7 nfsd is controlled mainly by pseudofiles under the "nfsd" filesystem, 10 The server is always started by the first write of a nonzero value to 13 Before doing that, NFSD can be told which sockets to listen on by 26 nfsd is shut down by a write of 0 to nfsd/threads. All locks and state 30 or down by additional writes to nfsd/threads or by writes to`
D	nfsroot.txt	4 Written 1996 by Gero Kuhlmann <gero@gkminix.han.de> 5 Updated 1997 by Martin Mares <mj@atrey.karlin.mff.cuni.cz> 6 Updated 2006 by Nico Schottelius <nico-kernel-nfsroot@schottelius.org> 7 Updated 2006 by Horms <horms@verge.net.au> 39 When the kernel has been loaded by a boot loader (see below) it needs to be 58 The default address is determined by the `ip' parameter 64 replaced by the ASCII-representation of the client's 67 <nfs-options> Standard NFS options. All options are separated by commas. 69 port = as given by server portmap daemon 126 <hostname> Name of the client. May be supplied by autoconfiguration, [all …]
D	idmapper.txt	`5 Id mapper is used by NFS to translate user and group ids into names, and to 9 or by placing a call to the rpc.idmap daemon. 65 nfs.idmap is designed to be called by request-key, and should not be run "by 70 The actual lookups are performed by functions found in nfsidmap.h. nfs.idmap 71 determines the correct function to call by looking at the first part of the`
/linux-4.4.14/Documentation/power/regulator/
D	consumer.txt	11 A consumer driver can get access to its supply regulator by calling :- 16 then finds the correct regulator by consulting a machine specific lookup table. 24 Consumers can be supplied by more than one regulator e.g. codec consumer with 37 A consumer can enable its power supply by calling:- 43 previously enabled by bootloader or kernel board initialization code. 45 A consumer can determine if a regulator is enabled by calling :- 52 A consumer can disable its supply when no longer needed by calling :- 75 Consumers can control their supply voltage by calling :- 87 The regulators configured voltage output can be found by calling :- 105 Consumers can control their supply current limit by calling :- [all …]
D	regulator.txt	`11 Drivers can register a regulator by calling :- 19 Regulators can be unregistered by calling :- 27 consumer drivers by calling :-`
D	overview.txt	35 o Consumer - Electronic device that is supplied power by a regulator. 40 power supply. Its supply voltage is set by the hardware, 47 o Power Domain - Electronic circuit that is supplied its input power by the 48 output power of a regulator, switch or by another power 70 by other regulators. i.e. 89 Regulator Level: This is defined by the regulator hardware 97 Power Domain Level: This is defined in software by kernel 105 Consumer Level: This is defined by consumer drivers 159 overvoltage or overcurrent caused by buggy client drivers. It also 161 supplied by others (similar to a clock tree).
/linux-4.4.14/Documentation/blockdev/drbd/
D	data-structure-v9.txt	`9 device is represented by a block device locally. 26 In this table, horizontally, devices can be accessed from resources by their 27 volume number. Likewise, peer_devices can be accessed from connections by 28 their volume number. Objects in the vertical direction are connected by double 33 devices can be accessed by their minor device number via the drbd_devices idr. 37 devices and connections; their lifetime is determined by the lifetime of the`
/linux-4.4.14/arch/powerpc/boot/dts/
D	ep405.dts	35 clock-frequency = <200000000>; /* Filled in by zImage / 36 timebase-frequency = <0>; / Filled in by zImage / 48 reg = <0x00000000 0x00000000>; / Filled in by zImage / 66 clock-frequency = <0>; / Filled in by zImage / 93 clock-frequency = <0>; / Filled in by zImage / 100 clock-frequency = <0>; / Filled in by zImage / 111 clock-frequency = <0>; / Filled in by zImage / 137 local-mac-address = [000000000000]; / Filled in by zImage / 159 / The ranges property is supplied by the bootwrapper 163 clock-frequency = <0>; /* Filled in by zImage */ [all …]
D	eiger.dts	37 clock-frequency = <0>; /* Filled in by U-Boot / 38 timebase-frequency = <0>; / Filled in by U-Boot / 50 reg = <0x00000000 0x00000000 0x00000000>; / Filled in by U-Boot / 114 clock-frequency = <0>; / Filled in by U-Boot / 149 clock-frequency = <0>; / Filled in by U-Boot / 156 clock-frequency = <0>; / Filled in by U-Boot / 157 / ranges property is supplied by U-Boot / 164 / reg property is supplied in by U-Boot / 199 / reg property is supplied by U-boot / 241 clock-frequency = <0>; / Filled in by U-Boot */ [all …]
D	walnut.dts	35 clock-frequency = <200000000>; /* Filled in by zImage / 36 timebase-frequency = <0>; / Filled in by zImage / 48 reg = <0x00000000 0x00000000>; / Filled in by zImage / 66 clock-frequency = <0>; / Filled in by zImage / 93 clock-frequency = <0>; / Filled in by zImage / 100 clock-frequency = <0>; / Filled in by zImage / 111 clock-frequency = <0>; / Filled in by zImage / 136 local-mac-address = [000000000000]; / Filled in by zImage / 156 / The ranges property is supplied by the bootwrapper 160 clock-frequency = <0>; /* Filled in by zImage */
D	acadia.dts	`34 clock-frequency = <0>; /* Filled in by wrapper / 35 timebase-frequency = <0>; / Filled in by wrapper / 47 reg = <0x0 0x0>; / Filled in by wrapper / 65 clock-frequency = <0>; / Filled in by wrapper / 89 clock-frequency = <0>; / Filled in by wrapper / 96 clock-frequency = <0>; / Filled in by wrapper / 106 clock-frequency = <0>; / Filled in by wrapper / 136 local-mac-address = [000000000000]; / Filled in by wrapper / 217 clock-frequency = <0>; / Filled in by wrapper */`
D	hotfoot.dts	35 clock-frequency = <0>; /* Filled in by zImage / 36 timebase-frequency = <0>; / Filled in by zImage / 48 reg = <0x00000000 0x00000000>; / Filled in by zImage / 66 clock-frequency = <0>; / Filled in by zImage / 93 clock-frequency = <0>; / Filled in by zImage / 102 clock-frequency = <0>; / Filled in by zImage / 113 clock-frequency = <0>; / Filled in by zImage / 167 local-mac-address = [000000000000]; / Filled in by zImage / 188 local-mac-address = [000000000000]; / Filled in by zImage / 209 / The ranges property is supplied by the bootwrapper [all …]
D	obs600.dts	6 * Based on Kilauea by: 39 clock-frequency = <0>; /* Filled in by U-Boot / 40 timebase-frequency = <0>; / Filled in by U-Boot / 52 reg = <0x00000000 0x00000000>; / Filled in by U-Boot / 103 clock-frequency = <0>; / Filled in by U-Boot / 146 clock-frequency = <0>; / Filled in by U-Boot / 153 clock-frequency = <0>; / Filled in by U-Boot / 154 / ranges property is supplied by U-Boot / 200 clock-frequency = <0>; / Filled in by U-Boot / 211 clock-frequency = <0>; / Filled in by U-Boot */ [all …]
D	mpc836x_rdk.dts	`10 * under the terms of the GNU General Public License as published by the 45 /* filled by u-boot / 54 / filled by u-boot / 66 / filled by u-boot / 109 / filled by u-boot / 119 / filled by u-boot / 205 / filled by u-boot / 279 / filled by u-boot / 294 / filled by u-boot / 309 / filled by u-boot */ [all …]`
D	arches.dts	17 * published by the Free Software Foundation; either version 2 of 55 clock-frequency = <0>; /* Filled in by U-Boot / 56 timebase-frequency = <0>; / Filled in by U-Boot / 69 reg = <0x00000000 0x00000000 0x00000000>; / Filled in by U-Boot / 143 clock-frequency = <0>; / Filled in by U-Boot / 178 clock-frequency = <0>; / Filled in by U-Boot / 185 clock-frequency = <0>; / Filled in by U-Boot / 186 / ranges property is supplied by U-Boot / 228 clock-frequency = <0>; / Filled in by U-Boot / 229 current-speed = <0>; / Filled in by U-Boot */ [all …]
D	bluestone.dts	9 * published by the Free Software Foundation; either version 2 of 47 clock-frequency = <0>; /* Filled in by U-Boot / 48 timebase-frequency = <0>; / Filled in by U-Boot / 61 reg = <0x00000000 0x00000000 0x00000000>; / Filled in by U-Boot / 143 clock-frequency = <0>; / Filled in by U-Boot / 171 clock-frequency = <0>; / Filled in by U-Boot / 178 clock-frequency = <0>; / Filled in by U-Boot / 179 / ranges property is supplied by U-Boot / 257 clock-frequency = <0>; / Filled in by U-Boot / 258 current-speed = <0>; / Filled in by U-Boot */ [all …]
D	haleakala.dts	34 clock-frequency = <0>; /* Filled in by U-Boot / 35 timebase-frequency = <0>; / Filled in by U-Boot / 47 reg = <0x00000000 0x00000000>; / Filled in by U-Boot / 89 clock-frequency = <0>; / Filled in by U-Boot / 125 clock-frequency = <0>; / Filled in by U-Boot / 132 clock-frequency = <0>; / Filled in by U-Boot / 133 / ranges property is supplied by U-Boot / 171 clock-frequency = <0>; / Filled in by U-Boot / 182 clock-frequency = <0>; / Filled in by U-Boot / 221 local-mac-address = [000000000000]; / Filled in by U-Boot */
D	glacier.dts	37 clock-frequency = <0>; /* Filled in by U-Boot / 38 timebase-frequency = <0>; / Filled in by U-Boot / 51 reg = <0x00000000 0x00000000 0x00000000>; / Filled in by U-Boot / 125 clock-frequency = <0>; / Filled in by U-Boot / 166 clock-frequency = <0>; / Filled in by U-Boot / 173 clock-frequency = <0>; / Filled in by U-Boot / 174 / ranges property is supplied by U-Boot / 243 clock-frequency = <0>; / Filled in by U-Boot / 244 current-speed = <0>; / Filled in by U-Boot / 254 clock-frequency = <0>; / Filled in by U-Boot */ [all …]
D	klondike.dts	`9 * published by the Free Software Foundation; either version 2 of 46 clock-frequency = <300000000>; /* Filled in by U-Boot / 47 timebase-frequency = <300000000>; / Filled in by U-Boot / 59 reg = <0x00000000 0x20000000>; / Filled in by U-Boot / 113 clock-frequency = <0>; / Filled in by U-Boot / 144 clock-frequency = <300000000>; / Filled in by U-Boot / 171 local-mac-address = [000000000000]; / Filled in by U-Boot / 201 local-mac-address = [000000000000]; / Filled in by U-Boot */`
D	makalu.dts	35 clock-frequency = <0>; /* Filled in by U-Boot / 36 timebase-frequency = <0>; / Filled in by U-Boot / 48 reg = <0x00000000 0x00000000>; / Filled in by U-Boot / 90 clock-frequency = <0>; / Filled in by U-Boot / 126 clock-frequency = <0>; / Filled in by U-Boot / 133 clock-frequency = <0>; / Filled in by U-Boot / 134 / ranges property is supplied by U-Boot / 172 clock-frequency = <0>; / Filled in by U-Boot / 183 clock-frequency = <0>; / Filled in by U-Boot / 222 local-mac-address = [000000000000]; / Filled in by U-Boot */ [all …]
D	mgcoge.dts	`8 * under the terms of the GNU General Public License as published by the 36 timebase-frequency = <0>; /* Filled in by U-Boot / 37 clock-frequency = <0>; / Filled in by U-Boot / 38 bus-frequency = <0>; / Filled in by U-Boot / 97 reg = <0 0>; / Filled in by U-Boot / 147 current-speed = <0>; / Filled in by U-Boot / 155 local-mac-address = [ 00 00 00 00 00 00 ]; / Filled in by U-Boot */`
D	ebony.dts	`38 clock-frequency = <0>; // Filled in by zImage 39 timebase-frequency = <0>; // Filled in by zImage 51 reg = <0x00000000 0x00000000 0x00000000>; // Filled in by zImage 88 clock-frequency = <0>; // Filled in by zImage 136 clock-frequency = <0>; // Filled in by zImage 143 clock-frequency = <0>; // Filled in by zImage 144 // ranges property is supplied by zImage 251 local-mac-address = [000000000000]; // Filled in by zImage 270 local-mac-address = [000000000000]; // Filled in by zImage`
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
D	S3C2412.txt	41 The UART hardware is similar to the S3C2440, and is supported by the 48 The NAND hardware is similar to the S3C2440, and is supported by the 56 control. The OHCI portion is supported by the ohci-s3c2410 driver, and 57 the clock control selection is supported by the core clock code. 76 The RTC hardware is similar to the S3C2410, and is supported by the 83 The watchdog hardware is the same as the S3C2410, and is supported by 95 The IIC hardware is the same as the S3C2410, and is supported by the
/linux-4.4.14/net/netfilter/ipset/
D	Kconfig	24 The value can be overridden by the 'max_sets' module 31 This option adds the bitmap:ip set type support, by which one 40 This option adds the bitmap:ip,mac set type support, by which one 49 This option adds the bitmap:port set type support, by which one 58 This option adds the hash:ip set type support, by which one 68 This option adds the hash:ip,mark set type support, by which one 77 This option adds the hash:ip,port set type support, by which one 86 This option adds the hash:ip,port,ip set type support, by which 96 This option adds the hash:ip,port,net set type support, by which 106 This option adds the hash:mac set type support, by which [all …]
/linux-4.4.14/Documentation/networking/
D	lapb-module.txt	7 The LAPB module will be a separately compiled module for use by any parts of 9 defines the interfaces to, and the services provided by this module. The 74 be unacknowledged by the remote end, the value of the window is between 1 89 MLP operation is the same as SLP operation except that the addresses used by 107 generated by the device driver to allow for the unique identification of the 108 instance of the LAPB link. It is returned by the LAPB module in all of the 109 callbacks, and is used by the device driver in all calls to the LAPB module. 175 is successful then the skbuff is owned by the LAPB module and may not be 176 used by the device driver again. The valid return values are: 188 is owned by the LAPB module and may not be used by the device driver again. [all …]
D	netdev-features.txt	19 one used internally by network core: 22 be changed (enabled or disabled) for a particular device by user's 27 for a device. This should be changed only by network core or in 31 by child VLAN devices (limits netdev->features set). This is currently 35 4. netdev->wanted_features set contains feature set requested by user. 36 This set is filtered by ndo_fix_features callback whenever it or 46 is calculated and filtered by calling ndo_fix_features callback 61 A driver that wants to trigger recalculation must do so by calling 63 from ndo_*_features callbacks. netdev->features should not be modified by 64 driver except by means of ndo_fix_features callback. [all …]
D	vxge.txt	`44 v) Offloads supported: (Enabled by default) 49 vi) MSI-X: (Enabled by default) 53 vii) NAPI: (Enabled by default) 56 viii)RTH (Receive Traffic Hash): (Enabled by default) 63 x) Multiple hardware queues: (Enabled by default) 65 multiple steering options (transmit multiqueue enabled by default).`
D	x25.txt	`8 framing, bit-stuffing and checksumming. These both need to be handled by the 12 Packet Layer is concerned, the link layer was being performed by a lower 14 implementation of LAPB. Therefore the LAPB modules would be called by 15 unintelligent X.25 card drivers and not by intelligent ones, this would 22 being served by the LLC will be completely separate from LAPB. The LLC 24 by a different author.`
D	alias.txt	`10 An alias is formed by adding a colon and a string when running ifconfig. 14 Alias creation is done by 'magic' interface naming: eg. to create a 20 The corresponding route is also set up by this command. 25 The alias is removed by shutting the alias down:`
D	LICENSE.qlcnic	6 Exhibit A) published by the Free Software Foundation (version 2). 27 using it. (Some other Free Software Foundation software is covered by 55 software. If the software is modified by someone else and passed on, we 57 that any problems introduced by others will not reflect on the original 60 Finally, any free program is threatened constantly by software 73 a notice placed by the copyright holder saying it may be distributed 83 covered by this License; they are outside its scope. The act of 86 Program (independent of having been made by running the Program). 135 your rights to work written entirely by you; rather, the intent is to 176 If distribution of executable or object code is made by offering [all …]
D	LICENSE.qlge	6 Exhibit A) published by the Free Software Foundation (version 2). 27 using it. (Some other Free Software Foundation software is covered by 55 software. If the software is modified by someone else and passed on, we 57 that any problems introduced by others will not reflect on the original 60 Finally, any free program is threatened constantly by software 73 a notice placed by the copyright holder saying it may be distributed 83 covered by this License; they are outside its scope. The act of 86 Program (independent of having been made by running the Program). 135 your rights to work written entirely by you; rather, the intent is to 176 If distribution of executable or object code is made by offering [all …]
D	dns_resolver.txt	20 by way of requesting a key of key type dns_resolver. These queries are 23 These routines must be supported by userspace tools dns.upcall, cifs.upcall and 40 The module should be enabled by turning on the kernel configuration options: 89 length should be given by the namelen argument. 106 This can be cleared by any process that has the CAP_SYS_ADMIN capability by 130 directed by means of configuration lines in /etc/request-key.conf that tell 154 Debugging messages can be turned on dynamically by writing a 1 into the
/linux-4.4.14/Documentation/cgroups/
D	cpuacct.txt	`11 Accounting groups can be created by first mounting the cgroup filesystem. 19 by this group which is essentially the CPU time obtained by all the tasks 29 process (bash) into it. CPU time consumed by this bash and its children 34 CPU time obtained by the cgroup into user and system times. Currently 37 user: Time spent by tasks of the cgroup in user mode. 38 system: Time spent by tasks of the cgroup in kernel mode.`
D	cgroups.txt	4 Written by Paul Menage <menage@google.com> based on 10 Modified by Paul Jackson <pj@sgi.com> 11 Modified by Christoph Lameter <clameter@sgi.com> 26 2.3 Mounting hierarchies by name 50 facilities provided by cgroups to treat groups of tasks in 65 User-level code may create and destroy cgroups by name in an 107 As an example of a scenario (originally proposed by vatsa@in.ibm.com) 137 (by putting those resource subsystems in different hierarchies), 178 can be determined by following pointers through the 190 - You can list all the tasks (by PID) attached to any cgroup. [all …]
D	blkio-controller.txt	111 CFQ by default and throttling with "sane_behavior" will handle the 115 directly generated by tasks in that cgroup. 147 on all the devices until and unless overridden by per device rule. 154 by blkio.weight. 191 - number of sectors transferred to/from disk by the group. First 193 third field specifies the number of sectors transferred by the 197 - Number of bytes transferred to/from the disk by the group. These 198 are further divided by the type of operation - read or write, sync 204 - Number of IOs (bio) issued to the disk by the group. These 205 are further divided by the type of operation - read or write, sync [all …]
/linux-4.4.14/Documentation/fb/
D	api.txt	10 This document describes the frame buffer API used by applications to interact 47 frame buffer memory in the format expected by the hardware. 49 Formats are described by frame buffer types and visuals. Some visuals require 87 Macropixels are stored in memory as described by the format FOURCC identifier 93 specified by the variable screen information bpp field. 95 Black pixels are represented by all bits set to 1 and white pixels by all bits 104 specified by the variable screen information bpp field. 106 Black pixels are represented by all bits set to 0 and white pixels by all bits 127 Each pixel value is stored in the number of bits reported by the variable 140 Pixels are encoded and interpreted as described by the format FOURCC [all …]
D	vt8623fb.txt	`22 * text mode (activated by bpp = 0) 29 lower pixclocks (maximum about 100 MHz). This limitation is not enforced by 39 if device is active (for example used by fbcon). 46 * secondary (not initialized by BIOS) device support`
D	tgafb.txt	14 This version is an almost complete rewrite of the code written by Geert 15 Uytterhoeven, which was based on the original TGA console code written by 22 (by allowing the video mode to be set at boot time) 40 separated by comma, values are separated from options by `:').
D	arkfb.txt	`24 * text mode (activated by bpp = 0) 31 hardware). This limitation is not enforced by driver. Text mode supports 8bit 42 if device is active (for example used by fbcon). 49 * secondary (not initialized by BIOS) device support`
/linux-4.4.14/Documentation/filesystems/
D	vfs.txt	32 calls. The pathname argument that is passed to them is used by the VFS 42 the way, and then loading the inode. This is done by looking up the 54 are written back to disc. A single inode can be pointed to by multiple 58 the parent directory inode. This method is installed by the specific 76 can see that this is another switch performed by the VFS. The file 80 is done by using the userspace file descriptor to grab the appropriate 100 filesystem. New vfsmount referring to the tree returned by ->mount() 148 by the specific filesystem code 157 The mount() method must return the root dentry of the tree requested by 182 mount_nodev: mount a filesystem that is not backed by a device [all …]
D	omfs.txt	6 OMFS is a filesystem created by SonicBlue for use in the ReplayTV DVR 32 uid=n - make all files owned by specified user 33 gid=n - make all files owned by specified group 45 have a smaller size than a data block, but since they are both addressed by the 63 Files and directories are both represented by omfs_inode: 81 until a match is found on i_name. Empty buckets are represented by block 84 A file is an omfs_inode structure followed by an extent table beginning at 99 Each extent holds the block offset followed by number of blocks allocated to 104 If this table overflows, a continuation inode is written and pointed to by
D	afs.txt	41 The filesystem should be enabled by turning on the kernel configuration 53 They permit the debugging messages to be turned on dynamically by manipulating 79 Once the module has been loaded, more modules can be added by the following 85 volume location servers within that cell, with the latter separated by colons. 87 Filesystems can be mounted anywhere by commands similar to the following: 125 This can be used by the administrator to attempt to unmount the whole AFS tree 126 mounted on /afs in one go by doing: 164 the system belongs is added to the database when modprobe is performed by the 168 Further cells can be added by commands similar to the following: 180 Secure operations are initiated by acquiring a key using the klog program. A [all …]
D	vfat.txt	59 is used by the console. It can be enabled for the 75 end in '~1' or tilde followed by some number. If this 83 scanning disk. But it's not used by default, because 86 correct, by this option you can avoid scanning disk. 109 between local time (as used by Windows on FAT) and UTC 116 used by FAT to UTC. I.e. <minutes> minutes will be subtracted 117 from each timestamp to convert it to UTC used internally by 119 not the time zone used by the filesystem. Note that this 122 setting will be off by one hour. 126 .COM, or .BAT. Not set by default. [all …]
D	gfs2-uevents.txt	`6 for (by gfs_controld in gfs2-utils). 14 uevent generated by the newly created filesystem. If the mount 29 be generated by older kernels. 34 successful mount of the filesystem by the first node (FIRSTMOUNT=Done). 35 This is used as a signal by gfs_controld that it is then ok for other 65 have been preceded by at least an ADD uevent for the same filesystem, 66 and unlike the other uevents is generated automatically by the kernel's 89 If a journal is in use by the filesystem (journals are not`
D	nilfs2.txt	`58 mounted. Checkpoints and snapshots are listed by lscp 86 There is some NILFS2 specific functionality which can be accessed by applications 101 ioctl is used in lscp utility and by 105 used by lscp, rmcp utilities and by 110 nilfs_resize utilities and by nilfs_cleanerd 114 segments. This ioctl is used by 122 by nilfs_cleanerd daemon. 125 This ioctl is used by nilfs_cleanerd daemon. 128 block numbers. This ioctl is used by 133 userspace. This ioctl is used by [all …]`
D	f2fs.txt	65 2. It loads parent index structures of all the data in the victim identified by 108 collection is on by default. 117 by default if CONFIG_F2FS_FS_XATTR is selected. 119 by default if CONFIG_F2FS_FS_POSIX_ACL is selected. 123 disable_ext_identify Disable the extension list configured by mkfs, so f2fs 147 increasing the cache hit ratio. Set by default. 151 enabled by default. 161 - major file system information managed by f2fs currently 163 - current memory footprint consumed by f2fs. 213 conducts. 32 sections is set by default. [all …]
/linux-4.4.14/Documentation/input/
D	joystick.txt	3 Sponsored by SuSE 9 under the terms of the GNU General Public License as published by the Free 22 Should you need to contact me, the author, you can do so either by e-mail 23 - mail your message to <vojtech@ucw.cz>, or by paper mail: Vojtech Pavlik, 117 program in the utilities package. You run it by typing: 123 joystick is in the center position. They should not jitter by themselves to 135 joystick should be autocalibrated by the driver automagically. However, with 171 Cyborg 'digital' joysticks are also supported by this driver, because 206 specify the type as a number by combining the bits in the table below. This 243 Microsoft 'Digital Overdrive' protocol is supported by the sidewinder.c [all …]
D	userio.txt	3 Sponsored by Red Hat 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 19 kernel module by writing to the device, and any data received from the serio 36 argument, this field can be left untouched and will be ignored by the kernel. 37 Each command should be sent by writing the struct directly to the character 39 returned by the character device and a more descriptive error will be printed
D	walkera0701.txt	40 walkera0701 module, check dmesg for error messages. Connect TX to PC by 42 be changed by TX "joystick", check output from /proc/interrupts. Value for 53 Based on walkera WK-0701 PCM Format description by Shaul Eizikovich. 80 (Warning, pulses on ACK are inverted by transistor, irq is raised up on sync 89 first 10 nibbles. Analog value is represented by one sign bit and 9 bit 107 calculated by sum of binary values in checked nibbles + sum of octal values 108 in checked nibbles divided by 8. Only bit 0 of this sum is used.
/linux-4.4.14/Documentation/ABI/testing/
D	sysfs-ata	`17 Number of IRQ received by the port while idle [some ata HBA only]. 36 Maximum speed supported by the connected SATA device. 40 Maximum speed imposed by libata. 62 Transfer modes supported by the device when in DMA mode. 63 Mostly used by PATA device. 67 Transfer modes supported by the device when in PIO mode. 68 Mostly used by PATA device. 95 Shows the DSM TRIM mode currently used by the device. Valid`
D	sysfs-driver-ppi	`7 Presence Interface). Only if TPM is supported by BIOS, this 8 folder makes sense. The folder path can be got by command 22 This attribute shows the version of the PPI supported by the 60 operation to be executed in the pre-OS environment by the BIOS 61 for the requests defined by TCG, i.e. requests from 1 to 22. 63 This attribute is only supported by PPI version 1.2+. 71 operation to be executed in the pre-OS environment by the BIOS 74 is also only supported by PPI version 1.2+.`
D	sysfs-bus-css	`5 Description: Contains the subchannel type, as reported by the hardware. 20 Description: Contains the ids of the channel paths used by this 21 subchannel, as reported by the channel subsystem 30 Description: Contains the PIM/PAM/POM values, as reported by the 31 channel subsystem when last queried by the common I/O`
D	sysfs-class-net-statistics	6 Indicates the number of collisions seen by this network device. 14 Indicates the number of multicast packets received by this 22 Indicates the number of bytes received by this network device. 31 Indicates the number of compressed packets received by this 41 by this network device. Note that the specific meaning might 42 depend on the MAC layer used by the interface. 49 Indicates the number of packets received by the network device 59 Indicates the number of receive FIFO errors seen by this 106 Indicates the total number of good packets received by this 115 during transmission by a network device (e.g: because of [all …]
D	sysfs-firmware-dmi-entries	`21 Some entries are required by the specification, but many 29 assigned by the operating system an 'instance', which is 54 entry by the firmware. This handle may be 55 referred to by other entries. 61 "formatted" region is sometimes followed by 64 by a two nul characters in series. 87 typically backed by nvram, but the implementation 88 details are abstracted by this table. This entry's data 110 as described by the DMI entry.`
D	sysfs-bus-event_source-devices-events	`18 supported by many/most CPUs. These events can be monitored 26 "raw code" for the perf event identified by the file's 37 performance monitoring event supported by the <pmu>. The name 58 particular set of bits (as defined by the format file 63 need to be provided by the user selecting the particular event. 73 (once multiplied by <event>.scale) represents. 85 scientific notation to be multiplied by the event count`
D	sysfs-driver-hid-wiimote	32 Description: While a device is initialized by the wiimote driver, we perform 52 values for all 4 sensors. The values are separated by colons and 54 First, 0kg values for all 4 sensors are written, followed by the 57 Calibration data is already applied by the kernel to all input 58 values but may be used by user-space to perform other 71 Calibration data is already applied by the kernel to all input 72 values but may be used by user-space to perform other 74 Calibration data is detected by the kernel during device setup.
D	sysfs-power	41 the name of the method by which the system will be put to 44 by some firmware, in which case we also assume that the 46 'platform' - the memory image will be saved by the kernel and 47 the system will be put to sleep by the platform driver (e.g. 49 'shutdown' - the memory image will be saved by the kernel and 51 'reboot' - the memory image will be saved by the kernel and 67 The suspend-to-disk method may be chosen by writing to this 85 created by the suspend-to-disk mechanism. It can be written a 95 limit, which is set to 500 MB by default. 106 it contains '0' which may be changed to '1' by writing a [all …]
D	sysfs-ptp	`41 alarms offer by the PTP hardware clock. 48 channels offered by the PTP hardware clock. 55 output channels offered by the PTP hardware clock. 62 offered by the PTP hardware clock. 69 pin offered by the PTP hardware clock. The file name 74 assignment may be changed by two writing numbers into 92 channel index followed by a "1" into the file. 94 index followed by a "0" into the file.`
D	sysfs-class-devfreq	`15 governor used by the corresponding devfreq object. 23 target_freq when get_cur_freq() is not implemented by 73 by the min/max frequency restrictions. 87 the minimum frequency requested by users. It is 0 if 89 frequency requested by governors. 96 the maximum frequency requested by users. It is 0 if 98 frequency requested by governors and min_freq.`
D	sysfs-devices-soc	`7 regarding each SoC can be obtained by reading sysfs files. This 8 functionality is only available if implemented by the platform. 33 Read-only attribute supported by most SoCs. In the case of 40 Read-only attribute supported by most SoCs. Contains the SoC's 48 the process by which the silicon chip was manufactured.`
D	sysfs-platform-dell-laptop	`19 as reported by the ambient light sensor. 31 enabled are preceded by '+', those disabled by '-'. 33 To enable a trigger, write its name preceded by '+' to 35 by '-' instead.`
D	sysfs-devices-real_power_state	`11 power state of the given device node as returned by the _PSC 14 "D3cold", reflect the power state names defined by the ACPI 20 resources used by the device node are only ON because of some`
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
D	max77693.txt	54 Valid values: 3650000 - 4400000, step by 25000 (rounded down) 58 Valid values: 3000000 - 3700000, step by 100000 (rounded down) 63 the charging current will be reduced by 105 mA/Celsius. 69 Valid values: 2000000 - 3500000, step by 250000 (rounded down) 84 by one child node. 100 Valid values: 3300 - 5500, step by 25 (rounded down) 105 Valid values: 2400 - 3400, step by 33 (rounded down) 113 15625 - 250000, step by 15625 (rounded down) 115 15625 - 500000, step by 15625 (rounded down) 119 15625 - 1000000, step by 15625 (rounded down) [all …]
/linux-4.4.14/Documentation/devicetree/bindings/spi/
D	snps,dw-apb-ssi.txt	`6 - interrupts : One interrupt, used by the controller. 7 - #address-cells : <1>, as required by generic SPI binding. 8 - #size-cells : <0>, also as required by generic SPI binding. 13 - reg-io-width : The I/O register width (in bytes) implemented by this`
D	spi-octeon.txt	`6 - interrupts : One interrupt, used by the controller. 7 - #address-cells : <1>, as required by generic SPI binding. 8 - #size-cells : <0>, also as required by generic SPI binding.`
/linux-4.4.14/Documentation/devicetree/bindings/mips/img/
D	xilfpga.txt	`11 project provided by IMG. 13 The example project runs on the Nexys4DDR board by Digilent powered by 14 the ARTIX-7 FPGA by Xilinx. 43 - clocks: phandle to ext clock for fixed-clock received by MIPS core. 74 DDR initialization is already handled by a HW IP block.`
/linux-4.4.14/Documentation/cpu-freq/
D	intel-pstate.txt	24 In addition to the interfaces provided by the cpufreq core for 29 max_perf_pct: limits the maximum P state that will be requested by 31 available (P states) performance may be reduced by the no_turbo 34 min_perf_pct: limits the minimum P state that will be requested by 42 is supported by hardware that is in the turbo range. This number 46 by hardware. This number is independent of whether turbo has 49 For contemporary Intel processors, the frequency is controlled by the 54 will run at is selected by the processor itself.
D	pcc-cpufreq.txt	11 * it under the terms of the GNU General Public License as published by 56 satisfied by platform firmware, then it usually means that power budget 66 is used by the OS to inform the platform firmware that a command has been 74 The following commands are supported by the PCC interface: 100 This command is used by the OSPM to query the running frequency of the 104 also signifies if the CPU frequency is limited by a power budget condition. 108 This command is used by the OSPM to communicate to the platform firmware the 110 ignored by OSPM. The next invocation of "Get Average Frequency" will inform 130 frequencies supported by the platform firmware. 151 /sys filesystem and how their values are affected by the PCC driver: [all …]
/linux-4.4.14/drivers/staging/unisys/Documentation/
D	proc-entries.txt	2 This document describes the proc entries created by the Unisys s-Par modules. 11 entries for the controlvm channel used by visorchipset. 17 /proc/visorchipset/chipsetready: This entry is written to by scripts 23 These entries provide status of the devices shared by a service partition. 30 performance, by setting the number of cycles we wait before going idle 34 /proc/uislib/smart_wakeup: This entry is used to tune performance, by 40 /proc/virthba/enable_ints: This entry controls interrupt use by the 55 /proc/virtnic/enable_ints: This entry controls interrupt use by the 65 directory for each device provided by that module. Each device has a 87 /proc/visorchipset/installer: this entry is used by the installation
D	overview.txt	25 The back-end for each device is owned and managed by a small, 61 visorbus_register_visor_driver() that is called by each of the function 64 GUIDs) it wants to handle. For use by function drivers, visorbus provides 80 arrives and departs, by calling the function driver's probe() and remove() 84 each virtual device are created and owned by visorbus. These device objects 100 * the GUID(s) of the channel type(s) that are handled by this driver, as 113 called automatically by the visorbus driver at appropriate times: 208 that this info is provided by a particular 228 "keyboard". Note that this name is provided by 248 disk devices, by proxying SCSI commands between the guest and the service [all …]
/linux-4.4.14/Documentation/rapidio/
D	rapidio.txt	6 use in embedded systems. Development of the RapidIO standard is directed by the 17 into the kernel similarly to other buses by defining RapidIO-specific device and 28 Each of these components is represented in the subsystem by an associated data 37 by a rio_mport data structure. This structure contains master port specific 42 RapidIO master ports are serviced by subsystem specific mport device drivers 51 All devices are presented in the RapidIO subsystem by corresponding rio_dev data 59 switch is defined by an internal routing table. A switch is presented in the 60 RapidIO subsystem by rio_dev data structure expanded by additional rio_switch 71 Each RapidIO network known to the system is represented by corresponding rio_net 85 common services may act separately from device-specific drivers or be used by [all …]
D	tsi721.txt	`27 mode API defined by common Linux kernel DMA Engine framework. 30 by setting CONFIG_RAPIDIO_DMA_ENGINE option. Tsi721 miniport driver uses seven 36 "dma_desc_per_channel" - defines number of hardware buffer descriptors used by 37 each BDMA channel of Tsi721 (by default - 128). 51 under the terms of the GNU General Public License as published by the Free`
/linux-4.4.14/Documentation/arm/nwfpe/
D	README	4 The majority of the code was written by me, Scott Bambrough It is 22 The floating point operations are based on SoftFloat Release 2, by 27 All operations required by the standard are implemented, except for 30 SoftFloat to the ARM was done by Phil Blundell, based on an earlier 31 port of SoftFloat version 1 by Neil Carson for NetBSD/arm32. 57 SoftFloat was written by John R. Hauser. This work was made possible in 58 part by the International Computer Science Institute, located at Suite 600, 60 provided by the National Science Foundation under grant MIP-9311980. The 63 California at Berkeley, overseen by Profs. Nelson Morgan and John Wawrzynek.
/linux-4.4.14/Documentation/i2c/
D	fault-codes	11 recovery, triggered by a fault report, there is no error. 34 Also, codes returned by adapter probe methods follow rules which are 39 Returned by I2C adapters when they lose arbitration in master 48 Returned by SMBus logic when an invalid Packet Error Code byte 57 Returned by SMBus adapters when the bus was busy for longer 73 Returned by driver probe() methods. This is a bit more 81 Returned by any component that can't allocate memory when 85 Returned by I2C adapters to indicate that the address phase 90 Returned by driver probe() methods to indicate that they 94 Returned by an adapter when asked to perform an operation [all …]
/linux-4.4.14/drivers/media/usb/pwc/
D	Kconfig	`20 The PCA635, PCVC665 and PCVC720/20 are not supported by this driver 21 and never will be, but the 665 and 720/20 are supported by other 24 Some newer logitech webcams are not handled by this driver but by the 27 The built-in microphone is enabled by selecting USB Audio support.`
/linux-4.4.14/fs/xfs/libxfs/
D	xfs_dir2.h	205 xfs_dir2_byte_to_dataptr(xfs_dir2_off_t by) in xfs_dir2_byte_to_dataptr() argument 207 return (xfs_dir2_dataptr_t)(by >> XFS_DIR2_DATA_ALIGN_LOG); in xfs_dir2_byte_to_dataptr() 214 xfs_dir2_byte_to_db(struct xfs_da_geometry geo, xfs_dir2_off_t by) in xfs_dir2_byte_to_db() argument 216 return (xfs_dir2_db_t)(by >> geo->blklog); in xfs_dir2_byte_to_db() 232 xfs_dir2_byte_to_off(struct xfs_da_geometry geo, xfs_dir2_off_t by) in xfs_dir2_byte_to_off() argument 234 return (xfs_dir2_data_aoff_t)(by & (geo->blksize - 1)); in xfs_dir2_byte_to_off() 269 xfs_dir2_byte_to_da(struct xfs_da_geometry *geo, xfs_dir2_off_t by) in xfs_dir2_byte_to_da() argument 271 return xfs_dir2_db_to_da(geo, xfs_dir2_byte_to_db(geo, by)); in xfs_dir2_byte_to_da()
/linux-4.4.14/Documentation/features/
D	arch-support.txt	`8 \| ok \| # feature supported by the architecture 9 \|TODO\| # feature not yet supported by the architecture 10 \| .. \| # feature cannot be supported by the hardware`
/linux-4.4.14/Documentation/scsi/
D	dtc3x80.txt	`2 by Ray Van Tassle (rayvt@comm.mot.com) March 1996 3 Based on the generic & core NCR5380 code by Drew Eckhard 13 supported by the driver. 18 buffering is done automagically by the chip. Data is transferred 25 Parity is supported by the chip, but not by this driver.`
D	hpsa.txt	28 nor supported by HP with this driver. For older Smart Arrays, the cciss 35 command completions indicated by a single interrupt. 55 triggered automatically by HP's Array Configuration Utility (either the GUI or 67 or "simple" mode. This is controlled by the "hpsa_simple_mode" module 73 parameter is used by kdump, for example, to reset the controller at driver 76 and not be disrupted in any way by stale commands or other stale state 103 not all of the ioctls supported by the cciss driver are also supported by the 104 hpsa driver. The data structures used by these are described in 128 These are used extensively by the HP Array Configuration Utility, SNMP storage
D	ChangeLog.ncr53c8xx	4 Fix sent by Stig Telfer <stig@api-networks.com>. 31 * Clarify memory barriers needed by the driver for architectures 35 sym53c8xx_defs.h header files. They are now shared by the 66 be shared by sym53c8xx and ncr53c8xx drivers. For now, it is 67 a header file that is only included by the ncr53c8xx driver, 83 be shared by sym53c8xx and ncr53c8xx drivers. For now, it is 84 a header file that is only included by the ncr53c8xx driver, 122 - Change messages written by the driver at initialisation and 130 - Change the driver detection code by the sym53c8xx one, modulo 148 - Replace __initfunc() which is deprecated stuff by __init which [all …]
D	aha152x.txt	5 TC1550 patches by Luuk van Dijk (ldz@xs4all.nl) 54 The normal configuration can be overridden by specifying a command line. 117 returned by the SCSI BIOS is a pure calculation and has nothing to 130 The AHA-1522 BIOS calculates the geometry by fixing the number of heads 131 to 64, the number of sectors to 32 and by calculating the number of 132 cylinders by dividing the capacity reported by the disk by 6432 (1 MB). 139 63 for sectors and then divides the capacity of the disk by 25563 158 - if that fails, take extended translation if enabled by override,
D	LICENSE.qla4xxx	7 Exhibit A) published by the Free Software Foundation (version 2). 28 using it. (Some other Free Software Foundation software is covered by 56 software. If the software is modified by someone else and passed on, we 58 that any problems introduced by others will not reflect on the original 61 Finally, any free program is threatened constantly by software 74 a notice placed by the copyright holder saying it may be distributed 84 covered by this License; they are outside its scope. The act of 87 Program (independent of having been made by running the Program). 136 your rights to work written entirely by you; rather, the intent is to 177 If distribution of executable or object code is made by offering [all …]
D	LICENSE.qla2xxx	7 Exhibit A) published by the Free Software Foundation (version 2). 29 using it. (Some other Free Software Foundation software is covered by 57 software. If the software is modified by someone else and passed on, we 59 that any problems introduced by others will not reflect on the original 62 Finally, any free program is threatened constantly by software 75 a notice placed by the copyright holder saying it may be distributed 85 covered by this License; they are outside its scope. The act of 88 Program (independent of having been made by running the Program). 137 your rights to work written entirely by you; rather, the intent is to 178 If distribution of executable or object code is made by offering [all …]
/linux-4.4.14/Documentation/ABI/stable/
D	sysfs-driver-usb-usbtmc	`7 by the device itself. The full description of the bitfields 21 by the device itself. The full description of the bitfields 35 device as described by the document, "Universal Serial Bus Test 37 (USBTMC) Revision 1.0" as published by the USB-IF. 51 published by the USB-IF. 62 (USBTMC) Revision 1.0" as published by the USB-IF.`
D	sysfs-class-rfkill	`14 Each registered rfkill driver is represented by an rfkillX 22 Description: Name assigned by driver to this key (interface or driver name). 54 The transmitter is forced off by something outside of 67 The transmitter is turned off by software.`
/linux-4.4.14/Documentation/locking/
D	lglock.txt	17 as per_cpu elements but can be mostly handled by CPU local actions 28 - by expensive access to all CPUs locks - effectively 43 One can relax the migration constraints by acquiring the current 63 On -RT this deadlock scenario is resolved by the arch_spin_locks in the 64 lglocks being replaced by rt_mutexes which resolve the above deadlock 65 by boosting the lock-holder. 73 turned into a set of functions by Andi Kleen [7]. The change to functions 74 was motivated by the presence of multiple lock users and also by them 151 The 'Big Reader' read-write spinlocks were originally introduced by 153 later were introduced by the VFS scalability patch set in 2.6 series [all …]
/linux-4.4.14/Documentation/hwmon/
D	ltc4260	`37 Voltage readings provided by this driver are reported as obtained from the ADC 39 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the 43 Current reading provided by this driver is reported as obtained from the ADC 46 current by dividing the reported value by the sense resistor value in mOhm.`
D	ltc4261	`37 Voltage readings provided by this driver are reported as obtained from the ADC 39 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the 43 Current reading provided by this driver is reported as obtained from the ADC 46 current by dividing the reported value by the sense resistor value in mOhm.`
D	ltc2945	`37 Voltage readings provided by this driver are reported as obtained from the ADC 39 real voltage by multiplying the reported value with (R1+R2)/R2, where R1 is the 43 Current reading provided by this driver is reported as obtained from the ADC 46 current by dividing the reported value by the sense resistor value in mOhm.`
D	sch5627	`21 initialization most be done by the BIOS, so if the watchdog is not enabled 22 by the BIOS the sch5627 driver will not register a watchdog device. 24 The hardware monitoring part of the SMSC SCH5627 is accessed by talking`
/linux-4.4.14/Documentation/security/
D	keys-ecryptfs.txt	8 the former case the operation is performed directly by the kernel CryptoAPI 10 the FEK is encrypted by 'ecryptfsd' with the help of external libraries in order 14 The data structure defined by eCryptfs to contain information required for the 17 by the userspace utility 'mount.ecryptfs' shipped with the package 23 authentication token in its payload with a FEFEK randomly generated by the 24 kernel and protected by the parent master key. 32 required key can be securely generated by an Administrator and provided at boot
/linux-4.4.14/Documentation/frv/
D	booting.txt	22 similar program and then downloaded and stored into flash by RedBoot. 29 The kernel will need to be loaded into RAM by RedBoot (or by some alternative 44 (2) Load by TFTP 47 default server (as negotiated by BOOTP) and store it into RAM: 53 (3) Load by Y-Modem 61 program by Y-Modem. 84 separated by spaces: 112 may be specified by major and minor number, device path, or even 137 discovered by consulting a BOOTP or DHCP server. 152 The NFS version to use can also be specified. v2 and v3 are supported by [all …]
/linux-4.4.14/Documentation/vm/
D	idle_page_tracking.txt	4 accessed by a workload and which are idle. This information can be useful for 9 It is enabled by CONFIG_IDLE_PAGE_TRACKING=y. 17 bitmap is represented by an array of 8-byte integers, and the page at PFN #i is 24 the page by writing to the file. A value written to the file is OR-ed with the 40 That said, in order to estimate the amount of pages that are not used by a 43 1. Mark all the workload's pages as idle by setting corresponding bits in 44 /sys/kernel/mm/page_idle/bitmap. The pages can be found by reading 45 /proc/pid/pagemap if the workload is represented by a process, or by 64 set, or marked accessed explicitly by the kernel (see mark_page_accessed()). The 74 - a page is accessed by a device driver using get_user_pages() [all …]
D	numa_memory_policy.txt	14 memory may be allocated by a set of processes. Memory policies are a 28 by one of the more specific policy scopes discussed below. When the 36 for a specific task, this policy controls all page allocations made by or 37 on behalf of the task that aren't controlled by a more specific scope. 39 would have been controlled by the task policy "fall back" to the System 52 subsequently created by that thread. Any sibling threads existing 57 installed. Any pages already faulted in by the task when the task 110 by any task, will obey the shared policy. 112 As of 2.6.22, only shared memory segments, created by shmget() or 123 policy installed on the virtual address range backed by the shared [all …]
D	slub.txt	6 slab caches. SLUB always includes full debugging but it is off by default. 69 switch off debugging for such caches by default, use 108 tracked by SLUB in a non debug situation. 113 To some degree SLUB's performance is limited by the need to take the 115 governed by the order of the allocation for each slab. The allocations 116 can be influenced by kernel parameters: 197 INFO: Allocated in <kernel function> age=<jiffies since alloc> cpu=<allocated by 199 INFO: Freed in <kernel function> age=<jiffies since free> cpu=<freed by cpu> 217 corruption by a write after free. 237 of the corruption is may be more likely found by looking at the function that [all …]
D	unevictable-lru.txt	45 details - the "what does it do?" - by reading the code. One hopes that the 46 descriptions below add value by provide the answer to "why does it do that?". 55 by Larry Woodman of Red Hat to address several scalability problems with page 69 (*) Those owned by ramfs. 76 unevictable, either by definition or by circumstance, in the future. 102 where they can be found by isolate_lru_page(), we would prevent their 112 lists and statistics originally proposed and posted by Christoph Lameter. 125 memory controller; see Documentation/cgroups/memory.txt] by extending the 152 address space flag is provided, and this can be manipulated by a filesystem 200 page_evictable() also checks for mlocked pages by testing an additional page [all …]
D	transhuge.txt	20 single page fault for each 2M virtual region touched by userland (so 21 reducing the enter/exit kernel frequency by a 512 times factor). This 50 backed by regular pages should be relocated on hugepages 65 if compared to the reservation approach of hugetlbfs by allowing all 76 is by far not mandatory and khugepaged already can take care of long 92 risk to lose memory by using hugepages, should use 110 time to defrag memory, we would expect to gain even more by the fact 120 It's possible to disable huge zero page by writing 0 or enable it 121 back by writing 1: 133 also possible to disable defrag in khugepaged by writing 0 or enable [all …]
D	zswap.txt	20 throttling by the hypervisor. This allows more work to get done with less 22 * Users with SSDs as swap devices can extend the life of the device by 29 Zswap is disabled by default but can be enabled at boot time by setting 53 allocation in zpool is not directly accessible by address. Rather, a handle is 54 returned by the allocation routine and that handle must be mapped before being 57 zbud is created, but it can be selected at boot time by setting the "zpool" 77 load function to decompress the page into the page allocated by the page fault 89 The default compressor is lzo, but it can be selected at boot time by setting
/linux-4.4.14/Documentation/video4linux/
D	soc-camera.txt	28 method is supported by host drivers. However, the soc-camera core also provides 76 parameters between the host and the sensor. .init_videobuf2 is called by 79 implemented completely by the specific camera host driver. If the host driver 88 Sensor drivers can use struct soc_camera_link, typically provided by the 98 soc_camera_power_off(), which switch regulators, provided by the platform and call 116 much as possible by modifying scaling factors. If the sensor window cannot be 133 factors have to be maintained by camera drivers internally. According to the 137 cropping support by the camera host driver at least the .g_crop method must be 141 soc_camera_device and used by the soc-camera core and host drivers. The core 152 maintained by soc-camera core, which describes, what FOURCC pixel format will [all …]
/linux-4.4.14/Documentation/devicetree/bindings/dma/
D	snps-dma.txt	`7 - dma-channels: Number of channels supported by hardware 9 - dma-masters: Number of AHB masters supported by the controller 15 - block_size: Maximum block size supported by the controller 16 - data_width: Maximum data width supported by hardware per AHB master 23 - is_private: The device channels should be marked as private and not for by the`
D	ste-dma40.txt	`12 - dma-channels: Number of channels supported by hardware - if not present 113 51: memcpy TX (to be used by the DMA driver for memcpy operations) 118 56: memcpy (to be used by the DMA driver for memcpy operations) 119 57: memcpy (to be used by the DMA driver for memcpy operations) 120 58: memcpy (to be used by the DMA driver for memcpy operations) 121 59: memcpy (to be used by the DMA driver for memcpy operations) 122 60: memcpy (to be used by the DMA driver for memcpy operations)`
D	dma.txt	`16 - dma-channels: Number of DMA channels supported by the controller. 17 - dma-requests: Number of DMA request signals supported by the 49 - In the node pointed by the dma-masters: 66 followed by DMA controller specific data. 71 - A number of integer cells, as determined by the 72 #dma-cells property in the node referenced by phandle`
/linux-4.4.14/Documentation/devicetree/bindings/pps/
D	pps-gpio.txt	`8 - gpios: one PPS GPIO in the format described by ../gpio/gpio.txt 11 - assert-falling-edge: when present, assert is indicated by a falling edge 12 (instead of by a rising edge)`
/linux-4.4.14/security/selinux/
D	Kconfig	`66 permissive mode (if permitted by the policy) via /selinux/enforce. 85 by the application or the protection that will be applied by the 89 by the kernel. If this option is set to 1 (one), SELinux will 90 default to checking the protection requested by the application. 93 via /selinux/checkreqprot if authorized by policy. 103 by SELinux to be set to a particular value. This value is reported 122 supported by SELinux. 129 policy format version supported by your policy toolchain, by`
/linux-4.4.14/Documentation/power/
D	pci.txt	6 management. Based on previous work by Patrick Mochel <mochel@transmeta.com> 27 In general, power management is a feature allowing one to save energy by putting 36 be signaled by the device itself. 38 PCI devices may be put into low-power states in two ways, by using the device 39 capabilities introduced by the PCI Bus Power Management Interface Specification, 45 used by the kernel to change the device's power state. 56 device (e.g. by generating interrupts). 58 In turn, if the methods provided by the platform firmware are used for changing 62 native PCI PM mechanism, because the method provided by the platform depends on 82 (B0-B3). The higher the number, the less power is drawn by the device or bus [all …]
D	opp.txt	44 is located in include/linux/pm_opp.h. OPP library can be enabled by enabling 54 OPP layer expects each domain to be represented by a unique device pointer. SoC 58 enabled by default in the system. 102 optimally- typical numbers range to be less than 5. The list generated by 103 registering the OPPs is maintained by OPP library throughout the device 107 dev_pm_opp_add - Add a new OPP for a specific domain represented by the device pointer. 112 used by SoC framework to define a optimal list as per the demands of 137 found, else returns error. These errors are expected to be handled by standard 138 error checks such as IS_ERR() and appropriate actions taken by the caller. 142 is not available by default. [all …]
/linux-4.4.14/Documentation/hid/
D	hid-transport.txt	17 and quirks are handled by all layers depending on the quirk. 64 this struct are used by HID core to communicate with the device. 80 On the other hand, synchronous channels can be implemented by the transport 98 this channel and is never acknowledged by the remote side. Devices usually 115 data is generated by the device and sent to the host with or without 145 is enforced by HID core as several transport drivers don't allow multiple 151 GET_REPORT is only used by custom HID device drivers to query device state. 157 payload may be blocked by the underlying transport driver if the 162 INPUT reports as payload might be blocked by the underlying transport driver 168 restriction is enforced by HID core as some transport drivers do not support [all …]
/linux-4.4.14/Documentation/accounting/
D	cgroupstats.txt	`1 Control Groupstats is inspired by the discussion at 3 suggested by Andrew Morton in http://lkml.org/lkml/2007/4/11/263. 8 extend per cgroup statistics, by adding members to the cgroupstats 13 user space requests for statistics by passing the cgroup path.`
/linux-4.4.14/drivers/media/v4l2-core/
D	Kconfig	`37 # Used by drivers that need tuner.ko 42 # Used by drivers that need v4l2-mem2mem.ko 47 # Used by LED subsystem flash drivers 58 # Used by drivers that need Videobuf modules 80 # Used by drivers that need Videobuf2 modules`
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
D	i2c.txt	`19 are described by a single value. This is usually a 7 bit address. However, 29 These properties may not be supported by all drivers. However, if a driver 35 - interrupts - interrupts used by the device. 36 - interrupt-names - "irq" and "wakeup" names are recognized by I2C core, 40 used by the device. I2C core will assign "irq" interrupt (or the very first`
/linux-4.4.14/drivers/leds/trigger/
D	Kconfig	`15 This allows LEDs to be controlled by a programmable timer 41 This allows LEDs to be controlled by IDE disk activity. 48 This allows LEDs to be controlled by a CPU load average. 66 This allows LEDs to be controlled by active CPUs. This shows 77 This allows LEDs to be controlled by gpio events. It's good 80 be triggered by this trigger when user slides up to show 108 This enables direct flash/torch on/off by the driver, kernel space.`
/linux-4.4.14/Documentation/parisc/
D	registers	`5 General Registers as specified by ABI 14 CR11 as specified by ABI (SAR) 58 N (Nullify next instruction) used by C code 60 B (Taken Branch) used by C code 62 V (divide step correction) used by C code 64 C/B (carry/borrow bits) used by C code 71 I (external interrupt mask) used by cli()/sti() macros 77 Shadow Registers used by interruption handler code 84 the state save and restore time by eliminating the need for general register`
/linux-4.4.14/Documentation/ABI/removed/
D	dv1394	`7 could be received by read() or transmitted by write(). A few 9 This special-purpose interface has been superseded by libraw1394 +`
/linux-4.4.14/Documentation/leds/
D	leds-lm3556.txt	`19 CONTROL REGISTER(0x09).Flash mode is activated by the ENABLE REGISTER(0x0A), 20 or by pulling the STROBE pin HIGH. 23 ON / OFF will be controlled by STROBE pin. 33 REGISTER(0x09).Torch Mode is activated by the ENABLE REGISTER(0x0A) or by the 37 and ON / OFF will be controlled by TORCH pin.`
/linux-4.4.14/arch/m68k/ifpsp060/
D	README	`10 To the maximum extent permitted by applicable law, 16 To the maximum extent permitted by applicable law, 26 No licenses are granted by implication, estoppel or otherwise under any patents 51 fskeleton.s Sample Call-outs needed by fpsp.sa and pfpsp.sa 53 iskeleton.s Sample Call-outs needed by isp.sa 55 os.s Sample Call-outs needed by fpsp.sa, pfpsp.sa, and isp.sa`
D	CHANGES	10 To the maximum extent permitted by applicable law, 16 To the maximum extent permitted by applicable law, 26 No licenses are granted by implication, estoppel or otherwise under any patents 59 requested by the package should return a failing value 95 all other bits are EQUAL TO ZERO and can be set by the _real_access() 96 "call-out" stub by the user as appropriate. The MC68060 User's Manual 117 all other bits are EQUAL TO ZERO and can be set by the _real_access() 118 "call-out" stub by the user as appropriate. The MC68060 User's Manual
D	isp.doc	10 To the maximum extent permitted by applicable law, 16 To the maximum extent permitted by applicable law, 26 No licenses are granted by implication, estoppel or otherwise under any patents 53 The hex image was created by assembling the source code and 58 assembly syntaxes by using any word processor with a global 92 by the host operating system. This section MUST be exactly 128 bytes in 94 to a function required by the ISP (these functions and their location are 100 The second section, the "Entry-point" section, is used by external routines 182 If the emulation code provided by the 060ISP is sufficient for the 184 made, by the system integrator, to point directly back into the package [all …]
D	TEST.DOC	10 To the maximum extent permitted by applicable law, 16 To the maximum extent permitted by applicable law, 26 No licenses are granted by implication, estoppel or otherwise under any patents 40 by assembling the source code and then converting the resulting 44 converted to other assembly syntaxes by using any word processor 78 by the host operating system. This section MUST be exactly 128 bytes in 80 to a function required by the test packages (these functions and their 87 The second section, the "Entry-point" section, is used by external routines 180 . # provided by system 184 . # provided by system [all …]
/linux-4.4.14/tools/perf/Documentation/
D	callchain-overhead-calculation.txt	`4 perf collects callchains. The 'self' overhead is simply calculated by 9 The 'children' overhead is calculated by adding all period values of 104 Since v3.16 the 'children' overhead is shown by default and the output 105 is sorted by its values. The 'children' overhead is disabled by 106 specifying --no-children option on the command line or by adding`
/linux-4.4.14/Documentation/block/
D	queue-sysfs.txt	20 reported by the device. A value of '0' means device does not support 27 The discard_max_bytes parameter is set by the device driver to the maximum 37 smaller discards and potentially help reduce latencies induced by large 42 When read, this file will show if the discarded block are zeroed by the 65 set by block layer which a hardware controller can handle. 71 size allowed by the hardware. 83 This is the smallest preferred IO size reported by the device. 105 regulated by nr_requests. 109 This is the optimal IO size reported by the device.
D	pr.txt	`19 by Linux. 80 reservation key for the device as acquired by the IOC_PR_REGISTER, 86 This ioctl command releases the reservation specified by key and flags 87 and thus removes any access restriction implied by it. 92 This ioctl command releases the existing reservation referred to by 100 any outstanding command sent over a connection identified by old_key.`
/linux-4.4.14/Documentation/s390/
D	CommonIO	15 The given devices will be ignored by the common I/O-layer; no detection 49 Lists the ranges of devices (by bus id) which are ignored by common I/O. 51 You can un-ignore certain or all devices by piping to /proc/cio_ignore. 69 You can also add ranges of devices to be ignored by piping to 88 The devices can be specified either by bus id (0.x.abcd) or, for 2.4 backward 89 compatibility, by the device number in hexadecimal (0xabcd or abcd). Device 108 Some views generated by the debug feature to hold various debug outputs. 122 The level of logging can be changed to be more or less verbose by piping to
/linux-4.4.14/Documentation/sh/
D	register-banks.txt	`8 bank (selected by SR.RB, only r0 ... r7 are banked), whereas other families 20 be used rather effectively as scratch registers by the kernel. 27 - Used by do_IRQ() and friends for doing irq mapping based off 31 interrupt priority level (used by local_irq_enable())`
/linux-4.4.14/Documentation/serial/
D	rocket.txt	23 RocketPort ISA and RocketModem II PCI boards currently are only supported by 26 The RocketPort ISA board requires I/O ports to be configured by the DIP 57 The RocketPort/RocketModem serial ports installed by this driver are assigned 64 manually by entering "modprobe rocket". To have the module loaded automatically 87 You must assign and configure the I/O addresses used by the ISA Rocketport 88 card before installing and using it. This is done by setting a set of DIP 105 0x2C0h, 0x300h, 0x340h, 0x380h, 0x3C0h. The I/O address used by the 118 The I/O address range used by any of the RocketPort cards must not 121 address ranges which may be in use by other devices in your system. 123 identifying what I/O addresses are being used by devices on your [all …]
/linux-4.4.14/Documentation/trace/
D	mmiotrace.txt	8 MMIO tracing was originally developed by Intel around 2003 for their Fault 18 ftrace framework by Pekka Paalanen <pq@iki.fi>. 24 Mmiotrace feature is compiled in by the CONFIG_MMIOTRACE option. Tracing is 25 disabled by default, so it is safe to have this set to yes. SMP systems are 28 activation. You can re-enable CPUs by hand, but you have been warned, there 63 During tracing you can place comments (markers) into the trace by 71 The 'cat' process exits. If it does not, kill it by issuing 'fg' command and 80 try again. Buffers are enlarged by first seeing how large the current buffers 101 Access to hardware IO-memory is gained by mapping addresses from PCI bus by 126 one line in the log. A record starts with a keyword, followed by keyword- [all …]
/linux-4.4.14/Documentation/powerpc/
D	cxl.txt	13 or CAPI. In the kernel it's referred to by the name CXL to avoid 39 by Linux by calls into OPAL. Linux doesn't directly program the 66 There are two programming modes supported by the AFU. Dedicated 79 operation, the ID can also be accessed by the kernel so it can 97 are received by the kernel as hardware interrupts and passed onto 98 userspace by a read syscall documented below. 100 Data storage faults and error interrupts are handled by the kernel 158 supports 2040 IRQs and 3 are used by the kernel, so 2037 are 197 defined by the AFU. Typically this is an effective 203 AMR. This field is only used by the kernel when the [all …]
D	cxlflash.txt	15 devices as a PCI device by implementing a virtual PCI host bridge. 20 CXL provides a mechanism by which user space applications can 46 by special translation services provided by the Flash AFU. 53 granted to it by the kernel or hypervisor allowing it to perform AFU 85 written to a specification provided by the block library may get 99 block device (/dev/sdb) may be opened directly by the block library 116 implemented as IOCTLs, that are provided by the cxlflash driver 132 by the cxlflash driver. As these services are implemented as ioctls, 135 descriptor is obtained by opening the device special file associated 138 SCSI protocol stack, this open is actually not seen by the cxlflash [all …]
D	transactional_memory.txt	5 its use by user programs. It is not currently used by the kernel itself. 7 This file aims to sum up how it is supported by Linux and what behaviour you 56 If, in the meantime, there is a conflict with the locations accessed by the 57 transaction, the transaction will be aborted by the CPU. Register and memory 68 - Conflicts with cache lines used by other processors 78 transaction will be doomed by the kernel with the failure code TM_CAUSE_SYSCALL 82 the transaction is not explicitly doomed by the kernel. However, what the 84 by the hardware. The syscall is performed in suspended mode so any side 86 guarantees are provided by the kernel about which syscalls will affect 171 Failure cause codes used by kernel [all …]
D	bootwrapper.txt	6 a boot wrapper to make it usable by the system firmware. There is no 43 inside the image instead of provided by firmware. The 56 can be overridden by the wrapper script. 87 uImage: Native image format used by U-Boot. The uImage target 95 Used by OpenFirmware and other firmware interfaces 111 targets build all the default images as selected by the kernel configuration. 112 Default images are selected by the boot wrapper Makefile 113 (arch/powerpc/boot/Makefile) by adding targets to the $image-y variable. Look 128 The wrapper is adapted for different image types at link time by linking in 130 script' (found in arch/powerpc/boot/wrapper) is called by the Makefile and [all …]
/linux-4.4.14/arch/x86/boot/
D	header.S	`137 # Filled in by build.c 143 # Filled in by build.c 200 # The offset & size fields are filled in by build.c. 219 # offset & size fields are filled in by build.c. 235 # The offset & size fields are filled in by build.c. 253 # The offset & size fields are filled in by build.c. 273 # Kernel attributes; used by setup. This is part 1 of the`
/linux-4.4.14/lib/fonts/
D	Kconfig	`29 provided by the text console 80x50 (and higher) modes). 34 Given the resolution provided by the frame buffer device, answer N 42 provided by the VGA text console 80x25 mode. 47 bool "Mac console 6x11 font (not supported by all drivers)" if FONTS 55 bool "console 7x14 font (not supported by all drivers)" if FONTS 97 bool "Sparc console 12x22 font (not supported by all drivers)" 105 bool "console 10x18 font (not supported by all drivers)" if FONTS`
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
D	msi.txt	4 Message Signaled Interrupts (MSIs) are a class of interrupts generated by a 7 MSIs were originally specified by PCI (and are used with PCIe), but may also be 12 MSIs are distinguished by some combination of: 16 Devices may be configured by software to write to arbitrary doorbells which 21 Devices may be configured to write an arbitrary payload chosen by software. 35 address by some master. An MSI controller may feature a number of doorbells. 50 The meaning of the msi-specifier is defined by the device tree binding of
/linux-4.4.14/tools/perf/config/
D	utilities.mak	50 # in an `awk' program that is delimited by shell 67 # delimited by shell single-quotes, so be wary 72 # overcome by putting a space between `{' and `gsub'). 83 # embedding in a shell string that is delimited by 108 # At least GNU make gets confused by expanding a newline 113 # This function avoids the problem by producing a string 141 # (It's necessary to use `sh -c' because GNU make messes up by 151 # (It's necessary to use `sh -c' because GNU make messes up by 163 # the `command -v' is defined by POSIX, but it's not 166 # by the presence of a leading `/'.
/linux-4.4.14/Documentation/gpio/
D	drivers-on-gpio.txt	21 by a timer. 24 up to three buttons by simply using GPIOs and no mouse port. You can cut the 41 system by pulling a GPIO line and will register a restart handler so 45 by pulling a GPIO line and will register a pm_power_off() callback so that 52 (two wires, SDA and SCL lines) by hammering (bitbang) two GPIO lines. It will 61 to this SPI by using the mmc_spi host from the MMC/SD card subsystem. 73 regulator providing a certain voltage by pulling a GPIO line, integrating 77 that will periodically "ping" a hardware connected to a GPIO line by toggling 88 to emulate MCTRL (modem control) signals CTS/RTS by using two GPIO lines. The 95 embedded hacking in particular by providing ready-made components.
/linux-4.4.14/Documentation/usb/
D	error-codes.txt	6 Some of them are returned by the Host Controller Drivers (HCDs), which 13 * Error codes returned by usb_submit_urb * 68 * Error codes returned by in urb->status * 90 -ENOENT URB was synchronously unlinked by usb_unlink_urb 108 error, a failure to respond (often caused by 117 completed, and no other error was reported by HC. 130 -EOVERFLOW () The amount of data returned by the endpoint was 138 -ENODEV Device was removed. Often preceded by a burst of 147 -ECONNRESET URB was asynchronously unlinked by usb_unlink_urb 165 Error codes returned by usbcore-functions *
/linux-4.4.14/net/ax25/
D	TODO	`9 Routes to a device being taken down might be deleted by ax25_rt_device_down 10 but added by somebody else before the device has been deleted fully. 13 the race caused by the static variable in it's previous implementation.`
/linux-4.4.14/fs/notify/fanotify/
D	Kconfig	`21 decisions concerning filesystem events. This is used by some fanotify 23 use those files. This is used by some anti-malware vendors and by some`
/linux-4.4.14/arch/sh/lib64/
D	memset.S	`6 ! by Toshiyasu Morita (tm@netcom.com) 8 ! SH5 code by J"orn Rennecke (joern.rennecke@superh.com)`
/linux-4.4.14/Documentation/video4linux/bttv/
D	PROBLEMS	`1 - Start capturing by pressing "c" or by selecting it via a menu! 3 - Start capturing by pressing "c" or by selecting it via a menu!!! 12 If it is different to the address found by bttv install bttv like this: 51 Disable backing store by starting X with the option "-bs"`
D	Insmod-options	44 push used by bttv. bttv will disable overlay 45 by default on this hardware to avoid crashes. 47 no_overlay=1 Disable overlay. It should be used by broken 51 no TV signal, on by default. You might try 55 chroma_agc=0/1 AGC of chroma signal, off by default. 56 adc_crush=0/1 Luminance ADC crush, on by default. 59 maximum supported speed by kernel bitbang 92 tda9855 = 1 therefore off by default, if you have 118 Note 2: tda9874h/a and tda9875 (which is supported separately by 141 for dbx stereo. Default is on if supported by
/linux-4.4.14/Documentation/devicetree/bindings/arm/
D	psci.txt	`5 processors") can be used by Linux to initiate various CPU-centric power 11 Functions are invoked by trapping to the privilege level of the PSCI 13 in a manner similar to that specified by AAPCS: 30 IDs are not required and should be ignored by an OS with PSCI 0.2 90 A DTB may provide IDs for use by kernels without PSCI 0.2 support, 92 These IDs will be ignored by kernels with PSCI 0.2 support, which will`
/linux-4.4.14/Documentation/devicetree/bindings/media/xilinx/
D	video.txt	`4 Xilinx video IP cores process video streams by acting as video sinks and/or 5 sources. They are connected by links through their input and output ports, 8 Each video IP core is represented by an AMBA bus child node in the device 12 The whole pipeline is represented by an AMBA bus child node in the device`
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
D	ti-omap.txt	`7 by mmc.txt and the properties used by the omap mmc driver. 34 by mmc.txt and the properties used by the omap mmc driver.`
/linux-4.4.14/fs/jffs2/
D	LICENCE	`7 the terms of the GNU General Public License as published by the Free 23 files, these files do not by themselves cause the resulting work to be 24 covered by the GNU General Public License. However the source code for 29 this file might be covered by the GNU General Public License.`
/linux-4.4.14/Documentation/acpi/
D	scan_handlers.txt	11 layout (i.e. parent device objects in the namespace are represented by parent 14 should not be confused with struct device_node objects used by the Device Trees 22 information from the device objects represented by them and populating them with 31 component represented by the given device node which can be determined on the 32 basis of the device node's hardware ID (HID). They are performed by objects 33 called ACPI scan handlers represented by the following structure: 44 maintained by the ACPI core and the .attach() and .detach() callbacks are 70 ACPI scan handlers can be added to the list maintained by the ACPI core with the
/linux-4.4.14/Documentation/devicetree/bindings/display/armada/
D	marvell,dove-lcd.txt	`7 - port: video output port with endpoints, as described by graph.txt 11 - clocks: as described by clock-bindings.txt 12 - clock-names: as described by clock-bindings.txt`
/linux-4.4.14/Documentation/arm64/
D	booting.txt	7 This document is based on the ARM booting document by Russell King and 62 therefore requires decompression (gzip etc.) to be performed by the boot 115 memory as possible free for use by the kernel immediately after the 121 below that base address is currently unusable by Linux, and therefore it 127 use by the kernel. 137 corrupted by bogus network packets or disk data. This will save 158 cache maintenance by VA rather than set/way operations. 159 System caches which respect the architected cache maintenance by VA 161 System caches which do not respect architected cache maintenance by VA 171 All CPUs to be booted by the kernel must be part of the same coherency [all …]
/linux-4.4.14/Documentation/mn10300/
D	compartmentalisation.txt	`19 The appropriate processor is selected by a CONFIG_MN10300_PROC_YYYY option 26 controlled by that processor. 42 The appropriate processor is selected by a CONFIG_MN10300_UNIT_ZZZZ option 59 The appropriate arch/mn10300/unit-ZZZZ directory will also be entered by the`
/linux-4.4.14/Documentation/misc-devices/
D	ad525x_dpot.txt	`8 interpretation of this settings is required by the end application according to 23 and may vary greatly on a part-by-part basis. For exact interpretation of 31 Locate the device in your sysfs tree. This is probably easiest by going into 32 the common i2c directory and locating the device by the i2c slave address.`
/linux-4.4.14/
D	COPYING	3 services by normal system calls - this is merely considered normal use 5 Also note that the GPL below is copyrighted by the Free Software 7 kernel) is copyrighted by me and others who actually wrote it. 33 using it. (Some other Free Software Foundation software is covered by 61 software. If the software is modified by someone else and passed on, we 63 that any problems introduced by others will not reflect on the original 66 Finally, any free program is threatened constantly by software 79 a notice placed by the copyright holder saying it may be distributed 89 covered by this License; they are outside its scope. The act of 92 Program (independent of having been made by running the Program). [all …]
/linux-4.4.14/drivers/block/paride/
D	Transition-notes	7 Consider the sequnce of these events. A can not be preceded by 9 ps_spinlock. C is always preceded by B, since we can't reach it 14 A and each B is preceded by either A or C. Moments when we enter 51 2) When there is such a thread, pd_busy is set or pd_lock is held by 54 held by that thread. 56 ->claim_cont or pi_spinlock is held by thread in question. 67 c) pi_do_claimed() is called by pd.c only from the area. 81 (2) can become not true only when pd_lock is released by the thread in question. 93 by the thread in question. However, all such places within the area are right 113 that the only possible contention is between scheduling ps_tq followed by [all …]
/linux-4.4.14/drivers/usb/core/
D	Kconfig	`10 usually used by distro vendors to help with debugging and to 20 bool "Enable USB persist by default" 24 enabled by default. If you say N it will make suspended USB 51 or a host. The initial role is decided by the type of 64 rejected during enumeration. This behavior is required by the 75 and software costs by not supporting external hubs. So 96 The ULPI interfaces (the buses) are registered by the drivers for USB`
/linux-4.4.14/Documentation/RCU/
D	NMI-RCU.txt	`11 The relevant pieces of code are listed below, each followed by a 57 given that the code referenced by the pointer is read-only? 68 data that is to be used by the callback must be initialized up -before- 81 up any data structures used by the old NMI handler until execution 104 that the code referenced by the pointer is read-only? 107 initialized some data that is to be used by the new NMI 120 being protected by RCU-sched.`
/linux-4.4.14/drivers/staging/unisys/Documentation/ABI/
D	sysfs-platform-visorchipset	`57 Description: This entry is used by Unisys application software on the guest 71 Description: This entry is used by a Unisys support script installed on the 72 guest, and triggered by a udev event. The support script is 78 situation by sending a message to guests using these VFs, and 90 Description: This entry is used by a Unisys support script installed on the 91 guest, and triggered by a udev event. The support script is 97 situation by sending a message to guests using these VFs, and`
/linux-4.4.14/drivers/firmware/efi/
D	Kconfig	`33 else supported by pstore to EFI variables. 36 bool "Disable using efivars as a pstore backend by default" 41 backend for pstore by default. This setting can be overridden 50 That memory map is used for example by kexec to set up efi virtual 62 to specific memory range by updating original (firmware provided)`
/linux-4.4.14/fs/reiserfs/
D	README	6 Source code files that contain the phrase "licensing governed by 8 files are licensed under the GPL. The portions of them owned by Hans 9 Reiser, or authorized to be licensed by him, have been in the past, 12 want it to be owned by Hans Reiser, put your copyright label on that 14 All portions of governed files not labeled otherwise are owned by Hans 15 Reiser, and by adding your code to it, widely distributing it to 17 licensing is governed by the statement in this file, you accept this. 19 to license code labeled as owned by you on your behalf other than 72 building, by buying from third party OS component suppliers. Leverage 77 be the ones to compete against the entire internet by themselves. Be [all …]
/linux-4.4.14/Documentation/devicetree/bindings/bus/
D	ti-gpmc.txt	`31 of the per-CS register GPMC_CONFIG7 (as set up by the 72 - gpmc,adv-extra-delay: ADV signal is delayed by half GPMC clock 73 - gpmc,cs-extra-delay: CS signal is delayed by half GPMC clock 78 - gpmc,oe-extra-delay: OE signal is delayed by half GPMC clock 79 - gpmc,we-extra-delay: WE signal is delayed by half GPMC clock 80 - gpmc,time-para-granularity: Multiply all access times by 2 86 to the GPMC_CLK rising edge used by the 110 - gpmc,wait-pin Wait-pin used by client. Must be less than`
/linux-4.4.14/Documentation/devicetree/bindings/pwm/
D	renesas,tpu-pwm.txt	`12 - reg: Base address and length of each memory resource used by the PWM 16 the cells format. The only third cell flag supported by this binding is 20 used by client devices.`
/linux-4.4.14/arch/mn10300/kernel/
D	mn10300-serial-low.S	`6 # Written by David Howells (dhowells@redhat.com) 10 # as published by the Free Software Foundation; either version 37 # - intended to run at interrupt priority 1 (not affected by local_irq_disable) 42 # or EPSW_IE,psw # permit overriding by 60 # - intended to run at interrupt priority 1 (not affected by local_irq_disable) 107 # - intended to run at interrupt priority 1 (not affected by local_irq_disable)`

12 3 4 5 6 7 8 9 10 >>...21

Project(s)

Full Search
Definition
Symbol
File Path
History
Type