| /linux-4.4.14/fs/nfs/blocklayout/ |
| D | extent_tree.c | 25 ext_tree_prev(struct pnfs_block_extent *be) in ext_tree_prev() argument
27 struct rb_node *node = rb_prev(&be->be_node); in ext_tree_prev()
32 ext_tree_next(struct pnfs_block_extent *be) in ext_tree_next() argument
34 struct rb_node *node = rb_next(&be->be_node); in ext_tree_next()
39 ext_f_end(struct pnfs_block_extent *be) in ext_f_end() argument
41 return be->be_f_offset + be->be_length; in ext_f_end()
48 struct pnfs_block_extent *be = NULL; in __ext_tree_search() local
51 be = ext_node(node); in __ext_tree_search()
52 if (start < be->be_f_offset) in __ext_tree_search()
54 else if (start >= ext_f_end(be)) in __ext_tree_search()
[all …]
|
| D | blocklayout.c | 52 static bool is_hole(struct pnfs_block_extent *be) in is_hole() argument
54 switch (be->be_state) { in is_hole()
58 return be->be_tag ? false : true; in is_hole()
142 struct pnfs_block_extent *be, bio_end_io_t end_io, in do_add_page_to_bio() argument
146 container_of(be->be_device, struct pnfs_block_dev, node); in do_add_page_to_bio()
153 isect += be->be_v_offset; in do_add_page_to_bio()
154 isect -= be->be_f_offset; in do_add_page_to_bio()
227 struct pnfs_block_extent be; in bl_read_pagelist() local
258 if (!ext_tree_lookup(bl, isect, &be, false)) { in bl_read_pagelist()
262 extent_length = be.be_length - (isect - be.be_f_offset); in bl_read_pagelist()
[all …]
|
| /linux-4.4.14/drivers/net/xen-netback/ |
| D | xenbus.c | 41 static int connect_rings(struct backend_info *be, struct xenvif_queue *queue);
42 static void connect(struct backend_info *be);
43 static int read_xenbus_vif_flags(struct backend_info *be);
44 static int backend_create_xenvif(struct backend_info *be);
45 static void unregister_hotplug_status_watch(struct backend_info *be);
47 static void set_backend_state(struct backend_info *be,
231 struct backend_info *be = dev_get_drvdata(&dev->dev); in netback_remove() local
233 set_backend_state(be, XenbusStateClosed); in netback_remove()
235 unregister_hotplug_status_watch(be); in netback_remove()
236 if (be->vif) { in netback_remove()
[all …]
|
| /linux-4.4.14/drivers/block/xen-blkback/ |
| D | xenbus.c | 47 struct xenbus_device *xen_blkbk_xenbus(struct backend_info *be) in xen_blkbk_xenbus() argument
49 return be->dev; in xen_blkbk_xenbus()
67 struct xenbus_device *dev = blkif->be->dev; in blkback_name()
95 if (blkif->be->dev->state == XenbusStateConnected) in xen_update_blkif_status()
99 connect(blkif->be); in xen_update_blkif_status()
100 if (blkif->be->dev->state != XenbusStateConnected) in xen_update_blkif_status()
105 xenbus_dev_error(blkif->be->dev, err, "get blkback dev name"); in xen_update_blkif_status()
111 xenbus_dev_error(blkif->be->dev, err, "block flush"); in xen_update_blkif_status()
120 xenbus_dev_error(blkif->be->dev, err, "start xenblkd"); in xen_update_blkif_status()
169 err = xenbus_map_ring_valloc(blkif->be->dev, gref, nr_grefs, in xen_blkif_map()
[all …]
|
| /linux-4.4.14/sound/soc/ |
| D | soc-pcm.c | 179 struct snd_soc_pcm_runtime *be = dpcm->be; in dpcm_dapm_stream_event() local
181 dev_dbg(be->dev, "ASoC: BE %s event %d dir %d\n", in dpcm_dapm_stream_event()
182 be->dai_link->name, event, dir); in dpcm_dapm_stream_event()
184 snd_soc_dapm_stream_event(be, dir, event); in dpcm_dapm_stream_event()
1121 struct snd_soc_pcm_runtime *be, int stream) in dpcm_be_connect() argument
1127 if (dpcm->be == be && dpcm->fe == fe) in dpcm_be_connect()
1135 dpcm->be = be; in dpcm_be_connect()
1137 be->dpcm[stream].runtime = fe->dpcm[stream].runtime; in dpcm_be_connect()
1140 list_add(&dpcm->list_fe, &be->dpcm[stream].fe_clients); in dpcm_be_connect()
1144 stream ? "<-" : "->", be->dai_link->name); in dpcm_be_connect()
[all …]
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | watchdog-parameters.txt | 3 be listed here unless the driver has its own driver-specific information
16 nowayout: Watchdog cannot be stopped once started
23 nowayout: Watchdog cannot be stopped once started
28 nowayout: Watchdog cannot be stopped once started
35 nowayout: Watchdog cannot be stopped once started
44 timeout: Timeout value. Limited to be 1 or 2 seconds. (default=2)
45 nowayout: Watchdog cannot be stopped once started
50 nowayout: Watchdog cannot be stopped once started
55 nowayout: Watchdog cannot be stopped once started
60 nowayout: Watchdog cannot be stopped once started
[all …]
|
| /linux-4.4.14/drivers/hwmon/ |
| D | Kconfig | 22 This support can also be built as a module. If so, the module
23 will be called hwmon.
52 This driver can also be built as a module. If so, the module
53 will be called abx500-temp.
62 chip can be found on Abit uGuru featuring motherboards (most modern
67 This driver can also be built as a module. If so, the module
68 will be called abituguru.
77 uGuru chip can be found on recent Abit motherboards (since end
81 This driver can also be built as a module. If so, the module
82 will be called abituguru3.
[all …]
|
| /linux-4.4.14/drivers/i2c/busses/ |
| D | Kconfig | 15 If you say yes to this option, support will be included for the SMB
20 This driver can also be built as a module. If so, the module
21 will be called i2c-ali1535.
27 If you say yes to this option, support will be included for the SMB
32 This driver can also be built as a module. If so, the module
33 will be called i2c-ali1563.
39 If you say yes to this option, support will be included for the
42 This driver can also be built as a module. If so, the module
43 will be called i2c-ali15x3.
49 If you say yes to this option, support will be included for the AMD
[all …]
|
| /linux-4.4.14/drivers/hwmon/pmbus/ |
| D | Kconfig | 12 This driver can also be built as a module. If so, the module will
13 be called pmbus_core.
26 This driver can also be built as a module. If so, the module will
27 be called pmbus.
37 This driver can also be built as a module. If so, the module will
38 be called adm1275.
47 This driver can also be built as a module. If so, the module will
48 be called lm25066.
58 This driver can also be built as a module. If so, the module will
59 be called ltc2978.
[all …]
|
| /linux-4.4.14/drivers/rtc/ |
| D | Kconfig | 15 be allowed to plug one or more RTCs to your system. You will
24 If you say yes here, the system time (wall clock) will be set using
33 The RTC device that will be used to (re)initialize the system
39 The driver for this RTC device must be loaded before late_initcall
40 functions run, so it must usually be statically linked.
42 This clock should be battery-backed, so that it reads the correct
47 be useful to reinitialize system time when resuming from system
55 If you say yes here, the system time (wall clock) will be stored
95 Other RTCs will not be available through that API.
110 can be accessed as /dev/rtc, which is a name
[all …]
|
| /linux-4.4.14/drivers/i2c/muxes/ |
| D | Kconfig | 13 If you say yes to this option, support will be included for an
18 This driver can also be built as a module. If so, the module
19 will be called i2c-arb-gpio-challenge.
25 If you say yes to this option, support will be included for a
30 This driver can also be built as a module. If so, the module
31 will be called i2c-mux-gpio.
39 This driver can also be built as a module. If so, the module
40 will be called i2c-mux-pca9541.
49 This driver can also be built as a module. If so, the module
50 will be called i2c-mux-pca954x.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
| D | l4.txt | 6 - compatible : Should be "ti,omap2-l4" for OMAP2 family l4 core bus
7 Should be "ti,omap2-l4-wkup" for OMAP2 family l4 wkup bus
8 Should be "ti,omap3-l4-core" for OMAP3 family l4 core bus
9 Should be "ti,omap4-l4-cfg" for OMAP4 family l4 cfg bus
10 Should be "ti,omap4-l4-wkup" for OMAP4 family l4 wkup bus
11 Should be "ti,omap5-l4-cfg" for OMAP5 family l4 cfg bus
12 Should be "ti,omap5-l4-wkup" for OMAP5 family l4 wkup bus
13 Should be "ti,dra7-l4-cfg" for DRA7 family l4 cfg bus
14 Should be "ti,dra7-l4-wkup" for DRA7 family l4 wkup bus
15 Should be "ti,am3-l4-wkup" for AM33xx family l4 wkup bus
[all …]
|
| D | l3-noc.txt | 7 - compatible : Should be "ti,omap3-l3-smx" for OMAP3 family
8 Should be "ti,omap4-l3-noc" for OMAP4 family
9 Should be "ti,omap5-l3-noc" for OMAP5 family
10 Should be "ti,dra7-l3-noc" for DRA7 family
11 Should be "ti,am4372-l3-noc" for AM43 family
|
| /linux-4.4.14/drivers/uwb/ |
| D | beacon.c | 168 kfree(bce->be); in uwb_bce_kfree()
265 struct uwb_rc_evt_beacon *be, in __uwb_beca_add() argument
314 static void uwb_beacon_print(struct uwb_rc *rc, struct uwb_rc_evt_beacon *be, in uwb_beacon_print() argument
326 devbuf, dstbuf, be->bChannelNumber, be->wBPSTOffset, in uwb_beacon_print()
337 struct uwb_rc_evt_beacon *be; in uwb_bce_print_IEs() local
344 be = bce->be; in uwb_bce_print_IEs()
345 if (be) { in uwb_bce_print_IEs()
346 bf = (struct uwb_beacon_frame *)bce->be->BeaconInfo; in uwb_bce_print_IEs()
347 ies_len = be->wBeaconInfoLength - sizeof(struct uwb_beacon_frame); in uwb_bce_print_IEs()
362 struct uwb_rc_evt_beacon *be) in uwb_verify_beacon() argument
[all …]
|
| /linux-4.4.14/drivers/char/tpm/ |
| D | Kconfig | 12 say Yes and it will be accessible from within Linux. For
15 userspace enablement piece of the specification, can be
18 will be called tpm. If unsure, say N.
22 2) Without ACPI enabled, the BIOS event log won't be accessible,
33 specification (TPM2.0) say Yes and it will be accessible from
35 the module will be called tpm_tis.
41 If you have an Atmel I2C TPM security chip say Yes and it will be
44 be called tpm_tis_i2c_atmel.
52 Specification 0.20 say Yes and it will be accessible from within
55 will be called tpm_i2c_infineon.
[all …]
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 58 This first two fields should be filled in before registration, and the third
59 will be filled in by the registration function; any other fields should just be
67 entire in-cache hierarchy for this netfs will be scrapped and begun
70 (3) The cookie representing the primary index will be allocated according to
105 (1) Any index containing non-index objects should be restricted to a single
106 cache. Any such objects created within an index will be created in the
107 first cache only. The cache in which an index is created can be
110 (2) The entry data must be atomically journallable, so it is limited to about
111 400 bytes at present. At least 400 bytes will be available.
113 (3) The depth of the index tree should be judged with care as the search
[all …]
|
| D | backend-api.txt | 5 The FS-Cache system provides an API by which actual caches can be supplied to
16 To start off, a cache definition must be initialised and registered for each
20 The cache definition (struct fscache_cache) should be initialised by calling:
38 The cache should then be registered with FS-Cache by passing a pointer to the
45 Two extra arguments should also be supplied:
48 master index in this cache. Netfs primary index entries will be created
52 (*) "tagname" which, if given, should be a text string naming this cache. If
53 this is NULL, the identifier will be used instead. For CacheFS, the
54 identifier is set to name the underlying block device and the tag can be
58 is already in use. 0 will be returned on success.
[all …]
|
| D | operations.txt | 29 This facility is available to and expected to be be used by the cache backends,
33 To make use of this facility, <linux/fscache-cache.h> should be #included.
58 with the operation to be initialised and the release function to use.
60 The op->flags parameter should be set to indicate the CPU time provision and
63 The op->fast_work, op->slow_work and op->processor flags should be set as
66 FSCACHE_OP_WAITING may be set in op->flags prior to each submission of the
74 There are a number of parameters that can be set in the operation record's flag
78 (1) The operation may be done synchronously (FSCACHE_OP_MYTHREAD). A thread
88 If this option is to be used, FSCACHE_OP_WAITING must be set in op->flags
90 to be cleared before proceeding:
[all …]
|
| /linux-4.4.14/Documentation/arm64/ |
| D | acpi_object_usage.txt | 29 Must be supplied if RAS support is provided by the platform. It
30 is recommended this table be supplied.
34 Microsoft only table, will not be supported.
53 Microsoft only table, will not be supported.
57 Microsoft only table, will not be supported.
69 x86 only table, will not be supported.
77 Optional, not currently supported, but could be used on ARM if and
80 need to be modified in the ACPI specification.
86 if it had actually occurred. However, this table should not be
87 shipped with a production system; it should be dynamically loaded
[all …]
|
| D | booting.txt | 18 hypervisor code, or it may just be a handful of instructions for
48 The device tree blob (dtb) must be placed on an 8-byte boundary and must
49 not exceed 2 megabytes in size. Since the dtb will be mapped cacheable
50 using blocks of up to 2 megabytes in size, it must not be placed within
51 any 2M region which must be mapped with any specific attributes.
53 NOTE: versions prior to v4.2 also require that the DTB be placed within
62 therefore requires decompression (gzip etc.) to be performed by the boot
101 little-endian and must be respected. Where image_size is zero,
102 text_offset can be assumed to be 0x80000.
119 The Image must be placed text_offset bytes from a 2MB aligned base
[all …]
|
| D | arm-acpi.txt | 3 ACPI can be used for ARMv8 general purpose servers designed to follow
6 can be retrieved simply by visiting [1], but the SBSA is currently only
13 by the specification can be found via http://www.uefi.org/acpi.
16 or cannot be described using the mechanisms defined in the required ACPI
17 specifications, then ACPI may not be a good fit for the hardware.
33 of the summary text almost directly, to be honest.
48 Such bindings could be defined in DT at some point, but doing so means ARM
53 and an OS is important. Hardware vendors would not be required to implement
67 responsibility for hardware behaviour cannot solely be the domain of the
68 kernel, but rather must be split between the platform and the kernel, in
[all …]
|
| /linux-4.4.14/Documentation/arm/ |
| D | Setup | 9 kernel loader to the Linux kernel proper, and may be short lived
11 should not be referenced outside of arch/arm/kernel/setup.c:setup_arch().
18 This parameter must be set to the page size of the machine, and
19 will be checked by the kernel.
32 This is now obsolete, and should not be used.
50 or VGA console character size. They should not be used for any other
53 It's generally a good idea to set these to be either standard VGA, or
55 all the bootup messages to be displayed correctly.
61 is otherwise unused. (should not be used for other console types, and
62 should not be used for other purposes).
[all …]
|
| D | Porting | 18 virtual or physical addresses here, since the MMU will be off at
21 to be located in RAM, it can be in flash or other read-only or
26 This must be pointing at RAM. The decompressor will zero initialise
27 this for you. Again, the MMU will be off.
30 This is the address where the decompressed kernel will be written,
31 and eventually executed. The following constraint must be valid:
35 The initial part of the kernel is carefully coded to be position
45 must be valid:
62 boot phase, virtual address PAGE_OFFSET will be mapped to physical
64 This should be the same value as TASK_SIZE.
[all …]
|
| D | Booting | 66 The boot loader must ultimately be able to provide a MACH_TYPE_xxx
68 should be passed to the kernel in register r1.
70 For DT-only platforms, the machine type will be determined by device
89 The ATAG_CORE tag may or may not be empty. An empty ATAG_CORE tag
93 Any number of tags can be placed in the list. It is undefined
110 The tagged list should be stored in system RAM.
112 The tagged list must be placed in a region of memory where neither
127 system memory, and the root filesystem location. The dtb must be
129 overwrite it, whilst remaining within the region which will be covered
140 If an initramfs is in use then, as with the dtb, it must be placed in
[all …]
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | review-checklist.txt | 7 2. Patches should be against kvm.git master branch.
10 - the API must be documented in Documentation/virtual/kvm/api.txt
11 - the API must be discoverable using KVM_CHECK_EXTENSION
18 6. New cpu features should be exposed via KVM_GET_SUPPORTED_CPUID2
20 7. Emulator changes should be accompanied by unit tests for qemu-kvm.git
23 8. Changes should be vendor neutral when possible. Changes to common code
29 10. User/kernel interfaces and guest/host interfaces must be 64-bit clean
33 11. New guest visible features must either be documented in a hardware manual
34 or be accompanied by documentation.
36 12. Features must be robust against reset and kexec - for example, shared
[all …]
|
| D | msr.txt | 18 data: 4-byte alignment physical address of a memory area which must be
28 whose data will be filled in by the hypervisor. The hypervisor is only
42 MSR_KVM_SYSTEM_TIME_NEW needs to be added.
47 Availability of this MSR must be checked via bit 3 in 0x4000001 cpuid
52 data: 4-byte aligned physical address of a memory area which must be in
67 whose data will be filled in by the hypervisor periodically. Only one
88 tsc_to_system_mul: multiplier to be used when converting
91 tsc_shift: shift to be used when converting tsc-related
111 of specific flags has to be checked in 0x40000001 cpuid leaf.
118 | | be monotonic
[all …]
|
| D | locking.txt | 7 (to be written)
15 the mmu-lock on x86. Currently, the page fault can be fast only if the
28 is safe because whenever changing these bits can be detected by cmpxchg.
32 The mapping from gfn to pfn may be changed since we can only ensure the pfn
64 - We have held the refcount of pfn that means the pfn can not be freed and
65 be reused for another gfn.
66 - The pfn is writable that means it can not be shared between different gfns
75 In the origin code, the spte can be fast updated (non-atomically) if the
77 Accessed bit and Dirty bit can not be lost.
79 But it is not true after fast page fault since the spte can be marked
[all …]
|
| /linux-4.4.14/arch/sparc/lib/ |
| D | strncmp_32.S | 26 be 8f
30 be,a 1f
42 be 8f
46 be,a 1f
58 be 8f
62 be,a 1f
74 be 8f
78 be 1f
99 be 8f
103 be 7f
|
| D | memscan_64.S | 21 be,pt %icc, we_are_aligned
28 be,pn %xcc, szzero
58 be,pn %icc, 1f
62 be,pn %icc, 1f
67 be,pn %icc, 1f
71 be,pn %icc, 1f
75 be,a,pn %icc, 2f
79 be,pn %icc, 1f
84 be,pn %icc, 1f
88 be,pn %icc, 1f
[all …]
|
| D | strlen.S | 18 BRANCH32(be, pt, 9f)
24 BRANCH32(be, pn, 4f)
30 BRANCH32(be, pt, 5f)
48 BRANCH32(be, pt, 8b)
54 BRANCH32(be, pn, 1f)
58 BRANCH32(be, pn, 1f)
62 BRANCH32(be, pn, 1f)
|
| D | memset.S | 80 be 2f
84 be 2f
106 be 2f
114 be 9f
127 be 13f
140 be 8f
143 be 1f
149 be 1f
161 be 13b
164 be 0f
[all …]
|
| D | U3memcpy.S | 97 be,pn %XCC, 85f
114 be,pt %XCC, 2f
125 be,pt %icc, 2f
138 be,pt %icc, 3f
147 be,pn %icc, 3f
236 be,pt %XCC, 1f
255 be,pn %XCC, 2f
257 be,pn %XCC, 2f
261 be,a,pt %XCC, 1f
269 be,pn %XCC, 2f
[all …]
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | user_mad.txt | 12 A MAD agent can be created by filling in a struct ib_user_mad_reg_req
15 request succeeds, a 32-bit id will be returned in the structure.
25 Agents can be unregistered with the IB_USER_MAD_UNREGISTER_AGENT
27 be unregistered when the descriptor is closed.
30 fields to be provided during registration.
37 RMPP. The buffer passed to read() must be at least one
69 fields will be filled in with information on the received MAD. For
70 example, the remote LID will be in mad.lid.
72 If a send times out, a receive will be generated with mad.status set
74 mad.status will be 0.
[all …]
|
| /linux-4.4.14/drivers/nvmem/ |
| D | Kconfig | 10 This driver can also be built as a module. If so, the module
11 will be called nvmem_core.
25 This driver can also be built as a module. If so, the module
26 will be called nvmem-imx-ocotp.
36 This driver can also be built as a module. If so, the module
37 will be called nvmem-mxs-ocotp.
47 This driver can also be built as a module. If so, the module
48 will be called nvmem_qfprom.
57 This driver can also be built as a module. If so, the module
58 will be called nvmem_rockchip_efuse.
[all …]
|
| /linux-4.4.14/Documentation/security/ |
| D | keys.txt | 6 user mappings, and similar to be cached in the kernel for the use of
13 The key service can be configured on by enabling:
57 (*) Each key is of a defined "type". Types must be registered inside the
59 can be added or used. Userspace programs cannot define new types directly.
62 number of operations that can be performed on a key of that type.
64 Should a type be removed from the system, all the keys of that type will
65 be invalidated.
67 (*) Each key has a description. This should be a printable string. The key
73 whether a kernel service will be able to find the key.
75 (*) Each key can be set to expire at a specific time by the key type's
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | at91-clock.txt | 8 - compatible : shall be one of the following:
25 All at91 specific clocks (clocks defined below) must be child
85 - #size-cells : shall be 0 (reg is used to encode clk id).
86 - #address-cells : shall be 1 (reg is used to encode clk id).
101 - #clock-cells : from common clock binding; shall be set to 0.
115 - #clock-cells : from common clock binding; shall be set to 0.
130 - #clock-cells : from common clock binding; shall be set to 0.
142 - #size-cells : shall be 0 (reg is used to encode clk id).
143 - #address-cells : shall be 1 (reg is used to encode clk id).
144 - interrupts : shall be set to PMC interrupt line.
[all …]
|
| D | vt8500.txt | 8 - compatible : shall be one of the following:
16 - reg : shall be the control register offset from PMC base for the pll clock.
17 - clocks : shall be the input parent clock phandle for the clock. This should
18 be the reference clock.
19 - #clock-cells : from common clock binding; shall be set to 0.
22 - clocks : shall be the input parent clock phandle for the clock. This should
23 be a pll output.
24 - #clock-cells : from common clock binding; shall be set to 0.
36 - enable-reg : shall be the register offset from PMC base for the enable
38 - enable-bit : shall be the bit within enable-reg to enable/disable the clock.
[all …]
|
| D | xgene.txt | 8 - compatible : shall be one of the following:
14 - reg : shall be the physical PLL register address for the pll clock.
15 - clocks : shall be the input parent clock phandle for the clock. This should
16 be the reference clock.
17 - #clock-cells : shall be set to 1.
18 - clock-output-names : shall be the name of the PLL referenced by derive
21 - clock-names : shall be the name of the PLL. If missing, use the device name.
24 - reg : shall be a list of address and length pairs describing the CSR
25 reset and/or the divider. Either may be omitted, but at least
26 one must be present.
[all …]
|
| D | silabs,si570.txt | 5 This binding uses the common clock binding[1]. Details about the devices can be
15 - compatible: Shall be one of "silabs,si570", "silabs,si571",
18 - #clock-cells: From common clock bindings: Shall be 0.
20 The correct frequency for the part used has to be provided in
23 - temperature-stability: Temperature stability of the device in PPM. Should be
27 - clock-output-names: From common clock bindings. Recommended to be "si570".
29 frequency set during boot. It can be reprogrammed during
|
| D | marvell,pxa910.txt | 8 - compatible: should be one of the following.
13 "mpmu", "apmu", "apbc", "apbcp". So four reg spaces need to be defined.
15 - #clock-cells: should be 1.
16 - #reset-cells: should be 1.
21 All these identifier could be found in <dt-bindings/clock/marvell-pxa910.h>.
|
| D | marvell,pxa168.txt | 8 - compatible: should be one of the following.
13 "mpmu", "apmu", "apbc". So three reg spaces need to be defined.
15 - #clock-cells: should be 1.
16 - #reset-cells: should be 1.
21 All these identifier could be found in <dt-bindings/clock/marvell,pxa168.h>.
|
| D | marvell,mmp2.txt | 8 - compatible: should be one of the following.
13 "mpmu", "apmu", "apbc". So three reg spaces need to be defined.
15 - #clock-cells: should be 1.
16 - #reset-cells: should be 1.
21 All these identifier could be found in <dt-bindings/clock/marvell-mmp2.h>.
|
| D | silabs,si5351.txt | 10 generators can be found in [1].
15 - compatible: shall be one of "silabs,si5351{a,a-msop,b,c}".
16 - reg: i2c device address, shall be 0x60 or 0x61.
17 - #clock-cells: from common clock binding; shall be set to 1.
19 handles, shall be xtal reference clock or xtal and clkin for
22 - #address-cells: shall be set to 1.
23 - #size-cells: shall be set to 0.
31 Each of the clock outputs can be overwritten individually by
39 - silabs,clock-source: source clock of the output divider stage N, shall be
44 - silabs,drive-strength: output drive strength in mA, shall be one of {2,4,6,8}.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | atmel-at91.txt | 8 compatible: must be one of:
11 * "atmel,at91sam9" for SoCs using an ARM926EJ-S core, shall be extended with
16 o "atmel,at91sam9x5" for the 5 series, shall be extended with the specific
28 * "atmel,sama5" for SoCs using a Cortex-A5, shall be extended with the specific
30 o "atmel,sama5d2" shall be extended with the specific SoC compatible:
32 o "atmel,sama5d3" shall be extended with the specific SoC compatible:
38 o "atmel,sama5d4" shall be extended with the specific SoC compatible:
45 - compatible: Should be "atmel,at91sam9260-pit"
51 - compatible: Should be "atmel,at91rm9200-st", "syscon", "simple-mfd"
56 Its subnodes can be:
[all …]
|
| D | sp810.txt | 9 should be: "arm,sp810", "arm,primecell"
16 should be: "refclk", "timclk", "apb_pclk"
22 should be: <1>
25 should be: "timerclken0", "timerclken1", "timerclken2", "timerclken3"
28 should be: clock specifier for each output clock of this
32 should be: phandle of input clock listed in clocks
|
| /linux-4.4.14/drivers/iio/adc/ |
| D | Kconfig | 23 To compile this driver as a module, choose M here: the module will be
34 module will be called ad7291.
46 module will be called ad7298.
59 module will be called ad7476.
69 To compile this driver as a module, choose M here: the module will be
81 module will be called AD7793.
93 module will be called ad7887.
105 module will be called ad7923.
118 To compile this driver as a module, choose M here: the module will be
131 To compile this driver as a module, choose M here: the module will be
[all …]
|
| /linux-4.4.14/Documentation/frv/ |
| D | booting.txt | 9 First of all, a root filesystem must be made available. This can be done in
14 A filesystem should be constructed in a directory on an NFS server that
15 the target board can reach. This directory should then be NFS exported
20 In this case, the image must be stored or built up on flash before it
21 can be used. A complete image can be built using the mkfs.jffs2 or
29 The kernel will need to be loaded into RAM by RedBoot (or by some alternative
30 boot loader) before it can be run. The kernel image (arch/frv/boot/Image) may
31 be loaded in one of three ways:
42 The image is then ready to be executed.
51 The image is then ready to be executed.
[all …]
|
| D | clock.txt | 13 On all boards, the 'p0' file should also be writable, and either '1' or '0'
14 can be rewritten, to set or clear the CLKC_P0 bit respectively, hence
17 The 'cm' file should also be available on all boards. '0' can be written to it
18 to shift the board into High-Speed mode (normal), and '1' can be written to
23 writable, allowing the CPU core speed (and other clock speeds) to be
30 The current state and the available masks can be found in /proc/cpuinfo. For
57 be set to what values. The specification values are bitmasks; so, for example,
58 "suspend=0x9" indicates that 0 and 3 can be written validly to
61 The PM-Controls line will only be present if CONFIG_PM is configured to Y.
64 the file can be read, then the suspend value must be 0, and so that's not
|
| D | kernel-ABI.txt | 11 registers, thus requiring at least one general purpose register to be
14 This cannot be extended to modules for the displacement is likely to be too
15 far. Thus in modules the address of a function to call must be calculated
54 available that may be accessed in this mode, in addition to all the
60 handler. On entry to the handler, the PSR.T bit will be cleared.
71 management exceptions will be flagged for later consideration, but
72 the exception handler won't be invoked. Debugging traps such as
73 hardware breakpoints and watchpoints will be ignored. This mode is
76 All kernel mode registers may be accessed, plus a few extra debugging
142 (including the stack pointer) may be changed.
[all …]
|
| D | atomic-ops.txt | 6 instruction. Unfortunately, this alone can't be used to implement the following operations:
17 interrupts, but on the FR-V CPUs, modifying the PSR takes a lot of clock cycles, and it has to be
34 (*) All atomic operations can then be broken down into the following algorithm:
38 (2) Load the value currently in the memory to be modified into a register.
47 task pointer in the kernel, and so is guaranteed to be non-zero).
85 load. The VLIW packing ensures they are done simultaneously. The ".p" on the load must not be
91 Then the proposed modification is generated. Note that the old value can be retained if required
105 Such that the branch can then be taken if the operation was aborted.
121 The atomic ops implementation can be made inline or out-of-line by changing the
125 - The resulting kernel image may be smaller
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/usb/ |
| D | omap-usb.txt | 4 - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
5 - ti,hwmods : must be "usb_otg_hs"
6 - multipoint : Should be "1" indicating the musb controller supports
9 MUSB configuration-specific setting. Should be set to "16"
10 - ram-bits : Specifies the ram address size. Should be set to "12"
12 interface between the controller and the phy. It should be "0" or "1"
14 - mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
16 - power : Should be "50". This signifies the controller can supply up to
47 - compatible : Should be
50 - ti,hwmods : Should be "usb_otg_ss"
[all …]
|
| D | exynos-usb.txt | 8 - compatible: should be "samsung,exynos4210-ehci" for USB 2.0
14 - clock-names: from common clock binding: Shall be "usbhost".
15 - port: if in the SoC there are EHCI phys, they should be listed here.
25 needs to be pulled up for the bus to be powered.
49 - compatible: should be "samsung,exynos4210-ohci" for USB 2.0
55 - clock-names: from common clock binding: Shall be "usbhost".
56 - port: if in the SoC there are OHCI phys, they should be listed here.
85 - compatible: should be one of the following -
89 - #address-cells, #size-cells : should be '1' if the device has sub-nodes
97 The dwc3 core should be added as subnode to Exynos dwc3 glue.
[all …]
|
| D | dwc3-st.txt | 8 - compatible : must be "st,stih407-dwc3"
10 - reg-names : should be "reg-glue" and "syscfg-reg"
11 - st,syscon : should be phandle to system configuration node which
13 - resets : list of phandle and reset specifier pairs. There should be two entries, one
15 - reset-names : list of reset signal names. Names should be "powerdown" and "softreset"
19 - #address-cells, #size-cells : should be '1' if the device has sub-nodes
22 - pinctl-names : A pinctrl state named "default" must be defined
32 The dwc3 core should be added as subnode to ST DWC3 glue as shown in the
33 example below. The DT binding details of dwc3 can be found in:
|
| D | ehci-st.txt | 4 - compatible : must be "st,st-ehci-300x"
7 - interrupts : one EHCI interrupt should be described here
8 - pinctrl-names : a pinctrl state named "default" must be defined
12 - clock-names : should be "ic" for interconnect clock and "clk48"
16 - phy-names : should be "usb"
19 - reset-names : should be "power" and "softreset"
|
| /linux-4.4.14/drivers/iio/light/ |
| D | Kconfig | 19 be called acpi-als.
30 This driver can also be built as a module. If so, the module
31 will be called adjd_s311.
41 module will be called al3320a.
51 module will be called apds9300.
64 module will be called apds9960
74 be called bh1750.
85 the module will be called cm32181.
96 the module will be called cm3232.
106 be called cm3323.
[all …]
|
| /linux-4.4.14/Documentation/ |
| D | md.txt | 1 Tools that manage md devices can be found at
47 This autodetection may be suppressed with the kernel parameter
49 superblock can be autodetected and run at boot time.
59 'dirty' means that the parity cannot be trusted, and the fact that it
61 be reconstructed (due to no parity).
72 arrays to be started.
100 be accessed.
102 An array should be created by a user-space tool. This will write
111 format is to be used. The minor number might be used to tune handling
121 Once started, new devices can be added. They should have an
[all …]
|
| D | circular-buffers.txt | 9 Linux provides a number of features that can be used to implement circular
18 To use these facilities, as discussed below, there needs to be just one
53 indices should be wrapped to 0 when they reach the end of the buffer, thus
56 Typically, items will all be of the same unit size, but this isn't strictly
57 required to use the techniques below. The indices can be increased by more
58 than 1 if multiple items or variable-sized items are to be included in the
60 be careful, however, as a region more than one unit in size may wrap the end of
61 the buffer and be broken into two segments.
69 circular buffer would normally be a slow operation, requiring the use of a
71 then a much quicker bitwise-AND instruction can be used instead.
[all …]
|
| D | padata.txt | 4 Padata is a mechanism by which the kernel can farm work out to be done in
6 developed for use with the IPsec code, which needs to be able to perform
9 sufficiently general fashion that it could be put to other uses as well.
12 overall control of how tasks are to be run:
20 The pcpumask describes which processors will be used to execute work
22 processors are allowed to be used as the serialization callback processor.
23 The workqueue wq is where the work will actually be done; it should be
27 cpumasks this helper function can be used:
51 The list of CPUs to be used can be adjusted with these functions:
61 Changing the CPU masks are expensive operations, though, so it should not be
[all …]
|
| D | vme_api.txt | 14 occurred a negative error code will be returned.
16 A pointer to a structure of type 'vme_driver' must be provided to the
32 should be correctly set. The '.name' element is a pointer to a string holding
36 be registered. The match function should return 1 if a device should be
62 driver. The bridge number (or bus number) can be accessed using
75 be called the number of times specified during the registration. If a match
76 succeeds, a non-zero value should be returned. A zero return value indicates
79 device structure. This pointer should be saved, it will be required for
84 specific window or DMA channel (which may be used by a different driver) this
85 driver allows a resource to be assigned based on the required attributes of the
[all …]
|
| D | module-signing.txt | 33 standard (though it is pluggable and permits others to be used). The possible
34 hash algorithms that can be used are SHA-1, SHA-224, SHA-256, SHA-384, and
49 (1) "Require modules to be validly signed" (CONFIG_MODULE_SIG_FORCE)
56 be marked as being tainted, and the concerned modules will be marked as
60 signature that can be verified by a public key in the kernel's possession
61 will be loaded. All other modules will generate an error.
64 cannot be parsed, it will be rejected out of hand.
69 If this is on then modules will be automatically signed during the
71 be signed manually using:
76 (3) "Which hash algorithm should modules be signed with?"
[all …]
|
| D | stable_kernel_rules.txt | 6 - It must be obviously correct and tested.
7 - It cannot be bigger than 100 lines, with context.
9 - It must fix a real bug that bothers people (not a, "This could be a
16 be considered if they fix a notable performance or interactivity issue.
18 regression they should only be submitted by a distribution kernel
23 race can be exploited is also provided.
35 - Security patches should not be handled (solely) by the -stable review
44 in the sign-off area. Once the patch is merged it will be applied to
45 the stable tree without anything else needing to be done by the author
52 why you think it should be applied, and what kernel version you wish it to
[all …]
|
| D | nommu-mmap.txt | 13 ptrace() work. Under uClinux there is no fork(), and clone() must be supplied
45 - If possible, the file mapping will be directly on the backing device
52 appropriate bit of the file will be read into a contiguous bit of
53 memory and any extraneous space beyond the EOF will be cleared
84 case, a shared-writable memory mapping will be possible. It will work
86 support, then the mapping request will be denied.
93 blockdev must be able to provide a contiguous run of pages without
103 provides memory or quasi-memory that can be accessed directly. Examples
105 provide any such support, then the mapping request will be denied.
113 page-aligned. This is because XIP may take place, and the data may not be
[all …]
|
| D | kobject.txt | 17 some terms we will be working with.
21 objects to be arranged into hierarchies), a specific type, and,
29 If it does, the reference counting for the object is sure to be messed
30 up and incorrect, and your code will be buggy. So do not do this.
36 - A kset is a group of kobjects. These kobjects can be of the same ktype
46 approach will be taken, so we'll go back to kobjects.
53 a larger, domain-specific object. To this end, kobjects will be found
55 object-oriented terms, kobjects can be seen as a top-level, abstract class
60 embedding - must be used.
92 embedded *within* a struct uio_map could be converted to a pointer to the
[all …]
|
| D | media-framework.txt | 33 not be confused with physical pins at chip boundaries.
53 registration. The following fields must be set:
58 - model must be filled with the device model name as a NUL-terminated UTF-8
59 string. The device/model revision must not be stored in this field.
65 doesn't provide a unique serial number this field must be left empty.
68 NUL-terminated ASCII string. For PCI/PCIe devices bus_info must be set to
70 the usb_make_path() function must be used. This field is used by
75 When possible the revision should be formatted with the KERNEL_VERSION
79 minor must be incremented when new features are added to the userspace API
80 without breaking binary compatibility. The version major must be
[all …]
|
| D | volatile-considered-harmful.txt | 1 Why the "volatile" type class should not be used
4 C programmers have often taken volatile to mean that the variable could be
20 unwanted optimization. If they are being used properly, there will be no
34 want to play with that data will be waiting on the lock. The spinlock
36 meaning that data accesses will not be optimized across them. So the
37 compiler might think it knows what will be in shared_data, but the
39 forget anything it knows. There will be no optimization problems with
42 If shared_data were declared volatile, the locking would still be
43 necessary. But the compiler would also be prevented from optimizing access
45 can be working with it. While the lock is held, shared_data is not
[all …]
|
| D | DMA-API.txt | 21 A dma_addr_t can hold any valid DMA address for the platform. It can be
23 a dma_addr_t directly because there may be translation between its physical
34 the processor can immediately be read by the processor or device
44 It also returns a <dma_handle> which may be cast to an unsigned integer the
48 Note: consistent memory can be expensive on some platforms, and the
49 minimum allocation length may be as big as a page, so you should
70 size and dma_handle must all be the same as those passed into
71 dma_alloc_coherent(). cpu_addr must be the virtual address returned by
75 may only be called with IRQs enabled.
88 for alignment, like queue heads needing to be aligned on N-byte boundaries.
[all …]
|
| D | assoc_array.txt | 34 [!] NOTE: Pointers to objects _must_ be zero in the least significant bit.
37 permits an object to be located in multiple arrays simultaneously.
42 (4) Index keys must be unique. Inserting an object with the same key as one
45 (5) Index keys can be of any length and can be of different lengths.
55 (9) The array can be iterated over whilst it is being modified, provided the
57 circumstances, some objects may be seen more than once. If this is a
59 be missed, however, unless deleted.
61 (10) Objects in the array can be looked up by means of their index key.
63 (11) Objects can be looked up whilst the array is being modified, provided the
68 tree. To improve memory efficiency, shortcuts can be emplaced to skip over
[all …]
|
| D | flexible-arrays.txt | 5 Large contiguous memory allocations can be unreliable in the Linux kernel.
8 memory from vmalloc() must be mapped into a relatively small address space;
15 In many cases, the need for memory from vmalloc() can be eliminated by
22 allocation failures should be relatively rare. The down sides are that the
23 arrays cannot be indexed directly, individual object size cannot exceed the
38 maximum number of objects which can be stored in the array. The flags
48 element size and total will be checked for validity at compile time.
56 indicated by element_nr (which must be less than the maximum specified when
57 the array was created). If any memory allocations must be performed, flags
58 will be used. The return value is zero on success, a negative error code
[all …]
|
| /linux-4.4.14/net/sched/ |
| D | Kconfig | 16 is a FIFO (first come, first served). If you say Y here, you will be
18 then be attached to different network devices. This is useful for
22 This code is considered to be experimental.
36 If you say Y here and to "/proc file system" below, you will be able
62 module will be called sch_cbq.
76 module will be called sch_htb.
85 module will be called sch_hfsc.
99 module will be called sch_atm.
108 module will be called sch_prio.
117 module will be called sch_multiq.
[all …]
|
| /linux-4.4.14/drivers/staging/comedi/ |
| D | Kconfig | 30 be requested by a userspace program without root privileges.
37 Enable comedi misc drivers to be built
54 To compile this driver as a module, choose M here: the module will be
61 This driver is mainly for testing purposes, but can also be used to
65 To compile this driver as a module, choose M here: the module will be
76 To compile this driver as a module, choose M here: the module will be
84 To compile this driver as a module, choose M here: the module will be
93 To compile this driver as a module, choose M here: the module will be
101 Enable comedi ISA and PC/104 drivers to be built
115 To compile this driver as a module, choose M here: the module will be
[all …]
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | automount-support.txt | 2 support (such as kAFS which can be found in fs/afs/ and NFS in
3 fs/nfs/). This facility includes allowing in-kernel mounts to be
4 performed and mountpoint degradation to be requested. The latter can
5 also be requested by userspace.
38 mountpoint to be expired in the automounting procedure outlined separately.
42 (1) Create at least one list off which the vfsmounts to be expired can be
49 (3) When you want mountpoints to be expired, call mark_mounts_for_expiry()
54 (it's only referenced by its parent vfsmount), then it will be deleted
65 mount is made on an expirable mount, the new vfsmount will not be on the
68 If a namespace is copied, all mountpoints contained therein will be copied,
[all …]
|
| D | adfs.txt | 4 uid=nnn All files in the partition will be owned by
6 gid=nnn All files in the partition will be in group
9 will be nnn. Default 0700.
11 will be nnn. Default 0077.
12 ftsuffix=n When ftsuffix=0, no file type suffix will be applied.
14 the RISC OS file type will be added. Default 0.
45 not a UnixExec filetype, then the permissions will be:
50 be modified to:
60 desire the permissions should be under Linux.
67 To enable non-RISC OS systems to be used to store files without losing
[all …]
|
| D | debugfs.txt | 11 to be maintained forever.
20 options can be used.
25 of business will be to create at least one directory to hold a set of
31 indicated parent directory. If parent is NULL, the directory will be
33 dentry pointer which can be used to create files in the directory (and to
47 should hold the file, data will be stored in the i_private field of the
50 operations should be provided; others can be included as needed. Again,
51 the return value will be a dentry pointer to the created file, NULL for
54 Create a file with an initial size, the following function can be used
67 for simple situations. Files containing a single integer value can be
[all …]
|
| D | afs.txt | 41 The filesystem should be enabled by turning on the kernel configuration
48 Additionally, the following can be turned on to aid debugging:
50 CONFIG_AF_RXRPC_DEBUG - Permit AF_RXRPC debugging to be enabled
51 CONFIG_AFS_DEBUG - Permit AFS debugging to be enabled
53 They permit the debugging messages to be turned on dynamically by manipulating
64 When inserting the driver modules the root cell must be specified along with a
72 RxRPC remote operation protocol and may also be accessed from userspace. See:
79 Once the module has been loaded, more modules can be added by the following
87 Filesystems can be mounted anywhere by commands similar to the following:
98 The name of the volume can be suffixes with ".backup" or ".readonly" to
[all …]
|
| D | fiemap.txt | 35 Certain flags to modify the way in which mappings are looked up can be
39 with all flags passed, the contents of fm_flags will be unmodified.
46 that can be used to return extents. If fm_extent_count is zero, then the
47 fm_extents[] array is ignored (no extents will be returned), and the
52 The following flags can be set in fm_flags:
67 number of elements in the fiemap_extents[] array should be passed via
68 fm_extent_count. The number of extents mapped by kernel will be
70 allocated is less than would be required to map the requested range,
71 the maximum number of extents that can be mapped in the fm_extent[]
72 array will be returned and fm_mapped_extents will be equal to
[all …]
|
| D | overlayfs.txt | 15 many use cases will be able to ignore these differences.
19 cases an object accessed in the union will be indistinguishable
26 only be unique when combined with st_dev, and both of these can change
28 tools ignore these values and will not be affected.
39 It would be more correct to refer to an upper and lower 'directory
41 directory trees to be in the same filesystem and there is no
42 requirement that the root of a filesystem be given for either upper or
45 The lower filesystem can be any filesystem supported by Linux and does
46 not need to be writable. The lower filesystem can even be another
47 overlayfs. The upper filesystem will normally be writable and if it
[all …]
|
| /linux-4.4.14/Documentation/networking/ |
| D | rxrpc.txt | 6 that can be used to perform RxRPC remote operations. This is done over sockets
67 manage security on the client end. The server end must of necessity be
99 endpoint, thus allowing the endpoints to be shared, even to the same
103 to multiple services. A service may be considered the RxRPC equivalent of
106 (*) Client-originating packets are marked, thus a transport endpoint can be
110 (*) Up to a billion connections may be supported concurrently between one
123 billion calls, but only up to four calls may be in progress on a
143 connection lapse before the client, the security will be renegotiated if
152 been received but may yet be discarded and re-requested. The sender may
162 (*) An call may be aborted by either end at any time up to its completion.
[all …]
|
| D | netdev-features.txt | 22 be changed (enabled or disabled) for a particular device by user's
23 request. This set should be initialized in ndo_init callback and not
27 for a device. This should be changed only by network core or in
38 networking core and should not be referenced in drivers.
45 When current feature set (netdev->features) is to be changed, new set
62 netdev_update_features() while holding rtnl_lock. This should not be done
63 from ndo_*_features callbacks. netdev->features should not be modified by
73 All dependencies between features should be resolved here. The resulting
74 set can be reduced further by networking core imposed limitations (as coded
78 This callback should not modify hardware nor driver state (should be
[all …]
|
| D | ipv6.txt | 4 Module options may be given as command line arguments to the insmod
17 its functionality. This might be used when another module
31 No IPv6 addresses will be added to interfaces, and
32 it will not be possible to open an IPv6 socket.
39 on all interfaces. This might be used when one does not wish
40 for addresses to be automatically generated from prefixes
49 will be added to interfaces.
59 This might be used when no IPv6 addresses are desired.
71 No IPv6 addresses will be added to interfaces.
|
| D | dns_resolver.txt | 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:
49 To set up this facility, the /etc/request-key.conf file must be altered so that
51 basic dname to IPv4/IPv6 address resolution, the following line should be
58 To direct a query for query type 'foo', a line of the following should be added
69 implemented in the module can be called after doing:
78 may then be cached. The key description is constructed as a string of the
84 and thus the type of query to do, and <name> specifies the string to be
88 The name parameter is not required to be a NUL-terminated string, and its
89 length should be given by the namelen argument.
[all …]
|
| D | x25-iface.txt | 5 This is a description of the messages to be passed between the X.25 Packet
9 The X.25 device driver will be coded normally as per the Linux device driver
10 standards. Most X.25 device drivers will be moderately similar to the
13 needs to be passed to and from the Packet Layer for proper operation.
15 All messages are held in sk_buff's just like real data to be transmitted
25 This indicates that the rest of the skbuff contains data to be transmitted
32 confirmation message should be returned as soon as possible.
37 confirmation message should be returned as soon as possible.
41 LAPB parameters. To be defined.
64 LAPB parameters. To be defined.
[all …]
|
| /linux-4.4.14/drivers/net/ieee802154/ |
| D | Kconfig | 10 If you say N, all options in this submenu will be skipped and
20 This driver can also be built as a module. To do so say M here.
21 The module will be called 'fakelb'.
32 This driver can also be built as a module. To do so, say M here.
33 the module will be called 'at86rf230'.
51 This driver can also be built as a module. To do so, say M here.
52 the module will be called 'mrf24j40'.
62 This driver can also be built as a module. To do so, say M here.
63 the module will be called 'cc2520'.
72 This driver can also be built as a module. To do so say M here.
[all …]
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 4.Coding | 3 While there is much to be said for a solid and community-oriented design
5 code. It is the code which will be examined by other developers and merged
29 the standard; many developers will request that the code be reformatted
37 win before the code can be merged. Putting code into the kernel means
48 on it for other reasons, but coding style changes should not be made for
51 The coding style document also should not be read as an absolute law which
52 can never be transgressed. If there is a good reason to go against the
63 But experience has shown that excessive or premature abstraction can be
64 just as harmful as premature optimization. Abstraction should be used to
75 patches to remove unused arguments; they should, in general, not be added
[all …]
|
| D | 5.Posting | 3 Sooner or later, the time comes when your work is ready to be presented to
9 more information can also be found in the files SubmittingPatches,
18 work being done is complex, though, there is a lot to be gained by getting
25 which remains to be done and any known problems. Fewer people will look at
26 patches which are known to be half-baked, but those who do will come in
32 There are a number of things which should be done before you consider
45 summary of the results should be included with the patch.
48 for an employer, the employer likely has a right to the work and must be
57 The preparation of patches for posting can be a surprising amount of work,
61 Patches must be prepared against a specific version of the kernel. As a
[all …]
|
| D | 7.AdvancedTopics | 5 number of topics which can be helpful for developers wanting to become a
23 teach the reader how to use git; that would be sufficient material for a
24 long document in its own right. Instead, the focus here will be on how git
36 available to others. A git-using developer should be able to obtain a copy
42 heads, etc. It can all be a little intimidating at the outset, but the
45 Using git to generate patches for submission by email can be a good
49 will, of course, need a server that can be pulled from. Setting up such a
57 of development can be separated into a separate "topic branch" and
61 Publicly-available branches should be created with care; merge in patches
67 say, or which has some other sort of obvious bug) can be fixed in place or
[all …]
|
| D | 6.Followthrough | 8 with, possibly, quite a bit of work yet to be done.
13 code. You, as the author of that code, will be expected to work with the
22 developers as they review the code. Working with reviewers can be, for
24 process. Life can be made much easier, though, if you keep a few things in
29 will not keep them from asking a fundamental question: what will it be
31 Many of the changes you may be asked to make - from coding style tweaks
33 still be around and under development a decade from now.
45 be working on the kernel years from now, but they understand that their
65 be easy to become blinded by your own solution to a problem to the point
85 time; if you help them get a running start, they will be in a better mood
[all …]
|
| D | 3.Early-stage | 3 When contemplating a Linux kernel development project, it can be tempting
13 clear description of the problem to be solved. In some cases, this step is
22 framework; this module could be configured to give specific applications
57 - What, exactly, is the problem which needs to be solved?
73 - It may well be that the problem is addressed by the kernel in ways which
80 it will also not be accepted into the mainline kernel.
82 - There may be elements of the proposed solution which will not be
87 problem; they may have ideas for a better solution, and may be willing
94 requiring months or years of effort before the code can be brought up to
98 single-processor systems. It could not be merged into the mainline
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 11 - model : Should be "nintendo,wii"
12 - compatible : Should be "nintendo,wii"
21 - compatible : Should be "nintendo,hollywood"
30 - compatible : should be "nintendo,hollywood-vi","nintendo,flipper-vi"
41 - compatible : should be "nintendo,hollywood-pi","nintendo,flipper-pi"
47 The node for the "Flipper" interrupt controller must be placed under
53 - compatible : should be "nintendo,flipper-pic"
63 - compatible : should be "nintendo,hollywood-dsp","nintendo,flipper-dsp"
75 - compatible : should be "nintendo,hollywood-si","nintendo,flipper-si"
86 - compatible : should be "nintendo,hollywood-ai","nintendo,flipper-ai"
[all …]
|
| D | gamecube.txt | 12 - compatible : Should be "nintendo,flipper"
21 - compatible : should be "nintendo,flipper-vi"
32 - compatible : should be "nintendo,flipper-pi"
38 The node for the "Flipper" interrupt controller must be placed under
43 - compatible : should be "nintendo,flipper-pic"
52 - compatible : should be "nintendo,flipper-dsp"
60 The ARAM node must be placed under the DSP node.
64 - compatible : should be "nintendo,flipper-aram"
73 - compatible : should be "nintendo,flipper-di"
84 - compatible : should be "nintendo,flipper-ai"
[all …]
|
| /linux-4.4.14/drivers/media/dvb-frontends/drx39xyj/ |
| D | drx_dap_fasi.h | 98 #error At least one of short- or long-addressing format must be allowed.
201 #error DRXDAP_MAX_WCHUNKSIZE must be at least 3 in single master mode
204 #error DRXDAP_MAX_WCHUNKSIZE must be at least 5 in multi master mode
209 #error DRXDAP_MAX_WCHUNKSIZE must be at least 5 in single master mode
212 #error DRXDAP_MAX_WCHUNKSIZE must be at least 7 in multi master mode
225 #error DRXDAP_MAX_RCHUNKSIZE must be at least 2
231 #error DRXDAP_MAX_RCHUNKSIZE must be even
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | brcm,unimac-mdio.txt | 9 - reg-names: name(s) of the register must be "mdio" and optional "mdio_indir_rw"
10 - #size-cells: must be 1
11 - #address-cells: must be 0
14 - interrupts: must be one if the interrupt is shared with the Ethernet MAC or
15 Ethernet switch this MDIO block is integrated from, or must be two, if there
16 are two separate interrupts, first one must be "mdio done" and second must be
18 - interrupt-names: must be "mdio_done_error" when there is a share interrupt fed
19 to this hardware block, or must be "mdio_done" for the first interrupt and
|
| D | brcm,bcm7445-switch-v4.0.txt | 5 - compatible: should be "brcm,bcm7445-switch-v4.0"
6 - reg: addresses and length of the register sets for the device, must be 6
8 - interrupts: interrupts for the devices, must be two interrupts
11 - #size-cells: must be 0
12 - #address-cells: must be 2, see dsa/dsa.txt
16 The integrated switch subnode should be specified according to the binding
22 must be: "core", "reg", "intrl2_0", "intrl2_1", "fcb", "acb"
25 must be: "switch_0" and "switch_1"
|
| /linux-4.4.14/Documentation/i2c/ |
| D | slave-interface | 6 Linux can also be an I2C slave if the I2C controller in use has slave
15 use a character device, be in-kernel only, or something completely different:
49 First, the events which are used by the bus driver and the backend will be
51 drivers and writing backends will be given.
62 types described hereafter. 'val' holds an u8 value for the data byte to be
63 read/written and is thus bidirectional. The pointer to val must always be
65 is the return value from the backend. Mandatory events must be provided by the
66 bus drivers and must be checked for by backend drivers.
75 Another I2C master wants to write data to us. This event should be sent once
78 to be done, though.
[all …]
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | pmu-ebb.txt | 11 One type of event for which EBBs can be configured is PMU exceptions. This
21 attr.config. All events which can be configured on the hardware PMU are
29 EBBs can only sensibly be used by programs for self-monitoring.
31 It is a feature of the perf_events API that events can be created on other
34 EBBs will ever be delivered.
38 and attach an EBB event to the process, which will then cause EBBs to be
44 events can be configured. This means that EBB events can not be run
48 kernel will in general schedule the EBB event, and perf will be notified that
53 events will be given priority over other events, unless they are also pinned.
55 first will be scheduled and the other will be put in error state. See the
[all …]
|
| D | transactional_memory.txt | 53 lwarx/stwcx), either *both* SAVINGS_ACCT(r3) and CURRENT_ACCT(r3) will be
54 updated, or neither will be updated.
57 transaction, the transaction will be aborted by the CPU. Register and memory
59 'tbegin+4'. The branch to abort_handler will be taken this second time; the
77 Syscalls made from within an active transaction will not be performed and the
78 transaction will be doomed by the kernel with the failure code TM_CAUSE_SYSCALL
85 effects will be persistent, independent of transaction success or failure. No
89 Care must be taken when relying on syscalls to abort during active transactions
107 delivered. For future compatibility the MSR.TS field should be checked to
119 However, basic signal handlers don't need to be aware of transactions
[all …]
|
| /linux-4.4.14/Documentation/ABI/ |
| D | README | 4 interfaces should be used by userspace programs in different ways.
14 defined to be stable. Userspace programs are free to use these
16 them will be guaranteed for at least 2 years. Most interfaces
17 (like syscalls) are expected to never change and always be
21 This directory documents interfaces that are felt to be stable,
23 The interface can be changed to add new features, but the
26 programs can start to rely on these interfaces, but they must be
28 be marked stable. Programs that use these interfaces are
36 the kernel, but are marked to be removed at some later point in
38 why it is obsolete and when it can be expected to be removed.
[all …]
|
| /linux-4.4.14/drivers/iio/temperature/ |
| D | Kconfig | 13 This driver can also be built as a module. If so, the module will
14 be called mlx90614.
23 This driver can also be built as a module. If so, the module will
24 be called tmp006.
34 This driver can also be built as a module. If so, the module will
35 be called tsys01.
45 This driver can also be built as a module. If so, the module will
46 be called tsys02d.
|
| /linux-4.4.14/drivers/media/usb/gspca/ |
| D | Kconfig | 16 module will be called gspca_main.
32 module will be called gspca_benq.
41 module will be called gspca_conex.
52 module will be called gspca_cpia1.
62 module will be called gspca_dtcs033.
71 module will be called gspca_etoms.
80 module will be called gspca_finepix.
89 module will be called gspca_jeilinj.
99 module will be called gspca_jl2005bcd.
108 module will be called gspca_kinect.
[all …]
|
| /linux-4.4.14/Documentation/crypto/ |
| D | asymmetric-keys.txt | 19 The "asymmetric" key type is designed to be a container for the keys used in
25 However, no requirement is made that the key data actually be stored in the
28 A completely in-kernel key retention and operation subtype can be defined, but
29 it would also be possible to provide access to cryptographic hardware (such as
30 a TPM) that might be used to both retain the relevant key and perform
32 merely be an interface to the TPM driver.
37 subtype of the key and define the operations that can be done on that key.
50 should be given from the content of the key.
52 This can then be used to refer to the key, either by complete match or by
71 only keys of the specified subtype (e.g. tpm) will be matched. For
[all …]
|
| /linux-4.4.14/Documentation/connector/ |
| D | connector.txt | 11 identifier, the appropriate callback will be called.
36 idx and val are unique identifiers which must be registered in the
38 callback function which will be called when a message with above idx.val
40 be dereferenced to struct cn_msg *.
62 It must be registered in connector.h for legal in-kernel users.
78 Sends message to the specified groups. It can be safely called from
80 If there are no listeners for given group -ESRCH can be returned.
83 u16 len - for *_multi multiple cn_msg messages can be sent
85 If non-zero the message will be sent to the
86 given port, which should be set to the
[all …]
|
| /linux-4.4.14/drivers/input/misc/ |
| D | Kconfig | 7 Say Y here, and a list of miscellaneous input drivers will be displayed.
23 will be called 88pm860x_onkey.
33 will be called 88pm80x_onkey.
43 will be called ab8500-ponkey.
53 module will be called ad714x.
63 module will be called ad714x-i2c.
73 module will be called ad714x-spi.
83 module will be called arizona-haptics.
94 module will be called bma150.
104 module will be called e3x0_button.
[all …]
|
| /linux-4.4.14/Documentation/input/ |
| D | event-codes.txt | 3 may be used.
23 type has a set of applicable codes to be used in generating events. See the
27 - Used as markers to separate events. Events may be separated in time or in
107 touchscreens. These devices may be used with fingers, pens, or other tools.
109 code should be set to a value of 1. When the tool is no longer interacting
110 with the input device, the BTN_TOOL_<name> code should be reset to 0. All
115 BTN_TOUCH is used for touch contact. While an input tool is determined to be
116 within meaningful physical contact, the value of this property must be set
120 certain value. BTN_TOUCH may be combined with BTN_TOOL_<name> codes. For
125 BTN_TOUCH must be the first evdev code emitted in a synchronization frame.
[all …]
|
| D | userio.txt | 33 "type" describes the type of command that is being sent. This can be any one
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
38 device. In the event that the command you send is invalid, an error will be
39 returned by the character device and a more descriptive error will be printed
40 to the kernel log. Only one command can be sent at a time, any additional data
41 written to the character device after the initial command will be ignored.
50 forth. Registration can only be performed once a port type is set with
56 set. Can be any of the macros from <linux/serio.h>. For example: SERIO_8042
57 would set the port type to be a normal PS/2 port.
[all …]
|
| D | walkera0701.txt | 15 At back side of transmitter S-video connector can be found. Modulation
16 pulses from processor to HF part can be found at pin 2 of this connector,
17 pin 3 is GND. Between pin 3 and CPU 5k6 resistor can be found. To get
18 modulation pulses to PC, signal pulses must be amplified.
39 access to parport, modules like lp must be unloaded before loading
42 be changed by TX "joystick", check output from /proc/interrupts. Value for
85 One binary and octal value can be grouped to nibble. 24 nibbles + one binary
86 values can be sampled between sync pulses.
88 Values for first four channels (analog joystick values) can be found in
93 Next nibbles 12 .. 21 represents four channels (not all channels can be
[all …]
|
| /linux-4.4.14/Documentation/early-userspace/ |
| D | README | 8 various pieces of functionality that are important enough to be
9 available while a Linux kernel is coming up, but that don't need to be
25 archive to be used as the image or have the kernel build process build
31 Your cpio archive should be specified in CONFIG_INITRAMFS_SOURCE and it
32 will be used directly. Only a single cpio file may be specified in
44 CONFIG_INITRAMFS_SOURCE. Sources can be either directories or files -
48 specified directory name will be mapped to '/'. When packaging a
49 directory, limited user and group ID translation can be performed.
50 INITRAMFS_ROOT_UID can be set to a user ID that needs to be mapped to
51 user root (0). INITRAMFS_ROOT_GID can be set to a group ID that needs
[all …]
|
| /linux-4.4.14/include/sound/ |
| D | soc-dpcm.h | 74 struct snd_soc_pcm_runtime *be; member
111 struct snd_soc_pcm_runtime *be, int stream);
115 struct snd_soc_pcm_runtime *be, int stream);
122 struct snd_soc_pcm_runtime *be, int stream);
126 snd_soc_dpcm_get_substream(struct snd_soc_pcm_runtime *be, int stream);
130 snd_soc_dpcm_be_get_state(struct snd_soc_pcm_runtime *be, int stream);
133 void snd_soc_dpcm_be_set_state(struct snd_soc_pcm_runtime *be, int stream,
|
| /linux-4.4.14/Documentation/devicetree/bindings/serial/ |
| D | omap_serial.txt | 4 - compatible : should be "ti,omap2-uart" for OMAP2 controllers
5 - compatible : should be "ti,omap3-uart" for OMAP3 controllers
6 - compatible : should be "ti,omap4-uart" for OMAP4 controllers
7 - compatible : should be "ti,am4372-uart" for AM437x controllers
8 - compatible : should be "ti,am3352-uart" for AM335x controllers
9 - compatible : should be "ti,dra742-uart" for DRA7x controllers
15 - ti,hwmods : Must be "uart<n>", n being the instance number (1-based)
|
| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-ryos | 5 profile will be read next. The data has to be 3 bytes long.
12 Description: The mouse can store 5 profiles which can be switched by the
17 The data has to be 3 bytes long.
26 The data has to be 125 bytes long.
27 Before reading this file, control has to be written to select
36 in written data. The data has to be 95 bytes long.
37 Before reading this file, control has to be written to select
46 written data. The data has to be 35 bytes long.
47 Before reading this file, control has to be written to select
56 in written data. The data has to be 23 bytes long.
[all …]
|
| D | sysfs-driver-hid-roccat-konepure | 4 Description: The mouse can store 5 profiles which can be switched by the
9 The data has to be 3 bytes long.
17 profile will be read next. The data has to be 3 bytes long.
25 When written, the device can be reset.
36 included in written data. The data has to be 2082 bytes long.
43 Description: The mouse can store 5 profiles which can be switched by the
47 buttons back to the mouse. The data has to be 59 bytes long.
51 Before reading this file, control has to be written to select
58 Description: The mouse can store 5 profiles which can be switched by the
63 settings back to the mouse. The data has to be 31 bytes long.
[all …]
|
| D | sysfs-driver-hid-roccat-isku | 26 written data. The data has to be 6 bytes long.
27 Before reading this file, control has to be written to select
36 in written data. The data has to be 6 bytes long.
37 Before reading this file, control has to be written to select
46 in written data. The data has to be 65 bytes long.
47 Before reading this file, control has to be written to select
56 in written data. The data has to be 41 bytes long.
57 Before reading this file, control has to be written to select
66 written data. The data has to be 35 bytes long.
67 Before reading this file, control has to be written to select
[all …]
|
| D | sysfs-driver-hid-roccat-savu | 4 Description: The mouse can store 5 profiles which can be switched by the
8 buttons to the mouse. The data has to be 47 bytes long.
12 Before reading this file, control has to be written to select
20 profile will be read next. The data has to be 3 bytes long.
27 Description: The mouse can store 5 profiles which can be switched by the
32 settings back to the mouse. The data has to be 43 bytes long.
43 When written, the device can be reset.
53 The data has to be 2083 bytes long.
54 Before reading this file, control has to be written to select
61 Description: The mouse can store 5 profiles which can be switched by the
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | open-pic.txt | 3 This binding specifies what properties must be available in the device tree
14 shall be <string> and the value shall include "open-pic".
17 PIC's addressable register space. The type shall be <prop-encoded-array>.
20 as an Open PIC. No property value shall be defined.
23 interrupt source. The type shall be a <u32> and the value shall be 2.
26 address. The type shall be <u32> and the value shall be 0. As such,
32 shall not be reset during runtime initialization. No property value shall
33 be defined. The presence of this property also mandates that any
34 initialization related to interrupt sources shall be limited to sources
74 // The PIC shall not be reset.
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.diversion | 4 module need to be adapted to the HL<->LL interface described in a separate
5 document. The diversion services may be used with all cards supported by
16 This program is distributed in the hope that it will be useful,
45 only supported by isdn phones. Incoming calls may be diverted
48 The diversions may be invoked statically in the providers exchange
51 forwarding reason is met. Activated static services may also be
56 In this case all incoming calls are checked by rules that may be
58 the checking process is finished and the rule matching will be applied
64 Actions that may be invoked by a rule are ignore, proceed, reject,
68 is selected the call will be held in a proceeding state (without ringing)
[all …]
|
| D | README.hfc-pci | 1 The driver for the HFC-PCI and HFC-PCI-A chips from CCD may be used
5 may be logged.
9 To activate the echo mode the following ioctls must be entered:
13 This reduces the available channels to 1. There must not be open connections
23 If more than one HFC-PCI cards are installed, a specific card may be selected
31 If you want to use all three cards, but the order needs to be at 0xdc00,0xd400,
33 Then the desired card will be the initialised in the desired order.
34 If the io parameter is used the io addresses of all used cards should be
|
| /linux-4.4.14/fs/fscache/ |
| D | Kconfig | 5 This option enables a generic filesystem caching manager that can be
7 Different sorts of caches can be plugged in, depending on the
16 This option causes statistical information to be gathered on local
23 multi-CPU system these may be on cachelines that keep bouncing
33 This option causes latency information to be gathered on local
40 and on a multi-CPU system these may be on cachelines that keep
41 bouncing between CPUs. On the other hand, the histogram may be
50 This permits debugging to be dynamically enabled in the local caching
51 management module. If this is set, the debugging output may be
60 Maintain a global list of active fscache objects that can be
|
| /linux-4.4.14/drivers/input/touchscreen/ |
| D | Kconfig | 7 Say Y here, and a list of supported touchscreens will be displayed.
28 module will be called 88pm860x-ts.
47 module will be called ads7846.
60 module will be called ad7877.
71 module will be called ad7879.
80 module will be called ad7879-i2c.
91 module will be called ad7879-spi.
103 module will be called ar1021_i2c.
116 module will be called atmel_mxt_ts.
129 module will be called auo-pixcir-ts.
[all …]
|
| /linux-4.4.14/Documentation/s390/ |
| D | CommonIO | 15 The given devices will be ignored by the common I/O-layer; no detection
16 and device sensing will be done on any of those devices. The subchannel to
17 which the device in question is attached will be treated as if no device was
20 An ignored device can be un-ignored later; see the "/proc entries"-section for
23 The devices must be given either as bus ids (0.x.abcd) or as hexadecimal
25 give a device number 0xabcd, it will be interpreted as 0.0.abcd.
28 keywords can be used to refer to the CCW based boot device and CCW console
66 the device driver will be notified if possible, so the device will become
69 You can also add ranges of devices to be ignored by piping to
73 Note: While already known devices can be added to the list of devices to be
[all …]
|
| D | monreader.txt | 19 The z/VM guest on which you want to access this API needs to be configured in
21 IUCV *MONITOR statement in its user entry. If the monitor DCSS to be used is
45 always start at 0 and be at least 64MB in size.
62 which can be loaded via the modprobe command, or it can be compiled into the
65 kernel, the kernel parameter "monreader.mondcss=<DCSS NAME>" can be specified
87 which data should be collected. This can be done by the CP command MONITOR
92 After loading the module, a char device will be created along with the device
97 If your distribution does not support udev, a device node will not be created
100 numbers can be found in /sys/class/misc/monreader/dev.
102 <major>:<minor>. The device node can be created via the mknod command, enter
[all …]
|
| /linux-4.4.14/drivers/pwm/ |
| D | Kconfig | 42 will be called pwm-ab8500.
51 will be called pwm-atmel.
63 will be called pwm-atmel-hlcdc.
75 will be called pwm-atmel-tcb.
84 will be called pwm-bcm-kona.
93 will be called pwm-bcm2835.
102 will be called pwm-berlin.
111 will be called pwm-bfin.
121 will be called pwm-brcmstb.c.
131 will be called pwm-clps711x.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | brcm,brcmstb-sata-phy.txt | 4 - compatible: should be one or more of
7 - address-cells: should be 1
8 - size-cells: should be 0
10 - reg-names: should be "phy"
13 Each port's PHY should be represented as a sub-node.
17 - phy-cells: generic PHY binding; must be 0
|
| D | berlin-sata-phy.txt | 5 - compatible: should be one of
8 - address-cells: should be 1
9 - size-cells: should be 0
10 - phy-cells: from the generic PHY bindings, must be 1
15 Each PHY should be represented as a sub-node.
|
| D | brcm,cygnus-pcie-phy.txt | 4 - compatible: must be "brcm,cygnus-pcie-phy"
6 - #address-cells: must be 1
7 - #size-cells: must be 0
9 Each PCIe PHY should be represented by a child node
15 - #phy-cells: must be 0
|
| D | rockchip-usb-phy.txt | 7 - #address-cells: should be 1
8 - #size-cells: should be 0
11 Each PHY should be represented as a sub-node.
15 - #phy-cells: should be 0
23 - clock-names: string, clock name, must be "phyclk"
|
| /linux-4.4.14/Documentation/gpio/ |
| D | board.txt | 4 This document explains how GPIOs can be assigned to given devices and functions.
12 is mandatory) or ARCH_WANT_OPTIONAL_GPIOLIB (if GPIO support can be omitted) in
14 describe its hardware layout. Currently, mappings can be defined through device
19 GPIOs can easily be mapped to devices and functions in the device tree. The
38 it but are only supported for compatibility reasons and should not be used for
52 The led GPIOs will be active-high, while the power GPIO will be active-low (i.e.
53 gpiod_is_active_low(power) will be true).
55 The second parameter of the gpiod_get() functions, the con_id string, has to be
67 The above DT example can be converted to an equivalent ACPI description
106 Finally, GPIOs can be bound to devices and functions using platform data. Board
[all …]
|
| D | consumer.txt | 27 non-forgeable handler that must be obtained through a call to one of the
36 device that displays digits), an additional index argument can be specified:
46 for the GPIO. Values can be:
48 * GPIOD_ASIS or 0 to not initialize the GPIO at all. The direction must be set
55 with IS_ERR() (they will never return a NULL pointer). -ENOENT will be returned
61 gpiod_get_index_optional() functions can be used. These functions return NULL
73 For a function using multiple GPIOs all of those can be obtained with one call:
121 A GPIO descriptor can be disposed of using the gpiod_put() function:
125 For an array of GPIOs this function can be used:
152 The return value is zero for success, else a negative errno. It should be
[all …]
|
| D | driver.txt | 23 the integer GPIO namespace so that it can be used with the legacy GPIO
24 interface. Each chip must thus have a "base" number (which can be automatically
25 assigned), and for each GPIO the global number will be (base + hardware number).
27 users and thus needs to be maintained.
33 be contiguous; either of those platforms could also use numbers 2000-2063 to
49 - optional base number (will be automatically assigned if omitted)
54 gpio_chip and issue gpiochip_add(). Removing a GPIO controller should be rare;
69 not be required.
83 - spinlock_t should be replaced with raw_spinlock_t [1].
84 - If sleepable APIs have to be used, these can be done from the .irq_bus_lock()
[all …]
|
| /linux-4.4.14/drivers/input/keyboard/ |
| D | Kconfig | 8 Say Y here, and a list of supported keyboards will be displayed.
23 be called adp5520-keys.
33 module will be called adp5588-keys.
43 module will be called adp5589-keys.
53 module will be called amikbd.
67 module will be called atakbd.
85 module will be called atkbd.
118 in the left-hand column will be interpreted as the corresponding key
122 right-hand column will be interpreted as the key shown in the
133 the module will be called qt1070
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | qe.txt | 4 NOTE: This is an interim binding; it should be updated to fit
8 as a complete entity (UCC, USB etc ). All of them should be siblings on
11 more nodes and properties would be extended in the future.
16 - compatible : should be "fsl,qe";
17 - model : precise model of the QE, Can be "QE", "CPM", or "CPM2"
29 that contains the firmware that should be uploaded for this QE.
52 - compatible : should be "fsl,qe-muram", "fsl,cpm-muram".
53 - mode : the could be "host" or "slave".
54 - ranges : Should be defined as specified in 1) to describe the
57 bus that can be allocated as data/parameter
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/imx/ |
| D | ldb.txt | 10 - #address-cells : should be <1>
11 - #size-cells : should be <0>
12 - compatible : should be "fsl,imx53-ldb" or "fsl,imx6q-ldb".
16 - gpr : should be <&gpr> on i.MX53 and i.MX6q.
37 - pinctrl-names : should be "default" on i.MX53, not used on i.MX6q
41 be configured - one input will be distributed on both outputs in dual
52 - reg : should be <0> or <1>
56 limitations, only one input port (port@[0,1]) can be used for each channel
58 On i.MX6, there should be four input ports (port@[0-3]) that correspond
60 A single output port (port@2 on i.MX5, port@4 on i.MX6) must be connected
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/pci/ |
| D | ralink,rt3883-pci.txt | 7 - compatible: must be "ralink,rt3883-pci"
13 address. The value must be 1.
16 of an address. The value must be 1.
24 Value must be either "disabled" or "okay".
38 address. The value must be 0. As such, 'interrupt-map' nodes do not
42 interrupt source. The value must be 1.
56 address. The value must be 0.
59 of an address. The value must be 2.
62 interrupt source. The value must be 1.
64 - device_type: must be "pci"
[all …]
|
| D | ti-pci.txt | 4 - compatible: Should be "ti,dra7-pcie""
6 - reg-names : The first entry must be "ti-conf" for the TI specific registers
7 The second entry must be "rc-dbics" for the designware pcie
9 The third entry must be "config" for the PCIe configuration space
11 - phy-names : must be "pcie-phy0", "pcie-phy1", "pcie-phyN".. based on the
15 - interrupts : Two interrupt entries must be specified. The first one is for
27 - gpios : Should be added if a gpio line is required to drive PERST# line
|
| /linux-4.4.14/drivers/misc/eeprom/ |
| D | Kconfig | 16 Unless you like data loss puzzles, always be sure that any chip
27 This driver can also be built as a module. If so, the module
28 will be called at24.
38 This driver can also be built as a module. If so, the module
39 will be called at25.
47 EEPROMs could theoretically be available on other devices as well.
49 This driver can also be built as a module. If so, the module
50 will be called eeprom.
60 All other features of this chip should be accessed via i2c-dev.
62 This driver can also be built as a module. If so, the module
[all …]
|
| /linux-4.4.14/Documentation/usb/ |
| D | mass-storage.txt | 6 provided by a regular file or a block device, access can be limited
16 a single memory/DMA buffer will be usable for bulk-in and bulk-out
18 there may be some with hardware restrictions that prevent a buffer
35 backing storage for each logical unit. There may be at most
37 be silently ignored. See also “luns” parameter.
40 be modified by any other process. This is because the host
41 assumes the data does not change without its knowledge. It may be
45 The size of the logical unit will be rounded down to a full
52 This parameter specifies whether each logical unit should be
58 backing file will be closed to simulate ejection and the logical
[all …]
|
| D | gadget_configfs.txt | 17 be connected to a USB Host to extend it with additional functions like a serial
26 Creating a gadget means deciding what configurations there will be
41 In order for this to work configfs must be available, so CONFIGFS_FS must be
51 made available through configfs can be seen here:
62 For each gadget to be created its corresponding directory must be created:
82 In order to have a place to store them, a strings subdirectory must be created
87 Then the strings can be specified:
97 directories must be created:
101 where <name> can be any string which is legal in a filesystem and the
110 Each configuration also needs its strings, so a subdirectory must be created
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/watchdog/ |
| D | atmel-wdt.txt | 6 - compatible: must be "atmel,at91sam9260-wdt".
15 seconds. This value should be less or equal to 16. It is used to
18 seconds. This value must be smaller than the max-heartbeat-sec value.
20 - atmel,watchdog-type : Should be "hardware" or "software". Hardware watchdog
23 - atmel,reset-type : Should be "proc" or "all".
27 - atmel,disable : Should be present if you want to disable the watchdog.
28 - atmel,idle-halt : Should be present if you want to stop the watchdog when
30 CAUTION: This property should be used with care, it actually makes the
35 - atmel,dbg-halt : Should be present if you want to stop the watchdog when
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c.txt | 4 This document describes generic bindings which can be used to describe I2C
10 - #address-cells - should be <1>. Read more about addresses below.
11 - #size-cells - should be <0>.
20 flags can be attached to the address. I2C_TEN_BIT_ADDRESS is used to mark a 10
22 of 0x50 and a 10 bit address of 0x050 which, in theory, can be on the same bus.
24 be devices ourselves.
29 These properties may not be supported by all drivers. However, if a driver
33 - wakeup-source - device can be used as a wakeup source.
45 binding, then primary interrupt will be used as wakeup interrupt.
|
| /linux-4.4.14/Documentation/power/ |
| D | swsusp-and-swap-files.txt | 7 (1) swap files need not be contiguous,
10 already taken care of by the swap-handling code, but (2) has to be taken into
13 In principle the location of a swap file's header may be determined with the
15 filesystem holding the swap file to be mounted, and if this filesystem is
16 journaled, it cannot be mounted during resume from disk. For this reason to
41 application in 2) (of course, this step may be carried out automatically
50 to a swap file allowing the resume to be initiated from an initrd or initramfs
54 partition. In particular, the swap file has to be active (ie. be present in
55 /proc/swaps) so that it can be used for suspending.
58 the location of its header need not be the same as before. Thus every time
[all …]
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | changesets.txt | 3 will be applied, or none of them will be. If an error occurs partway
4 through applying the changeset, then the tree will be rolled back to the
5 previous state. A changeset can also be removed after it has been
25 ensures there can only be one editor at a time.
29 be restored to the previous state
33 If a successfully applied changeset needs to be removed, it can be done
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | jz4780-dma.txt | 5 - compatible: Should be "ingenic,jz4780-dma"
8 - interrupt-parent: Should be the phandle of the interrupt controller that
10 - #dma-cells: Must be <2>. Number of integer cells in the dmas property of
16 need a specific channel. These channels will only be assigned when explicitly
18 can be configured to have special behaviour for NAND/BCH when using
43 2. Channel: If set to 0xffffffff, any available channel will be allocated for
44 the client. Otherwise, the exact channel specified will be used. The channel
45 should be reserved on the DMA controller using the ingenic,reserved-channels
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | atmel-flexcom.txt | 4 controller and an USART. Only one function can be used at a time and is chosen
8 - compatible: Should be "atmel,sama5d2-flexcom"
9 - reg: Should be the offset/length value for Flexcom dedicated
11 - clocks: Should be the Flexcom peripheral clock from PMC.
12 - #address-cells: Should be <1>
13 - #size-cells: Should be <1>
14 - ranges: Should be one range for the full I/O register region
16 - atmel,flexcom-mode: Should be one of the following values:
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/dsa/ |
| D | dsa.txt | 5 - compatible : Should be "marvell,dsa"
6 - #address-cells : Must be 2, first cell is the address on the MDIO bus
9 - #size-cells : Must be 0
10 - dsa,ethernet : Should be a phandle to a valid Ethernet device node
11 - dsa,mii-bus : Should be a phandle to a valid MDIO bus device node
24 number that must be unique in cascaded configurations
25 - #address-cells : Must be 1
26 - #size-cells : Must be 0
31 switch. Must be set if the switch can not detect
47 - link : Should be a list of phandles to another switch's DSA port.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-emc.txt | 4 - name : Should be emc
5 - #address-cells : Should be 1
6 - #size-cells : Should be 0
9 - nvidia,use-ram-code : If present, the sub-nodes will be addressed
11 set of tables can be present and said tables will be used
37 - name : Should be emc-tables
52 and they will always be used (based on which frequency is used).
61 these strappings can be read through a register in the SoC, and thus
65 - name : Should be emc-table
68 the valid frequency for which the table should be used (in kHz).
[all …]
|
| /linux-4.4.14/Documentation/power/regulator/ |
| D | consumer.txt | 24 Consumers can be supplied by more than one regulator e.g. codec consumer with
31 usually be called in your device drivers probe() and remove() respectively.
41 NOTE: The supply may already be enabled before regulator_enabled() is called.
57 regulator will only be disabled when the enabled reference count is zero.
59 Finally, a regulator can be forcefully disabled in the case of an emergency :-
64 consumers will be powered off.
70 Some consumer drivers need to be able to dynamically change their supply
82 NOTE: this can be called when the regulator is enabled or disabled. If called
87 The regulators configured voltage output can be found by calling :-
92 regulator is enabled or disabled and should NOT be used to determine regulator
[all …]
|
| /linux-4.4.14/Documentation/laptops/ |
| D | disk-shock-protection.txt | 29 Please note, however, that other components have to be set up on your
39 block/*/device/unload_heads in sysfs (here assumed to be mounted under
46 normal operation will be resumed. The maximal value accepted for a
48 -EOVERFLOW, but heads will be parked anyway and the timeout will be
58 of milliseconds remaining until normal operation will be resumed;
71 will be resumed.
74 milliseconds may raise expectations that cannot be satisfied in
77 that this will typically be within 500 milliseconds apparently has
81 confusion and should be discussed here. When a head park request has
83 controller port this device is attached to will be deferred. That is
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | pbias-regulator.txt | 5 - should be "ti,pbias-dra7" for DRA7
6 - should be "ti,pbias-omap2" for OMAP2
7 - should be "ti,pbias-omap3" for OMAP3
8 - should be "ti,pbias-omap4" for OMAP4
9 - should be "ti,pbias-omap5" for OMAP5
13 - regulator-name : should be
|
| D | max77686.txt | 4 More information can be found in ../mfd/max77686.txt file.
7 regulators that can be controlled over I2C.
9 Following properties should be present in main device node of the MFD chip.
12 - voltage-regulators : The regulators of max77686 have to be instantiated
21 The regulator node's name should be initialized with a string
29 Regulators which can be turned off during system suspend:
34 LDO20, LDO21, LDO22, BUCK8 and BUCK9 can be configured to GPIO enable
35 control. To turn this feature on this property must be added to the regulator
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | emc2103 | 21 readings can be divided by a programmable divider (1, 2, 4 or 8) to give
22 the readings more range or accuracy. Not all RPM values can accurately be
27 should be written to fan1_target and pwm1_enable should be set to 3.
30 be connected to two anti-parallel diodes. These values can be read
32 will show as "fault". The module parameter "apd=0" can be used to suppress
|
| D | acpi_power_meter | 27 Both power[1-*]_average_{min,max} must be set before the trip points will work.
28 When both of them are set, an ACPI event will be broadcast on the ACPI netlink
29 socket and a poll notification will be sent to the appropriate
38 average power consumption exceeds the cap, an ACPI event will be broadcast on
39 the netlink event socket and a poll notification will be sent to the
44 There are a few other ACPI notifications that can be sent by the firmware. In
45 all cases the ACPI event will be broadcast on the ACPI netlink event socket as
49 power[1-*]_cap will be notified if the firmware changes the power cap.
50 power[1-*]_interval will be notified if the firmware changes the averaging
|
| /linux-4.4.14/drivers/staging/gdm724x/ |
| D | Kconfig | 10 It exposes 4 network devices to be used per PDN and 2 tty devices to be
12 The modules will be called gdmulte.ko and gdmtty.ko
14 GCT-ATCx can be used for AT Commands
15 GCT-DMx can be used for LTE protocol monitoring
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | tca6507.txt | 4 - compatible : should be : "ti,tca6507".
5 - #address-cells: must be 1
6 - #size-cells: must be 0
10 - gpio-controller: allows lines to be used as output-only GPIOs.
11 - #gpio-cells: if present, must not be 0.
17 - reg : number of LED line (could be from 0 to 6)
|
| /linux-4.4.14/sound/pci/ |
| D | Kconfig | 21 will be called snd-ad1889.
33 will be called snd-als300
47 will be called snd-als4000.
61 will be called snd-ali5451.
73 will be called snd-asihpi.
84 will be called snd-atiixp.
94 will be called snd-atiixp-modem.
108 will be called snd-au8810.
121 will be called snd-au8820.
135 will be called snd-au8830.
[all …]
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | kbuild.txt | 20 will be used in all cases where kbuild does preprocessing including
59 Set the kbuild verbosity. Can be assigned same values as "V=...".
67 The directory can be specified in several ways:
77 The output directory can also be specified using "O=...".
85 The value of KBUILD_DEBARCH is assumed (not checked) to be a valid Debian
90 Set ARCH to the architecture to be built.
100 CROSS_COMPILE can be a part of the filename or the full path.
121 The script will be called with the following arguments:
140 The value can be overridden in which case the default value is ignored.
146 makefile but the argument can be passed to make if needed.
[all …]
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | ALS | 16 - standalone MPU401 support may be required for some cards; for the
18 Since the ALS-007/100/200 are PnP cards, ISAPnP support should probably be
20 be required to configure the card before the sound modules are loaded.
26 section. This should all be correctly configured by the kernel; if problems
30 synth device can be accessed using the "opl3" module.
33 of the card's resources should be passed to the kernel modules ("sb", "opl3"
34 and "mpu401") using the module parameters. When configuring an ALS-007, be
36 requires they be different. For "sb", "io", "irq" and "dma" should be set
38 isapnp. "dma16" should be explicitly set to "-1" for an ALS-007 since this
41 "mpu_io" should be set to 0. The "io" parameter of the "opl3" module should
[all …]
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-platform-chipidea-usb-otg | 5 Can be set and read.
6 Set a_bus_req(A-device bus request) input to be 1 if
8 and to be 0 when the application no longer wants to use
10 be set to 1 by kernel in response to remote wakeup signaling
22 Can be set and read
26 the a_bus_req shall be 0.
37 Can be set and read.
41 work as host and decides to switch back to be peripheral.
52 Only can be set.
|
| D | sysfs-power | 15 labels, which may be "mem", "standby", "freeze" and "disk"
22 not be present depending on the capabilities of the
23 platform. "freeze" can only be present if "standby" is
41 the name of the method by which the system will be put to
43 'firmware' - means that the memory image will be saved to disk
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
50 the system will be powered off.
51 'reboot' - the memory image will be saved by the kernel and
[all …]
|
| D | sysfs-platform-kim | 20 UART configurations, so the baud-rate needs to be set
31 entry most often should be 1, the host's UART is required
33 entry can be made use of for exceptions.
44 entry. This entry would be polled upon by the user-space
46 by the sysfs_notify. The value would be '1' when UART needs
47 to be opened/ldisc installed, and would be '0' when UART
48 is no more required and needs to be closed.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 3 Partitions can be represented by sub-nodes of an mtd device. This can be used
8 The partition table should be a subnode of the mtd node and should be named
10 - compatible : (required) must be "fixed-partitions"
16 string are not considered partitions, as they may be used for other bindings.
18 #address-cells & #size-cells must both be present in the partitions subnode of the
32 partition should only be mounted read-only. This is usually used for flash
33 partitions containing early-boot firmware images or data which should not be
|
| /linux-4.4.14/arch/um/ |
| D | Kconfig.char | 26 and there is never any data to be read.
32 lines to host portals. They may be accessed with 'telnet <host>
33 <port number>'. Any number of consoles and serial lines may be
35 you telnet to that portal will be unpredictable.
45 will be announced in the kernel message log.
61 lines to xterms. Each UML device so assigned will be brought up in
74 will be attached by default. This value can be overridden from the
84 except the main console will be attached by default. This value can
85 be overridden from the command line. The default value is "xterm",
88 this if you expect the UML that you build to be run in environments
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | st,sta350.txt | 9 - reset-gpios: a GPIO spec for the reset pin. If specified, it will be
13 it will be deasserted before communication to the codec
27 If parameter is missing, mode 0 will be enabled.
28 This property has to be specified as '/bits/ 8' value.
37 This properties have to be specified as '/bits/ 8' values.
46 If present, then fault recovery will be enabled.
50 configured. Must be one of these values:
60 The value must be in the range of 0..300, and only
80 channels. If not present, normal PWM spped mode (384 kHz) will be used.
90 If present, a mute output will be activated in ase the volume will
[all …]
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | spear-pcie-gadget.txt | 23 This driver has several nodes which can be read/written by configfs interface.
26 type. This driver can be used to show spear's PCIe device capability.
47 int_type :write interrupt type to be configured and (int_type could be
52 send_msi :write MSI vector to be sent.
53 vendor_id :write vendor id(hex) to be programmed.
54 device_id :write device id(hex) to be programmed.
62 bar0_data :write data to be written at bar0_rw_offset.
85 memory, which is to be made visible to PCIe host. Similarly any other peripheral
86 can also be made visible to PCIe host. E.g., if you program base address of UART
87 as BAR0 address then when this device will be connected to a host, it will be
[all …]
|
| /linux-4.4.14/drivers/media/i2c/ |
| D | Kconfig | 39 module will be called tvaudio.
48 module will be called tda7432.
57 module will be called tda9840.
66 module will be called tea6415c.
75 module will be called tea6420.
84 module will be called msp3400.
94 module will be called cs5345.
104 module will be called cs53l32a.
113 module will be called tlv320aic23b.
122 module will be called uda1342.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 6 "fsl,mpc8349-pmc" should be listed for any chip whose PMC is
7 compatible. "fsl,mpc8313-pmc" should also be listed for any chip
10 "fsl,mpc8548-pmc" should be listed for any chip whose PMC is
11 compatible. "fsl,mpc8536-pmc" should also be listed for any chip
14 "fsl,mpc8641d-pmc" should be listed for any chip whose PMC is
33 this is a phandle to an "fsl,gtm" node on which timer 4 can be used as
39 that is set in the cell, the corresponding bit in SCCR will be saved
44 which will be ORed into PMCDR upon suspend, and cleared from PMCDR
50 first of which will be ORed into DEVDISR (and the second into
51 DEVDISR2, if present -- this cell should be zero or absent if the
|
| D | mpic-msgr.txt | 3 This binding specifies what properties must be available in the device tree
10 block. The type shall be <string-list> and the value shall be of the form
15 message register block's addressable register space. The type shall be
20 cell is interrupt-number and second cell is level-sense. The type shall be
29 be <u32>. If not present, then all of the message registers in the block
34 An alias should be created for every message register block. They are not
36 may require aliases to be present. Aliases are of the form
|
| /linux-4.4.14/Documentation/devicetree/bindings/edac/ |
| D | apm-xgene-edac.txt | 14 - compatible : Shall be "apm,xgene-edac".
19 - reg : First resource shall be the CPU bus (PCP) resource.
24 - compatible : Shall be "apm,xgene-edac-mc".
25 - reg : First resource shall be the memory controller unit
30 - compatible : Shall be "apm,xgene-edac-pmd" or
32 - reg : First resource shall be the PMD resource.
36 - compatible : Shall be "apm,xgene-edac-l3" or
38 - reg : First resource shall be the L3 EDAC resource.
41 - compatible : Shall be "apm,xgene-edac-soc-v1" for revision 1 or
44 - reg : First resource shall be the SoC EDAC resource.
|
| /linux-4.4.14/Documentation/devicetree/bindings/hwmon/ |
| D | max6697.txt | 5 Should be one of
21 Set to disable SMBus timeout. If not specified, SMBus timeout will be
25 Extended temperature will be disabled if not specified.
29 Beta compensation will be disabled if not specified.
33 If not specified, alert will be enabled for all channels.
38 If not specified, over-temperature reporting will be enabled for all
46 If not specified, resistance cancellation will be disabled for all
52 Transistor ideality will be initialized to default (1.008) if not
|
| /linux-4.4.14/drivers/usb/dwc2/ |
| D | Kconfig | 9 linked modules, the core module will be called dwc2.ko, the PCI
10 bus interface module (if you have a PCI bus system) will be
12 controllers directly connected to the CPU) will be called
14 will be an additional module named dwc2.ko.
32 comment "Gadget/Dual-role mode requires USB Gadget support to be enabled"
41 USB_GADGET to be enabled.
49 the role will be determined by the cable that gets plugged-in. This
50 option requires USB_GADGET to be enabled.
87 Say N here to disable (verbose) debugging messages to be
89 non-periodic transfers, but of course the debug logs will be
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/samsung/ |
| D | exynos-adc.txt | 13 - compatible: Must be "samsung,exynos-adc-v1"
15 Must be "samsung,exynos-adc-v2" for
17 Must be "samsung,exynos3250-adc" for
19 Must be "samsung,exynos7-adc" for
21 Must be "samsung,s3c2410-adc" for
23 Must be "samsung,s3c2416-adc" for
25 Must be "samsung,s3c2440-adc" for
27 Must be "samsung,s3c2443-adc" for
29 Must be "samsung,s3c6410-adc" for
51 Note: child nodes can be added for auto probing from device tree.
[all …]
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | rpc-cache.txt | 8 a wide variety of values to be caches.
14 Examples of caches that are likely to be needed are:
77 Format a request to be send to user-space for an item
78 to be instantiated. *bpp is a buffer of size *blen.
79 bpp should be moved forward over the encoded message,
80 and *blen should be reduced to show how much free
91 3/ A cache needs to be registered using cache_register(). This
92 includes it on a list of caches that will be regularly
100 This will be passed to ->match to identify the target entry. If no
101 entry is found, a new entry will be create, added to the cache, and
[all …]
|
| D | knfsd-stats.txt | 16 '#' character are comments intended for humans and should be ignored
24 /proc/fs/nfsd filesystem is mounted (it almost always should be).
41 currently cannot be larger than the number of CPUs in the system.
42 Note that in the default case there will be a single thread pool
49 sunrpc server layer that new data may be available on a transport
54 on the wire, this may be either more or less than the number
66 network-facing work to be done but it couldn't be done immediately,
82 thing. The ideal rate of change for this counter will be close
91 threads configured than can be used by the NFS workload. This is
92 a clue that the number of nfsd threads can be reduced without
[all …]
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | GPIO.txt | 23 be removed in favour of this common access method.
26 listed below will be removed (they may be marked as __deprecated
54 2) The s3c2410_gpio_cfgpin() can be directly replaced with s3c_gpio_cfgpin()
59 s3c2410_gpio_pullup(x, 1) can be easily translated to the
66 which may be required if this becomes a problem.
68 4) s3c2410_gpio_setpin() can be replaced by gpio_set_value(), the old call
70 direction should be changed before using gpio_set_value().
75 would return the value the pin is supposed to be outputting).
77 6) s3c2410_gpio_getirq() should be directly replaceable with the
98 the GPIO functions which pin is to be used.
[all …]
|
| /linux-4.4.14/drivers/iio/pressure/ |
| D | Kconfig | 17 will be called bmp280.
31 will be called hid-sensor-press.
41 will be called mpl115.
53 will be called mpl3115.
62 be called ms5611_core.
71 be called ms5611_i2c.
80 be called ms5611_spi.
92 This driver can also be built as a module. If so, the module will
93 be called ms5637.
106 This driver can also be built as a module. If so, these modules
[all …]
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 14 could be useful for a networked machine that needs to come back
46 get killed. If you say Y here, the watchdog cannot be stopped once
66 module will be called softdog.
78 which will be called da9052_wdt.
88 This driver can also be built as a module. If so, the module
89 will be called da9055_wdt.
98 This driver can be built as a module. The module name is da9063_wdt.
107 This driver can be built as a module. The module name is da9062_wdt.
123 to be triggered.
124 If you say yes here, the initcall level would be raised to
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | composite.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
9 of which can be selected as output, this behaves exactly as [2]
13 a gating function which can be used to enable and disable the output
16 The binding must provide a list of the component clocks that shall be
17 merged to this clock. The component clocks shall be of one of the
26 - compatible : shall be: "ti,composite-clock"
28 - #clock-cells : from common clock binding; shall be set to 0.
|
| D | dra7-atl.txt | 3 The ATL IP is used to generate clock to be used to synchronize baseband and
5 functional clock but can be configured to provide different clocks.
9 In order to provide the support for ATL and it's output clocks (which can be used
14 To be able to integrate the ATL clocks with DT clock tree.
15 Provides ccf level representation of the ATL clocks to be used by drivers.
23 - compatible : shall be "ti,dra7-atl-clock"
24 - #clock-cells : from common clock binding; shall be set to 0.
32 - compatible : shall be "ti,dra7-atl"
36 - clock-names : Shall be set to "fck"
37 - ti,hwmods : Shall be set to "atl"
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | cache.txt | 33 may be out of date or kept in sync with the copy on the cache device
51 This information could be put on the cache device, but having it
54 be used by a single cache device.
61 using block sizes of 256KB - 1024KB. The block size must be between 64
65 something of a compromise. For instance, a small part of a block may be
66 getting hit a lot, yet the whole block will be promoted to the cache.
78 cached will go only to the cache and the block will be marked dirty in
86 to be coherent with the origin device, then all reads are served from
89 block invalidates. To enable passthrough mode the cache must be clean.
90 Passthrough mode allows a cache device to be activated without having to
[all …]
|
| /linux-4.4.14/drivers/memstick/host/ |
| D | Kconfig | 12 Say Y here if you want to be able to access MemoryStick cards with
21 module will be called tifm_ms.
28 Say Y here if you want to be able to access MemoryStick cards with
32 module will be called jmb38x_ms.
39 Say Y here if you want to be able to access MemoryStick cards with
44 be called r592.
54 be called rtsx_pci_ms.
64 be called rts5139_ms.
|
| /linux-4.4.14/drivers/input/serio/ |
| D | Kconfig | 17 module will be called serio.
40 module will be called i8042.
55 module will be called serport.
68 module will be called ct82c710.
86 module will be called parkbd.
97 module will be called rpckbd.
107 be called at32psif.
123 over which HP PS/2 keyboards and PS/2 mice may be connected.
129 module will be called gscps2.
141 The SDC may also be connected to a battery-backed real-time
[all …]
|
| /linux-4.4.14/drivers/misc/ |
| D | Kconfig | 31 This driver can also be built as a module. If so, the module
32 will be called ad525x_dpot.
41 module will be called ad525x_dpot-i2c.
52 module will be called ad525x_dpot-spi.
72 may be used as a clock event device supporting oneshot mode
84 TC can be used for other purposes, such as PWM generation and
103 processor. The driver is meant to be used in conjunction with
107 this feature serial driver support (CONFIG_SERIAL_8250) must be
110 WARNING: This software may not be supported or function
124 If you choose to build module, its name will be phantom. If unsure,
[all …]
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 22 Internet Drafts may be updated, replaced, or obsoleted by other documents
37 IP datagrams to be labeled with security classifications. This option
56 security policy. Support for additional security policies shall be
76 This option permits security related information to be passed between
82 mapping to hosts within the authority's domain. These mappings may be
87 This option MUST be copied on fragmentation. This option appears at most
88 once in a datagram. All multi-octet fields in the option are defined to be
148 actual security information to be passed. All multi-octet fields in a tag
149 are defined to be transmitted in network byte order. Like the DOI
154 be guaranteed if CIPSO is not the first IP option.
[all …]
|
| /linux-4.4.14/drivers/leds/trigger/ |
| D | Kconfig | 7 be configured via sysfs. If unsure, say Y.
15 This allows LEDs to be controlled by a programmable timer
16 via sysfs. Some LED hardware can be programmed to start
41 This allows LEDs to be controlled by IDE disk activity.
48 This allows LEDs to be controlled by a CPU load average.
57 This allows LEDs to be controlled as a backlight device: they
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
89 This allows LEDs to be initialised in the ON state.
[all …]
|
| /linux-4.4.14/sound/isa/ |
| D | Kconfig | 37 will be called snd-adlib.
52 will be called snd-ad1816a.
65 will be called snd-ad1848.
80 will be called snd-als100.
93 will be called snd-azt1605.
106 will be called snd-azt2316.
120 will be called snd-azt2320.
132 will be called snd-cmi8328.
145 will be called snd-cmi8330.
156 will be called snd-cs4231.
[all …]
|
| /linux-4.4.14/Documentation/mn10300/ |
| D | ABI.txt | 12 The stack grows downwards, and should always be 32-bit aligned. There are
25 registers and the stack. If the first argument is a 64-bit value, it will be
27 is, the second will be passed entirely on the stack and D1 will be unused.
30 word. For example, two byte-sized arguments will always be passed in separate
75 array, then a hidden first argument will be passed to the callee by the caller:
78 memory, and no value will be returned in D0 or A0.
85 The values in certain registers may be clobbered by the callee, and other
86 values must be saved:
114 will be kept in the E2 register, and that register will be marked
125 be carried globally in an register, it can use:
|
| /linux-4.4.14/drivers/staging/android/ |
| D | TODO | 4 - rename files to be not so "generic"
10 - Remove ION_IOC_SYNC: Flushing for devices should be purely a kernel internal
11 interface on top of dma-buf. flush_for_device needs to be added to dma-buf
14 vendor trees. Should be replaced with an ioctl on the dma-buf to expose the
18 explicit coherency management mode to flush_for_device to be used by drivers
22 since ion would just be the central allocator for shared buffers.
24 such cma regions must already be used by some device for dma. I.e. ion only
|
| /linux-4.4.14/Documentation/rapidio/ |
| D | rapidio.txt | 83 RapidIO interconnect specification defines features that may be used to provide
85 common services may act separately from device-specific drivers or be used by
87 which implements Ethernet-over-RapidIO interface. Because only one driver can be
88 registered for a device, all common RapidIO services have to be registered as
101 an enumeration and/or discovery routine may be called automatically or
104 RapidIO subsystem can be configured to be built as a statically linked or
116 define how any given method can be attached to available RapidIO mports:
122 (a) Statically linked enumeration and discovery process can be started
129 and are waiting for enumeration to be completed.
131 endpoint waits for enumeration to be completed. If the specified timeout
[all …]
|
| /linux-4.4.14/drivers/uio/ |
| D | Kconfig | 5 Enable this to allow the userspace driver core code to be
8 to be written in userspace. Note that a small kernel driver
21 all of the heavy lifting and can be found at:
25 will be called uio_cif.
47 Memory regions can be specified with the same platform device
49 be specified.
68 can be used to read and write the ports:
72 If you compile this as a module, it will be called uio_aec.
79 Automata GmbH. The userspace part of this driver will be
85 If you compile this as a module, it will be called uio_sercos3.
[all …]
|
| /linux-4.4.14/drivers/iio/dac/ |
| D | Kconfig | 17 module will be called ad5064.
27 To compile this driver as module choose M here: the module will be called
40 To compile this driver as module choose M here: the module will be called
50 To compile this driver as module choose M here: the module will be called
63 module will be called ad5446.
73 module will be called ad5449.
83 module will be called ad5504.
101 module will be called ad5686.
112 module will be called ad5755.
122 module will be called ad5764.
[all …]
|
| /linux-4.4.14/drivers/input/ |
| D | Kconfig | 14 it to be available to applications. This includes standard PS/2
24 module will be called input.
39 module will be called input-leds.
52 module will be called ff-memless.
65 module will be called input-polldev.
78 module will be called sparse-keymap.
91 module will be called matrix-keymap.
99 Say Y here if you want your mouse to be accessible as char devices
102 programs (including SVGAlib, GPM and X) will be able to use your
108 module will be called mousedev.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 5 controllers. Each pin controller must be represented as a node in device tree,
9 designated client devices. Again, each client device must be represented as a
24 Note that pin controllers themselves may also be client devices of themselves.
37 property exists to define the pin configuration. Each state may also be
41 Each client device's own binding determines the set of states that must be
43 IDs that must be provided, or whether to define the set of state names that
44 must be provided.
48 node. These referenced pin configuration nodes must be child
51 controllers may be configured, or so that a state may be built
57 In some cases, it may be useful to define a state, but for it
[all …]
|
| /linux-4.4.14/Documentation/prctl/ |
| D | seccomp_filter.txt | 33 mechanism for minimizing the exposed kernel surface. It is meant to be
35 behavior and information flow should be managed with a combination of
39 system calls in socketcall() is allowed, for instance) which could be
47 CONFIG_HAVE_ARCH_SECCOMP_FILTER, then filters may be added as below:
52 The BPF program will be executed over struct seccomp_data
55 acceptable values to inform the kernel which action should be
66 processes will be constrained to the same filters and system
71 true, -EACCES will be returned. This requirement ensures that filter
72 programs cannot be applied to child processes with greater privileges
76 additional filters may be layered on which will increase evaluation
[all …]
|
| /linux-4.4.14/drivers/input/joystick/ |
| D | Kconfig | 9 and the list of supported devices will be displayed. This option
32 module will be called analog.
42 module will be called a3d.
52 module will be called adi.
61 module will be called cobra.
71 module will be called gf2k.
81 module will be called grip.
91 module will be called grip_mp.
101 module will be called guillemot.
111 module will be called interact.
[all …]
|
| /linux-4.4.14/drivers/char/hw_random/ |
| D | Kconfig | 12 module will be called rng-core. This provides a device
31 is to be read no faster than, for example, once a second;
35 module will be called timeriomem-rng.
48 module will be called intel-rng.
61 module will be called amd-rng.
74 module will be called atmel-rng.
87 module will be called bcm63xx-rng
100 module will be called bcm2835-rng
113 module will be called iproc-rng200
126 module will be called geode-rng.
[all …]
|
| /linux-4.4.14/drivers/usb/serial/ |
| D | Kconfig | 18 module will be called usbserial.
26 If you say Y here, it will be possible to use a USB to serial
29 allows logins in single user mode). This could be useful if some
33 (/dev/tty0) will still be used as the system console by default, but
51 support" be compiled as a module for this driver to be used
73 will be called usb-serial-simple.
81 will be called aircable.
90 module will be called ark3116
100 module will be called belkin_sa.
109 module will be called ch341.
[all …]
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | unified-hierarchy.txt | 7 their rationales. It will eventually be merged into the main cgroup
44 type controllers such as freezer which can be useful in all
45 hierarchies can only be used in one. The issue is exacerbated by the
46 fact that controllers can't be moved around once hierarchies are
51 In practice, these issues heavily limit which controllers can be put
64 There's no limit on how many hierarchies there may be, which means
65 that a task's cgroup membership can't be described in finite length.
72 of hierarchies other controllers would be on, each controller has to
81 be collapsed from leaf towards root when viewed from specific
97 Currently, unified hierarchy can be mounted with the following mount
[all …]
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | kernel.txt | 12 The files in this directory can be used to tune and monitor
14 kernel. Since some of the files _can_ be used to screw up your
115 See Doc*/kernel/power/video.txt, it allows mode of video boot to be
122 This variable has no effect and may be removed in future kernel
192 and core_uses_pid is set, then .PID will be appended to
208 %e executable filename (may be shortened)
212 the rest of the pattern as a command to run. The core dump will be
230 processes may be piped to user space applications in parallel. If
233 special value, indicating that unlimited processes may be captured in
245 and core_uses_pid is set, then .PID will be appended to
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/soc/rockchip/ |
| D | power_domain.txt | 3 Rockchip processors include support for multiple power domains which can be
7 - compatible: Should be one of the following.
10 Should be 1 for multiple PM domains.
11 - #address-cells: Should be 1.
12 - #size-cells: Should be 0.
17 - clocks (optional): phandles to clocks which need to be enabled while power domain
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/ |
| D | par_io.txt | 5 device that using parallel I/O ports, a child node should be created.
10 - device_type : should be "par_io".
25 Note that "par_io" nodes are obsolete, and should not be used for
26 the new device trees. Instead, each Par I/O bank should be represented
30 - #gpio-cells : should be "2".
31 - compatible : should be "fsl,<chip>-qe-pario-bank",
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/st/ |
| D | st,clkgen-vcc.txt | 4 output clocks. Not all inputs or outputs have to be in use in a
5 particular instantiation. Each output can be individually enabled,
15 - compatible : shall be:
19 - #clock-cells : from common clock binding; shall be set to 1.
27 have to be used in the SoC. If a clock name is left as
28 an empty string then no clock will be created for the
30 16 strings are provided then no clocks will be created
|
| /linux-4.4.14/Documentation/devicetree/bindings/spi/ |
| D | spi-mt65xx.txt | 4 - compatible: should be one of the following.
9 - #address-cells: should be 1.
11 - #size-cells: should be 0.
18 The first should be one of the following. It's PLL.
25 The second should be <&topckgen CLK_TOP_SPI_SEL>. It's clock mux.
28 - clock-names: shall be "parent-clk" for the parent clock, "sel-clk" for the
35 controller used. This is a array, the element value should be 0~3,
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-mvebu.txt | 5 - compatible : Should be "marvell,orion-gpio", "marvell,mv78200-gpio"
6 or "marvell,armadaxp-gpio". "marvell,orion-gpio" should be used for
8 370. "marvell,mv78200-gpio" should be used for the Discovery
9 MV78200. "marvel,armadaxp-gpio" should be used for all Armada XP
18 managed by this GPIO bank. There can be more than one interrupt
25 interrupt source. Should be two.
38 - #gpio-cells: Should be two. The first cell is the pin number. The
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi.txt | 7 It can also be found at:
12 The scsi support in the linux kernel can be modularized in a number of
18 The scsi core support can be a module (scsi_mod.o), or it can be built into
19 the kernel. If the core is a module, it must be the first scsi module
20 loaded, and if you unload the modules, it will have to be the last one
25 The individual upper and lower level drivers can be loaded in any order
29 level drivers to support the various assorted devices which can be
38 Adaptec. Almost all lower level drivers can be built either as modules or
|