| /linux-4.4.14/drivers/spi/ |
| D | spi-atmel.c | 340 static bool atmel_spi_is_v2(struct atmel_spi *as) in atmel_spi_is_v2() argument
342 return as->caps.is_spi2; in atmel_spi_is_v2()
365 static void cs_activate(struct atmel_spi *as, struct spi_device *spi) in cs_activate() argument
371 if (atmel_spi_is_v2(as)) { in cs_activate()
372 spi_writel(as, CSR0 + 4 * spi->chip_select, asd->csr); in cs_activate()
376 spi_writel(as, CSR0, asd->csr); in cs_activate()
377 if (as->caps.has_wdrbt) { in cs_activate()
378 spi_writel(as, MR, in cs_activate()
384 spi_writel(as, MR, in cs_activate()
390 mr = spi_readl(as, MR); in cs_activate()
[all …]
|
| /linux-4.4.14/drivers/net/wireless/ath/ath5k/ |
| D | ani.c | 223 ath5k_ani_raise_immunity(struct ath5k_hw *ah, struct ath5k_ani_state *as, in ath5k_ani_raise_immunity() argument
232 if (as->noise_imm_level < ATH5K_ANI_MAX_NOISE_IMM_LVL) { in ath5k_ani_raise_immunity()
233 ath5k_ani_set_noise_immunity_level(ah, as->noise_imm_level + 1); in ath5k_ani_raise_immunity()
239 as->spur_level < ah->ani_state.max_spur_level) { in ath5k_ani_raise_immunity()
240 ath5k_ani_set_spur_immunity_level(ah, as->spur_level + 1); in ath5k_ani_raise_immunity()
246 if (as->firstep_level < ATH5K_ANI_MAX_FIRSTEP_LVL) in ath5k_ani_raise_immunity()
247 ath5k_ani_set_firstep_level(ah, as->firstep_level + 1); in ath5k_ani_raise_immunity()
262 if (ofdm_trigger && as->ofdm_weak_sig) { in ath5k_ani_raise_immunity()
268 if (as->firstep_level < ATH5K_ANI_MAX_FIRSTEP_LVL) { in ath5k_ani_raise_immunity()
269 ath5k_ani_set_firstep_level(ah, as->firstep_level + 1); in ath5k_ani_raise_immunity()
[all …]
|
| /linux-4.4.14/drivers/char/ |
| D | apm-emulation.c | 198 struct apm_user *as; in queue_event() local
201 list_for_each_entry(as, &apm_user_list, list) { in queue_event()
202 if (as->reader) in queue_event()
203 queue_add_event(&as->queue, event); in queue_event()
211 struct apm_user *as = fp->private_data; in apm_read() local
218 if (queue_empty(&as->queue) && fp->f_flags & O_NONBLOCK) in apm_read()
221 wait_event_interruptible(apm_waitqueue, !queue_empty(&as->queue)); in apm_read()
223 while ((i >= sizeof(event)) && !queue_empty(&as->queue)) { in apm_read()
224 event = queue_get_event(&as->queue); in apm_read()
231 if (as->suspend_state == SUSPEND_PENDING && in apm_read()
[all …]
|
| D | Kconfig | 77 To compile this driver as a module, choose M here: the module
88 OTP pages. This is dangerous by nature as you can only program
90 need it so as to not inadvertently clobber data.
99 box (as opposed to using a serial printer; if the connector at the
108 To compile this driver as a module, choose M here and read
124 If you want kernel messages to be printed out as they occur, you
150 To compile this driver as a module, choose M here: the
164 Also serves as a general-purpose serial device for data
191 It is also possible to say M here to build it as a module (ds1620)
204 This is most useful for applications, as yet unwritten, which
[all …]
|
| /linux-4.4.14/drivers/iommu/ |
| D | tegra-smmu.c | 262 struct tegra_smmu_as *as; in tegra_smmu_domain_alloc() local
267 as = kzalloc(sizeof(*as), GFP_KERNEL); in tegra_smmu_domain_alloc()
268 if (!as) in tegra_smmu_domain_alloc()
271 as->attr = SMMU_PD_READABLE | SMMU_PD_WRITABLE | SMMU_PD_NONSECURE; in tegra_smmu_domain_alloc()
273 as->pd = alloc_page(GFP_KERNEL | __GFP_DMA | __GFP_ZERO); in tegra_smmu_domain_alloc()
274 if (!as->pd) { in tegra_smmu_domain_alloc()
275 kfree(as); in tegra_smmu_domain_alloc()
279 as->count = kcalloc(SMMU_NUM_PDE, sizeof(u32), GFP_KERNEL); in tegra_smmu_domain_alloc()
280 if (!as->count) { in tegra_smmu_domain_alloc()
281 __free_page(as->pd); in tegra_smmu_domain_alloc()
[all …]
|
| /linux-4.4.14/arch/xtensa/include/asm/ |
| D | cacheasm.h | 48 .macro __loop_cache_range ar as at insn line_width
51 add \as, \as, \at
53 __loops \ar, \as, \at, \line_width
132 .macro ___flush_invalidate_dcache_range ar as at
135 __loop_cache_range \ar \as \at dhwbi XCHAL_DCACHE_LINEWIDTH
141 .macro ___flush_dcache_range ar as at
144 __loop_cache_range \ar \as \at dhwb XCHAL_DCACHE_LINEWIDTH
150 .macro ___invalidate_dcache_range ar as at
153 __loop_cache_range \ar \as \at dhi XCHAL_DCACHE_LINEWIDTH
159 .macro ___invalidate_icache_range ar as at
[all …]
|
| D | asmmacro.h | 65 .macro __loops ar, as, at, incr_log2, mask_log2, cond, ncond
69 addi \at, \as, (1 << \incr_log2) - 1
79 extui \at, \as, \incr_log2, \mask_log2
82 srli \at, \as, \incr_log2
93 add \at, \ar, \as
104 .macro __loopt ar, as, at, incr_log2
107 sub \at, \as, \ar
123 .macro __loop as
126 loop \as, 99f
137 .macro __endl ar, as
[all …]
|
| /linux-4.4.14/arch/x86/kernel/ |
| D | apm_32.c | 1164 static int queue_empty(struct apm_user *as) in queue_empty() argument
1166 return as->event_head == as->event_tail; in queue_empty()
1169 static apm_event_t get_queued_event(struct apm_user *as) in get_queued_event() argument
1171 if (++as->event_tail >= APM_MAX_EVENTS) in get_queued_event()
1172 as->event_tail = 0; in get_queued_event()
1173 return as->events[as->event_tail]; in get_queued_event()
1178 struct apm_user *as; in queue_event() local
1183 for (as = user_list; as != NULL; as = as->next) { in queue_event()
1184 if ((as == sender) || (!as->reader)) in queue_event()
1186 if (++as->event_head >= APM_MAX_EVENTS) in queue_event()
[all …]
|
| /linux-4.4.14/drivers/usb/core/ |
| D | devio.c | 276 struct async *as; in alloc_async() local
278 as = kzalloc(sizeof(struct async), GFP_KERNEL); in alloc_async()
279 if (!as) in alloc_async()
281 as->urb = usb_alloc_urb(numisoframes, GFP_KERNEL); in alloc_async()
282 if (!as->urb) { in alloc_async()
283 kfree(as); in alloc_async()
286 return as; in alloc_async()
289 static void free_async(struct async *as) in free_async() argument
293 put_pid(as->pid); in free_async()
294 if (as->cred) in free_async()
[all …]
|
| /linux-4.4.14/sound/usb/ |
| D | stream.c | 82 static void snd_usb_init_substream(struct snd_usb_stream *as, in snd_usb_init_substream() argument
86 struct snd_usb_substream *subs = &as->substream[stream]; in snd_usb_init_substream()
91 subs->stream = as; in snd_usb_init_substream()
93 subs->dev = as->chip->dev; in snd_usb_init_substream()
94 subs->txfr_quirk = as->chip->txfr_quirk; in snd_usb_init_substream()
95 subs->tx_length_quirk = as->chip->tx_length_quirk; in snd_usb_init_substream()
99 snd_usb_set_pcm_ops(as->pcm, stream); in snd_usb_init_substream()
327 struct snd_usb_stream *as; in snd_usb_add_audio_stream() local
332 list_for_each_entry(as, &chip->pcm_list, list) { in snd_usb_add_audio_stream()
333 if (as->fmt_type != fp->fmt_type) in snd_usb_add_audio_stream()
[all …]
|
| /linux-4.4.14/include/linux/ |
| D | util_macros.h | 4 #define __find_closest(x, a, as, op) \ argument
6 typeof(as) __fc_i, __fc_as = (as) - 1; \
26 #define find_closest(x, a, as) __find_closest(x, a, as, <=) argument
38 #define find_closest_descending(x, a, as) __find_closest(x, a, as, >=) argument
|
| /linux-4.4.14/Documentation/pcmcia/ |
| D | driver-changes.txt | 2 * pcmcia_loop_config() and autoconfiguration (as of 2.6.36)
14 * pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
16 as it mirrors pcmcia_disable_device(). Configuration settings are now
20 * pcmcia_request_window changes (as of 2.6.36)
27 * pcmcia_request_io changes (as of 2.6.36)
34 * No dev_info_t, no cs_types.h (as of 2.6.36)
36 in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
39 * No dev_node_t (as of 2.6.35)
42 * New IRQ request rules (as of 2.6.35)
53 * no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)
[all …]
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | ufs.txt | 18 default value, supported as read-only
21 supported as read-write
24 supported as read-write
29 supported as read-write
32 supported as read-write
35 supported as read-only
39 supported as read-only
43 supported as read-only
47 supported as read-only
|
| D | f2fs.txt | 5 NAND flash memory-based storage devices, such as SSD, eMMC, and SD cards, have
49 the upper index structures such as inode, inode map, and checkpoint block are
50 also updated recursively. This problem is called as wandering tree problem [1],
52 propagation as much as possible.
61 as a cleaning process.
63 The process consists of three operations as follows.
72 amount of valid data to be moved, and move them quickly as well.
82 - Align FS data structures to the operational units in FTL as best efforts
86 - Use a term, “node”, that represents inodes as well as various pointer blocks
124 does not aware of cold files such as media files.
[all …]
|
| /linux-4.4.14/drivers/staging/comedi/ |
| D | Kconfig | 50 from multiple devices together as one.
54 To compile this driver as a module, choose M here: the module will be
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
115 To compile this driver as a module, choose M here: the module will be
136 To compile this driver as a module, choose M here: the module will be
144 To compile this driver as a module, choose M here: the module will be
167 To compile this driver as a module, choose M here: the module will be
[all …]
|
| /linux-4.4.14/tools/testing/selftests/futex/ |
| D | README | 11 primitives. These can be used as is in user applications or can serve as
13 directory or purely as header files under include/, I'm leaning toward the
23 o Tests should be as self contained as is practical so as to facilitate sharing
25 o The build system shall remain as simple as possible, avoiding any archive or
30 o External dependencies shall remain as minimal as possible. Currently gcc
47 # useful here. Using -v to toggle it them on and off, as with -c.
55 problem as we intend to write multiple tests which collide in this namespace.
62 kernel as defined in the Linux source Documentation/CodingStyle.
|
| /linux-4.4.14/drivers/input/misc/ |
| D | Kconfig | 19 Support the ONKEY of Marvell 88PM860x PMICs as an input device
22 To compile this driver as a module, choose M here: the module
29 Support the ONKEY of Marvell 88PM80x PMICs as an input device
32 To compile this driver as a module, choose M here: the module
42 To compile this driver as a module, choose M here: the module
52 To compile this driver as a module, choose M here: the
62 To compile this driver as a module, choose M here: the
72 To compile this driver as a module, choose M here: the
82 To compile this driver as a module, choose M here: the
93 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/drivers/md/ |
| D | dm-flakey.c | 46 static int parse_features(struct dm_arg_set *as, struct flakey_c *fc, in parse_features() argument
61 if (!as->argc) in parse_features()
64 r = dm_read_arg_group(_args, as, &argc, &ti->error); in parse_features()
69 arg_name = dm_shift_arg(as); in parse_features()
93 r = dm_read_arg(_args + 1, as, &fc->corrupt_bio_byte, &ti->error); in parse_features()
101 arg_name = dm_shift_arg(as); in parse_features()
115 r = dm_read_arg(_args + 2, as, &fc->corrupt_bio_value, &ti->error); in parse_features()
123 r = dm_read_arg(_args + 3, as, &fc->corrupt_bio_flags, &ti->error); in parse_features()
165 struct dm_arg_set as; in flakey_ctr() local
169 as.argc = argc; in flakey_ctr()
[all …]
|
| D | dm-mpath.c | 514 static int parse_path_selector(struct dm_arg_set *as, struct priority_group *pg, in parse_path_selector() argument
525 pst = dm_get_path_selector(dm_shift_arg(as)); in parse_path_selector()
531 r = dm_read_arg_group(_args, as, &ps_argc, &ti->error); in parse_path_selector()
537 r = pst->create(&pg->ps, ps_argc, as->argv); in parse_path_selector()
545 dm_consume_args(as, ps_argc); in parse_path_selector()
550 static struct pgpath *parse_path(struct dm_arg_set *as, struct path_selector *ps, in parse_path() argument
560 if (as->argc < 1) { in parse_path()
569 r = dm_get_device(ti, dm_shift_arg(as), dm_table_get_mode(ti->table), in parse_path()
625 r = ps->type->add_path(ps, &p->path, as->argc, as->argv, &ti->error); in parse_path()
638 static struct priority_group *parse_priority_group(struct dm_arg_set *as, in parse_priority_group() argument
[all …]
|
| D | dm-switch.c | 204 static int parse_path(struct dm_arg_set *as, struct dm_target *ti) in parse_path() argument
210 r = dm_get_device(ti, dm_shift_arg(as), dm_table_get_mode(ti->table), in parse_path()
217 if (kstrtoull(dm_shift_arg(as), 10, &start) || start != (sector_t)start) { in parse_path()
261 struct dm_arg_set as; in switch_ctr() local
265 as.argc = argc; in switch_ctr()
266 as.argv = argv; in switch_ctr()
268 r = dm_read_arg(_args, &as, &nr_paths, &ti->error); in switch_ctr()
272 r = dm_read_arg(_args + 1, &as, ®ion_size, &ti->error); in switch_ctr()
276 r = dm_read_arg_group(_args + 2, &as, &nr_optional_args, &ti->error); in switch_ctr()
281 if (as.argc != nr_paths * 2) { in switch_ctr()
[all …]
|
| /linux-4.4.14/drivers/media/usb/gspca/ |
| D | Kconfig | 15 To compile this driver as modules, choose M here: the
31 To compile this driver as a module, choose M here: the
40 To compile this driver as a module, choose M here: the
51 To compile this driver as a module, choose M here: the
61 To compile this driver as a module, choose M here: the
70 To compile this driver as a module, choose M here: the
79 To compile this driver as a module, choose M here: the
88 To compile this driver as a module, choose M here: the
98 To compile this driver as a module, choose M here: the
107 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/Documentation/input/ |
| D | gamepad.txt | 40 differently labeled on most devices so we define them as NORTH,
46 Furthermore, many gamepads have a fancy branded button that is used as
64 an alias for BTN_SOUTH/BTN_A. It can be used to identify a gamepad as such.
79 and one analog stick. It reports them as if it were a gamepad with only one
100 If only 2 action-buttons are present, they are reported as BTN_SOUTH and
104 If only 3 action-buttons are present, they are reported as (from left
106 If the buttons are aligned perfectly vertically, they are reported as
110 different formations. If diamond-shaped, they are reported as BTN_NORTH,
117 Some of these are available as digital buttons, some as analog buttons. Some
121 Digital buttons are reported as:
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | nvidia,tegra20-kbc.txt | 3 can be configured as row or column. The maximum column pin can be 8
10 - nvidia,kbc-row-pins: The KBC pins which are configured as row. This is an
11 array of pin numbers which is used as rows.
12 - nvidia,kbc-col-pins: The KBC pins which are configured as column. This is an
13 array of pin numbers which is used as column.
14 - linux,keymap: The keymap for keys as described in the binding document
26 - linux,fn-keymap: a second keymap, same specification as the
32 - wakeup-source: configure keyboard as a wakeup source for suspend/resume
46 nvidia,kbc-row-pins = <0 1 2>; /* pin 0, 1, 2 as rows */
47 nvidia,kbc-col-pins = <11 12 13>; /* pin 11, 12, 13 as columns */
|
| /linux-4.4.14/drivers/pwm/ |
| D | Kconfig | 7 in a rectangular pulse signal is used as a means to alter the
18 to configure as well as enable and disable them.
25 continue to work as expected.
41 To compile this driver as a module, choose M here: the module
50 To compile this driver as a module, choose M here: the module
62 To compile this driver as a module, choose M here: the module
74 To compile this driver as a module, choose M here: the module
83 To compile this driver as a module, choose M here: the module
92 To compile this driver as a module, choose M here: the module
101 To compile this driver as a module, choose M here: the module
[all …]
|
| /linux-4.4.14/drivers/ptp/ |
| D | Kconfig | 21 This driver adds support for PTP clocks as character
23 also enable at least one clock driver as well.
25 To compile this driver as a module, choose M here: the module
29 tristate "Freescale eTSEC as PTP clock"
34 This driver adds support for using the eTSEC as a PTP
39 To compile this driver as a module, choose M here: the module
43 tristate "Intel IXP46x as PTP clock"
48 This driver adds support for using the IXP46X as a PTP
53 To compile this driver as a module, choose M here: the module
67 This driver adds support for using the DP83640 as a PTP
[all …]
|
| /linux-4.4.14/net/bridge/netfilter/ |
| D | Kconfig | 49 To compile it as a module, choose M here. If unsure, say N.
58 To compile it as a module, choose M here. If unsure, say N.
67 To compile it as a module, choose M here. If unsure, say N.
76 To compile it as a module, choose M here. If unsure, say N.
85 To compile it as a module, choose M here. If unsure, say N.
93 To compile it as a module, choose M here. If unsure, say N.
101 To compile it as a module, choose M here. If unsure, say N.
110 To compile it as a module, choose M here. If unsure, say N.
119 If you want to compile it as a module, say M here and read
127 This value is the same as the one used in the iptables mark match and
[all …]
|
| /linux-4.4.14/drivers/iio/adc/ |
| D | Kconfig | 23 To compile this driver as a module, choose M here: the module will be
33 To compile this driver as a module, choose M here: the
45 To compile this driver as a module, choose M here: the
58 To compile this driver as a module, choose M here: the
69 To compile this driver as a module, choose M here: the module will be
80 To compile this driver as a module, choose M here: the
92 To compile this driver as a module, choose M here: the
104 To compile this driver as a module, choose M here: the
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/drivers/input/touchscreen/ |
| D | Kconfig | 27 To compile this driver as a module, choose M here: the
46 To compile this driver as a module, choose M here: the
59 To compile this driver as a module, choose M here: the
70 To compile this driver as a module, choose M here: the
79 To compile this driver as a module, choose M here: the
90 To compile this driver as a module, choose M here: the
102 To compile this driver as a module, choose M here: the
111 such as AT42QT602240/ATMXT224, connected to your system.
115 To compile this driver as a module, choose M here: the
128 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/drivers/input/joystick/ |
| D | Kconfig | 31 To compile this driver as a module, choose M here: the
41 To compile this driver as a module, choose M here: the
51 To compile this driver as a module, choose M here: the
60 To compile this driver as a module, choose M here: the
70 To compile this driver as a module, choose M here: the
80 To compile this driver as a module, choose M here: the
90 To compile this driver as a module, choose M here: the
100 To compile this driver as a module, choose M here: the
110 To compile this driver as a module, choose M here: the
120 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/drivers/input/keyboard/ |
| D | Kconfig | 22 To compile this driver as a module, choose M here: the module will
32 To compile this driver as a module, choose M here: the
42 To compile this driver as a module, choose M here: the
52 To compile this driver as a module, choose M here: the
66 To compile this driver as a module, choose M here: the
84 To compile this driver as a module, choose M here: the
104 built-in keyboard (as opposed to an external keyboard).
107 AT and PS/2 keyboards. These are as follows:
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
[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
26 This driver can also be built as a module. If so, the module will
37 This driver can also be built as a module. If so, the module will
47 This driver can also be built as a module. If so, the module will
58 This driver can also be built as a module. If so, the module will
75 This driver can also be built as a module. If so, the module will
85 This driver can also be built as a module. If so, the module will
95 This driver can also be built as a module. If so, the module will
105 This driver can also be built as a module. If so, the module will
115 This driver can also be built as a module. If so, the module will
[all …]
|
| /linux-4.4.14/net/sched/ |
| D | Kconfig | 41 can say Y to as many as you like. If unsure, say N now.
59 want to use as leaf disciplines.
61 To compile this code as a module, choose M here: the
75 To compile this code as a module, choose M here: the
84 To compile this code as a module, choose M here: the
98 To compile this code as a module, choose M here: the
107 To compile this code as a module, choose M here: the
116 To compile this code as a module, choose M here: the
127 To compile this code as a module, choose M here: the
138 To compile this code as a module, choose M here: the
[all …]
|
| /linux-4.4.14/drivers/hwmon/ |
| D | Kconfig | 13 sensors and various additional features such as the ability to
22 This support can also be built as a module. If so, the module
52 This driver can also be built as a module. If so, the module
67 This driver can also be built as a module. If so, the module
81 This driver can also be built as a module. If so, the module
91 This driver can also be built as a module. If so, the module
101 This driver can also be built as a module. If so, the module
111 This driver can also be built as a module. If so, the module
122 This driver can also be built as a module. If so, the module
133 This driver can also be built as a module. If so, the module
[all …]
|
| /linux-4.4.14/drivers/input/ |
| D | Kconfig | 23 To compile this driver as a module, choose M here: the
34 as standard LED class devices in sysfs.
38 To compile this driver as a module, choose M here: the
45 such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
51 To compile this driver as a module, choose M here: the
64 To compile this driver as a module, choose M here: the
77 To compile this driver as a module, choose M here: the
90 To compile this driver as a module, choose M here: the
99 Say Y here if you want your mouse to be accessible as char devices
100 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
[all …]
|
| /linux-4.4.14/sound/pci/ |
| D | Kconfig | 20 To compile this as a module, choose M here: the module
32 To compile this driver as a module, choose M here: the module
46 To compile this driver as a module, choose M here: the module
60 To compile this driver as a module, choose M here: the module
72 To compile this driver as a module, choose M here: the module
83 To compile this driver as a module, choose M here: the module
93 To compile this driver as a module, choose M here: the module
107 To compile this driver as a module, choose M here: the module
120 To compile this driver as a module, choose M here: the module
134 To compile this driver as a module, choose M here: the module
[all …]
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | Kconfig | 7 This is the Speakup screen reader. Think of it as a
23 Speakup can either be built in or compiled as a module
27 the synthesizer drivers below can only be built as
31 used in conjunction with Speakup. Think of them as
35 The Dectalk pc driver can only be built as a module, and
49 or m to build it as a module. See the configuration
58 or m to build it as a module. See the configuration
66 or m to build it as a module. See the configuration
74 build it as a module. See the configuration help on the
82 or m to build it as a module. See the configuration
[all …]
|
| /linux-4.4.14/drivers/misc/mic/ |
| D | Kconfig | 8 device or driver on the MIC Bus, such as CONFIG_INTEL_MIC_HOST,
14 More information about the Intel MIC family as well as the Linux
25 device or driver on the SCIF Bus, such as CONFIG_INTEL_MIC_HOST
31 More information about the Intel MIC family as well as the Linux
51 More information about the Intel MIC family as well as the Linux
83 (SCIF (pronounced as skiff)) is a low level communications API
89 More information about the Intel MIC family as well as the Linux
101 devices. COSM drivers implement functions such as boot,
107 More information about the Intel MIC family as well as the Linux
|
| /linux-4.4.14/drivers/input/tablet/ |
| D | Kconfig | 22 (CONFIG_INPUT_EVDEV) as well.
24 To compile this driver as a module, choose M here: the
35 support" (CONFIG_INPUT_EVDEV) as well.
37 To compile this driver as a module, choose M here: the
47 (CONFIG_INPUT_EVDEV) as well.
49 To compile this driver as a module, choose M here: the
60 To compile this driver as a module, choose M here: the
71 (CONFIG_INPUT_EVDEV) as well.
73 To compile this driver as a module, choose M here: the
83 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/drivers/rtc/ |
| D | Kconfig | 106 interfaces, which "udev" sets up as /dev/rtc0 through
110 can be accessed as /dev/rtc, which is a name
139 This driver can also be built as a module. If so, the module
154 This driver can also be built as a module. If so, the module
164 This driver can also be built as a module. If so, the module
174 This driver can also be built as a module. If so, the module
184 This driver can also be built as a module. If so, the module
194 This driver can also be built as a module. If so, the module
208 registers may add features such as NVRAM, a trickle charger for
212 This driver can also be built as a module. If so, the module
[all …]
|
| /linux-4.4.14/drivers/iio/light/ |
| D | Kconfig | 18 To compile this driver as a module, choose M here: the module will
30 This driver can also be built as a module. If so, the module
40 To compile this driver as a module, choose M here: the
50 To compile this driver as a module, choose M here: the
63 To compile this driver as a module, choose M here: the
73 To compile this driver as a module, choose M here: the module will
84 To compile this driver as a module, choose M here:
95 To compile this driver as a module, choose M here:
105 To compile this driver as a module, choose M here: the module will
116 To compile this driver as a module, choose M here:
[all …]
|
| /linux-4.4.14/fs/afs/ |
| D | super.c | 293 struct afs_super_info *as = sb->s_fs_info; in afs_test_super() local
295 return as->volume == as1->volume; in afs_test_super()
310 struct afs_super_info *as = sb->s_fs_info; in afs_fill_super() local
322 sb->s_bdi = &as->volume->bdi; in afs_fill_super()
323 strlcpy(sb->s_id, as->volume->vlocation->vldb.name, sizeof(sb->s_id)); in afs_fill_super()
326 fid.vid = as->volume->vid; in afs_fill_super()
362 struct afs_super_info *as; in afs_mount() local
401 as = kzalloc(sizeof(struct afs_super_info), GFP_KERNEL); in afs_mount()
402 if (!as) { in afs_mount()
407 as->volume = vol; in afs_mount()
[all …]
|
| /linux-4.4.14/drivers/input/serio/ |
| D | Kconfig | 11 as well as serial mice, Sun keyboards, some joysticks and 6dof
16 To compile this driver as a module, choose M here: the
39 To compile this driver as a module, choose M here: the
54 To compile this driver as a module, choose M here: the
67 To compile this driver as a module, choose M here: the
85 To compile this driver as a module, choose M here: the
96 To compile this driver as a module, choose M here: the
106 To compile this driver as a module, choose M here: the module will
128 To compile this driver as a module, choose M here: the
149 to use a HIL keyboard as your primary keyboard, you may wish
[all …]
|
| /linux-4.4.14/drivers/media/i2c/ |
| D | Kconfig | 38 To compile this driver as a module, choose M here: the
47 To compile this driver as a module, choose M here: the
56 To compile this driver as a module, choose M here: the
65 To compile this driver as a module, choose M here: the
74 To compile this driver as a module, choose M here: the
83 To compile this driver as a module, choose M here: the
93 To compile this driver as a module, choose M here: the
103 To compile this driver as a module, choose M here: the
112 To compile this driver as a module, choose M here: the
121 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/net/netfilter/ipset/ |
| D | Kconfig | 11 To compile it as a module, choose M here. If unsure, say N.
34 To compile it as a module, choose M here. If unsure, say N.
43 To compile it as a module, choose M here. If unsure, say N.
52 To compile it as a module, choose M here. If unsure, say N.
62 To compile it as a module, choose M here. If unsure, say N.
71 To compile it as a module, choose M here. If unsure, say N.
80 To compile it as a module, choose M here. If unsure, say N.
90 To compile it as a module, choose M here. If unsure, say N.
100 To compile it as a module, choose M here. If unsure, say N.
109 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-4.4.14/drivers/char/hw_random/ |
| D | Kconfig | 11 To compile this driver as a module, choose M here: the
34 To compile this driver as a module, choose M here: the
47 To compile this driver as a module, choose M here: the
60 To compile this driver as a module, choose M here: the
73 To compile this driver as a module, choose M here: the
86 To compile this driver as a module, choose M here: the
99 To compile this driver as a module, choose M here: the
112 To compile this driver as a module, choose M here: the
125 To compile this driver as a module, choose M here: the
138 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | introduction.txt | 20 engine will handle those tasks as well. Other kernel subsystems should
32 formatting of these NetLabel messages as well as the Generic NETLINK family
33 names can be found in the 'net/netlabel/' directory as comments in the
34 header files as well as in 'include/net/netlabel.h'.
45 'include/net/netlabel.h' header file as well as the 'lsm_interface.txt' file
|
| /linux-4.4.14/Documentation/networking/ |
| D | framerelay.txt | 3 Data Link Connection Identifier (DLCI) as its hardware address. Usually these
11 The configuration script will ask you how many DLCIs you need, as well as
21 S508 are supported. This driver is currently set up for only FR, but as
23 them as well.
27 to specify the types of boards to be configured as FRADs, as well as perform
32 Additional FRAD device drivers can be added as hardware is available.
|
| D | ltpc.txt | 9 configuration dialog. You can also compile it as a module.
18 as the following to your /etc/lilo.conf:
26 If you load the driver as a module, you can pass the parameters "io=",
28 them as options in a configuration file in /etc/modprobe.d/ directory:
34 need to add a line such as:
55 compiled as a module, you will need to refer to it as "dummy0" or some
69 board. Set the switches so as not to conflict with other hardware.
101 Instead, you follow the same procedure as for doing IP in EtherTalk.
110 this, either compile the driver as a module, or pass the parameters
111 for the card to the kernel as described above.
[all …]
|
| D | xfrm_sync.txt | 10 the processing of the SA as accurate as possible if it has access to it.
15 with as minimal loss at failover time.
16 This way a backup stays as closely uptodate as an active member.
43 A XFRM_MSG_NEWAE will have at least two TLVs (as is
69 message (kernel<->user) as well the cause (config, query or event).
95 This is a timer value in milliseconds which is used as the nagle
106 in order to not change existing applications such as racoon
139 XFRM_MSG_NEWAE is also issued to any listeners as described in iii).
141 ii) kernel->user direction as a response to XFRM_MSG_GETAE
146 iii) kernel->user to report as event if someone sets any values or
[all …]
|
| D | sctp.txt | 11 Transport Area (TSVWG) working group for the continued evolvement of SCTP as a
19 referred to as the UDP-style API of the Sockets Extensions for SCTP, as
24 -lksctp can be built as statically or as a module. However, be aware that
|
| D | PLIP.txt | 14 parallel ports to appear as a IP network interface.
79 mode as compared to IRQ mode as far as the data transfer speed is involved.
90 Alpha, as of this writing). Between two such polls, there are 10^6/HZ usecs.
92 quite possible for the trigger timeout to expire between two such polls, as
129 status inputs, and they are used as four data inputs and a clock (data
130 strobe) input, arranged so that the data input bits appear as contiguous
133 A cable that implements this protocol is available commercially as a
135 two DB-25 male connectors symmetrically connected as follows:
161 ``printer'' (as opposed to ``parallel'') ports or when the machine
162 isn't configured for PLIP, as it will result in output driver
[all …]
|
| /linux-4.4.14/Documentation/blackfin/ |
| D | bfin-gpio-notes.txt | 23 multi-functions. They can be configured as peripheral, or just as GPIO,
33 - Use the pin as peripheral,
38 - Use the pin as GPIO,
41 - Use the pin as GPIO interrupt,
55 - Kernel permit the identical GPIO be requested both as GPIO and GPIO
60 configuring it as IRQ!
63 identical GPIO, one of them use it as GPIO, the other use it as
|
| /linux-4.4.14/drivers/clk/qcom/ |
| D | Kconfig | 18 Say Y if you want to use peripheral devices such as UART, SPI,
28 Say Y if you want to support multimedia devices such as display,
36 Say Y if you want to use peripheral devices such as UART, SPI,
45 Say Y if you want to use audio devices such as i2s, pcm,
53 Say Y if you want to use peripheral devices such as UART, SPI,
62 Say Y if you want to use devices such as UART, SPI i2c, USB,
70 Say Y if you want to use peripheral devices such as UART, SPI,
79 Say Y if you want to use audio devices such as i2s, pcm,
88 Say Y if you want to support multimedia devices such as display,
97 Say Y if you want to use peripheral devices such as UART, SPI,
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | rt5645.txt | 24 1: using IN2P pin as dmic1 data pin
25 2: using GPIO6 pin as dmic1 data pin
26 3: using GPIO10 pin as dmic1 data pin
27 4: using GPIO12 pin as dmic1 data pin
31 1: using IN2N pin as dmic2 data pin
32 2: using GPIO5 pin as dmic2 data pin
33 3: using GPIO11 pin as dmic2 data pin
|
| D | renesas,fsi.txt | 5 "renesas,sh_fsi2" or "renesas,sh_fsi" as
17 - fsib,spdif-connection : same as fsia
18 - fsib,stream-mode-support : same as fsia
19 - fsib,use-internal-clock : same as fsia
|
| D | cs42l52.txt | 22 as a differential input. If not present then the MICA input is configured as
26 as a differential input. If not present then the MICB input is configured as
|
| /linux-4.4.14/sound/isa/ |
| D | Kconfig | 36 To compile this driver as a module, choose M here: the module
51 To compile this driver as a module, choose M here: the module
64 To compile this driver as a module, choose M here: the module
79 To compile this driver as a module, choose M here: the module
92 To compile this driver as a module, choose M here: the module
105 To compile this driver as a module, choose M here: the module
119 To compile this driver as a module, choose M here: the module
131 To compile this driver as a module, choose M here: the module
144 To compile this driver as a module, choose M here: the module
155 To compile this driver as a module, choose M here: the module
[all …]
|
| /linux-4.4.14/drivers/usb/serial/ |
| D | Kconfig | 17 To compile this driver as a module, choose M here: the
27 converter port as the system console (the system console is the
33 (/dev/tty0) will still be used as the system console by default, but
34 you can alter that using a kernel command line option such as
41 port, /dev/ttyUSB0, as system console.
51 support" be compiled as a module for this driver to be used
72 To compile this driver as a module, choose M here: the module
80 To compile this driver as a module, choose M here: the module
89 To compile this driver as a module, choose M here: the
99 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/drivers/iio/humidity/ |
| D | Kconfig | 12 Other sensors should work as well as long as they speak the
22 To compile this driver as a module, choose M here: the module
35 This driver can also be built as a module. If so, the module will
45 To compile this driver as a module, choose M here: the module
55 To compile this driver as a module, choose M here: the module
|
| /linux-4.4.14/Documentation/ |
| D | SecurityBugs | 3 disclosed as quickly as possible. Please report security bugs to the
23 bug submitter to bug resolution as well as disclosure. We prefer
24 to fully disclose the bug as soon as possible. It is reasonable to
29 bug submitter as well as vendors. However, the kernel security team
|
| D | futex-requeue-pi.txt | 8 brevity, this action will be referred to as "requeue_pi" throughout
9 this document. Priority inheritance is abbreviated throughout as
56 would be modified as follows:
89 is necessary for both the requeue code, as well as the waiting code,
92 acquire the rt_mutex as it would open a race window between the
119 task as a waiter on the underlying rt_mutex. It is possible that
120 the lock can be acquired at this stage as well, if so, the next
123 FUTEX_CMP_REQUEUE_PI accepts nr_wake and nr_requeue as arguments, but
125 requeue up to nr_wake + nr_requeue tasks. It will wake only as many
126 tasks as it can acquire the lock for, which in the majority of cases
[all …]
|
| D | eisa.txt | 7 status as other much more mainstream busses such as PCI or USB. This
14 most EISA drivers are among the oldest Linux drivers so, as you can
28 by the bus code. This can go from something as simple as reserving
44 The eisa_root_register function is used to declare a device as the
46 to this device, as well as some parameters for probing purposes.
90 driver : a generic driver, such as described in
115 when driver is built as a module).
118 encapsulated in a 'struct eisa_device' described as follows :
130 id : EISA id, as read from device. id.driver_data is set from the
162 set the card as disabled. The driver must be able to properly
[all …]
|
| D | init.txt | 19 required drivers such as storage hardware (such as SCSI or USB!)
20 and filesystem (ext3, jffs2 etc.) are builtin (alternatively as modules,
26 D) e.g. required library dependencies of the init binary such as
35 non-script binary such as /bin/sh and confirm its successful execution.
41 which needs to be made as painless as possible), then submit patch to LKML.
|
| D | printk-formats.txt | 57 functionality as the 'S' and 's' specifiers.
82 For printing a phys_addr_t type (and its derivatives, such as
93 Raw buffer as an escaped string:
97 For printing raw buffer as an escaped string. For the following buffer
125 Raw buffer as a hex string:
132 For printing a small buffers (up to 64 bytes long) as a hex string with
185 print a compressed IPv6 address as described by
206 In case of an IPv6 address the compressed IPv6 address as described by
209 case of additional specifiers 'p', 'f' or 's' as suggested by
213 specifiers can be used as well and are ignored in case of an IPv6
[all …]
|
| D | logo.txt | 4 and is freely usable as long as you acknowledge Larry as the original
|
| /linux-4.4.14/drivers/media/platform/davinci/ |
| D | Kconfig | 14 To compile this driver as a module, choose M here. There will
28 To compile this driver as a module, choose M here. There will
39 with decoder modules such as TVP5146 over BT656 or
40 sensor module such as MT9T001 over a raw interface. This
44 To compile this driver as a module, choose M here. There will
55 with decoder modules such as TVP5146 over BT656 or
56 sensor module such as MT9T001 over a raw interface. This
60 To compile this driver as a module, choose M here. There will
73 To compile this driver as a module, choose M here. There will
86 To compile this driver as a module, choose M here. There will
|
| /linux-4.4.14/net/ax25/ |
| D | Kconfig | 27 carry other protocols such as tcp/ip. To use it, you need a device
29 use a low speed TNC (a Terminal Node Controller acts as a kind of
39 radio as well as information about how to configure an AX.25 port is
47 To compile this driver as a module, choose M here: the
58 If you say Y here, your Linux box will act as a DAMA slave; this is
60 configuration. Linux cannot yet act as a DAMA server. This option
73 If you say Y here, your Linux box will act as a DAMA master; this is
75 configuration. Linux cannot yet act as a DAMA server. This option
87 users as well as information about how to configure an AX.25 port is
94 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-entries | 12 cannot ensure that the data as exported to userland is
15 DMI is structured as a large table of entries, where
17 length of the entry, as well as a firmware-provided
33 doesn't matter), they will be represented in sysfs as
45 assigned entry handles as the kernel itself makes no
46 guarantees that handles as exported are unique, and
51 exported as attributes:
56 length : The length of the entry, as presented in the
70 as found in the directory name. It indicates
73 given type. This value is the same as found
[all …]
|
| D | configfs-usb-gadget-mass-storage | 21 Required if LUN is not marked as removable.
24 is enabled as well as when it was impossible
26 removable - Flag specifying that LUN shall be indicated as
28 cdrom - Flag specifying that LUN shall be reported as
|
| D | evm | 8 value as the extended attribute 'security.evm'.
17 should be done as early as possible. Normally this is done
18 in the initramfs, which has already been measured as part
|
| D | sysfs-class-power-twl4030 | 24 "auto" - draw power as appropriate for detected
28 - activate mode described as "linear" in
34 such as bicycle dynamo, but care should
43 "auto" - draw power as appropriate for detected
|
| D | sysfs-gpio | 13 GPIOs are identified as they are inside the kernel, using integers in
22 /direction ... r/w as: in, out (default low); write: high, low
23 /edge ... r/w as: none, falling, rising, both
25 /base ... (r/o) same as N
|
| D | sysfs-bus-css | 5 Description: Contains the subchannel type, as reported by the hardware.
12 Description: Contains the module alias as reported with uevents.
21 subchannel, as reported by the channel subsystem
30 Description: Contains the PIM/PAM/POM values, as reported by the
|
| /linux-4.4.14/net/l2tp/ |
| D | Kconfig | 16 intervening network in a way that is as transparent as
21 connections. L2TP is also used as a VPN protocol, popular
24 L2TPv3 allows other protocols as well as PPP to be carried
33 If you don't need L2TP, say N. To compile all L2TP code as
46 To compile this driver as a module, choose M here. The module
59 packet-oriented data network (e.g., over IP). L2TP, as
84 To compile this driver as a module, choose M here. The module
96 used as a control protocol and for data encapsulation to set
108 To compile this driver as a module, choose M here. The module
|
| /linux-4.4.14/drivers/i2c/busses/ |
| D | Kconfig | 20 This driver can also be built as a module. If so, the module
32 This driver can also be built as a module. If so, the module
42 This driver can also be built as a module. If so, the module
54 This driver can also be built as a module. If so, the module
67 This driver can also be built as a module. If so, the module
77 This driver can also be built as a module. If so, the module
87 This driver can also be built as a module. If so, the module
131 This driver can also be built as a module. If so, the module
142 This driver can also be built as a module. If so, the module
152 This driver can also be built as a module. If so, the module will be
[all …]
|
| /linux-4.4.14/drivers/nvmem/ |
| D | Kconfig | 10 This driver can also be built as a module. If so, the module
25 This driver can also be built as a module. If so, the module
36 This driver can also be built as a module. If so, the module
47 This driver can also be built as a module. If so, the module
55 from eFuse, such as cpu-leakage.
57 This driver can also be built as a module. If so, the module
68 This driver can also be built as a module. If so, the module
78 This driver can also be build as a module. If so, the module will
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 15 on-line as fast as possible after a lock-up. There's both a watchdog
65 To compile this driver as a module, choose M here: the
77 Alternatively say M to compile the driver as a module,
88 This driver can also be built as a module. If so, the module
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.
118 bool "Register the watchdog as early as possible"
135 This driver can also be built as a module. If so the module
161 To compile this driver as a module, choose M here: the
214 driver as a module, which will be called wdt285.
[all …]
|
| /linux-4.4.14/drivers/iio/dac/ |
| D | Kconfig | 16 To compile this driver as a module, choose M here: the
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
62 To compile this driver as a module, choose M here: the
72 To compile this driver as a module, choose M here: the
82 To compile this driver as a module, choose M here: the
100 To compile this driver as a module, choose M here: the
111 To compile this driver as a module, choose M here: the
121 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/drivers/iio/pressure/ |
| D | Kconfig | 16 To compile this driver as a module, choose M here: the module
30 To compile this driver as a module, choose M here: the module
40 To compile this driver as a module, choose M here: the module
52 To compile this driver as a module, choose M here: the module
61 To compile this driver as a module, choose M here: the module will
70 To compile this driver as a module, choose M here: the module will
79 To compile this driver as a module, choose M here: the module will
92 This driver can also be built as a module. If so, the module will
106 This driver can also be built as a module. If so, these modules
131 To compile this driver as a module, choose M here: the module
|
| /linux-4.4.14/arch/cris/arch-v10/ |
| D | Kconfig | 76 set this to same as CONFIG_ETRAX_LED1G (normally 2).
86 set this to same as CONFIG_ETRAX_LED1G (normally 2).
96 set this to same as CONFIG_ETRAX_LED1G (normally 2).
105 set this to same as CONFIG_ETRAX_LED1G (normally 2).
114 set this to same as CONFIG_ETRAX_LED1G (normally 2).
123 set this to same as CONFIG_ETRAX_LED1G (normally 2).
132 set this to same as CONFIG_ETRAX_LED1G (normally 2).
141 set this to same as CONFIG_ETRAX_LED1G (normally 2).
150 set this to same as CONFIG_ETRAX_LED1G (normally 2).
159 set this to same as CONFIG_ETRAX_LED1G (normally 2).
[all …]
|
| /linux-4.4.14/Documentation/arm64/ |
| D | acpi_object_usage.txt | 44 time as ARM-compatible hardware is available, and the specification
85 conditions; it allows one to inject an error into the system as
119 If PSCI is used (as is recommended), make sure that ARM_BOOT_ARCH is
121 PSCI_USE_HVC is set or unset as needed (see table 5-37).
158 x86 only table as of ACPI 5.1; future versions have been adapted for
281 _ADR 6.1.1 Use as needed.
283 _BBN 6.5.5 Use as needed; PCI-specific.
289 it explicit ensures the kernel will set up DMA as
294 _CID 6.1.2 Use as needed.
296 _CLS 6.1.3 Use as needed.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/spi/ |
| D | spi-ath79.txt | 4 - compatible: has to be "qca,<soc-type>-spi", "qca,ar7100-spi" as fallback.
8 - #address-cells: <1>, as required by generic SPI binding.
9 - #size-cells: <0>, also as required by generic SPI binding.
11 Child nodes as per the generic SPI binding.
|
| D | omap-spi.txt | 9 - ti,pindir-d0-out-d1-in: Select the D0 pin as output and D1 as
10 input. The default is D0 as input and
11 D1 as output.
15 as described in the generic DMA client binding. A tx and rx
|
| D | spi-octeon.txt | 7 - #address-cells : <1>, as required by generic SPI binding.
8 - #size-cells : <0>, also as required by generic SPI binding.
10 Child nodes as per the generic SPI binding.
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | spear-pcie-gadget.txt | 24 Its main purpose is to configure selected dual mode PCIe controller as device
25 and then program its various registers to configure it as a particular device
67 to the PCIe host, then host sees this device as 1MB RAM.
72 program vendor id as 0x104a
75 program device id as 0xCD80
78 program BAR0 size as 1MB
84 Program BAR0 Address as DDR (0x2100000). This is the physical address of
87 as BAR0 address then when this device will be connected to a host, it will be
88 visible as UART.
110 if MSI is to be used as interrupt, program no of msi vector needed (say4)
[all …]
|
| /linux-4.4.14/drivers/usb/storage/ |
| D | Kconfig | 23 To compile this driver as a module, choose M here: the
40 If this driver is compiled as a module, it will be named ums-realtek.
54 If this driver is compiled as a module, it will be named ums-datafab.
63 If this driver is compiled as a module, it will be named ums-freecom.
81 If this driver is compiled as a module, it will be named ums-isd200.
104 If this driver is compiled as a module, it will be named ums-usbat.
114 If this driver is compiled as a module, it will be named ums-sddr09.
123 If this driver is compiled as a module, it will be named ums-sddr55.
132 If this driver is compiled as a module, it will be named ums-jumpshot.
144 If this driver is compiled as a module, it will be named ums-alauda.
[all …]
|
| /linux-4.4.14/drivers/misc/eeprom/ |
| D | Kconfig | 17 you configure as a 24c32 (32 kbit) or larger is NOT really a
19 as read-only won't help recover from this. Also, if your chip
27 This driver can also be built as a module. If so, the module
38 This driver can also be built as a module. If so, the module
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
62 This driver can also be built as a module. If so, the module
70 The driver supports both read as well as write commands.
82 This driver can also be built as a module. If so, the module
|
| /linux-4.4.14/drivers/block/ |
| D | Kconfig | 29 That file also contains the location of the Floppy driver FAQ as
30 well as location of the fdutils package used to configure additional
33 To compile this driver as a module, choose M here: the
62 This enables support for using Chip RAM and Zorro II RAM as a
63 ramdisk or as a swap partition. Say Y if you want to include this
66 To compile this driver as a module, choose M here: the
78 You can also build this as a module which will be called gdrom.
93 kernel, or M if you would like to build it as a loadable module. If
95 PARIDE as a module. If you built PARIDE support into your kernel,
97 drivers as loadable modules. If you build this support as a module,
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,vic.txt | 12 - interrupt-controller : Identifies the node as an interrupt controller
13 - #interrupt-cells : The number of cells to define the interrupts. Must be 1 as
26 configured as wake up source for the system. Order of bits is the same as for
28 configured as a wake up source for the system. If unspecied, defaults to all
29 interrupt sources configurable as wake up sources.
|
| D | ti,omap4-wugen-mpu | 4 routes interrupts to the GIC, and also serves as a wakeup source. It
5 is also referred to as "WUGEN-MPU", hence the name of the binding.
12 - interrupt-controller : Identifies the node as an interrupt controller.
22 - Only SPIs can use the WUGEN as an interrupt parent. SGIs and PPIs
|
| D | marvell,armada-370-xp-mpic.txt | 6 - interrupt-controller: Identifies the node as an interrupt controller.
7 - msi-controller: Identifies the node as an PCI Message Signaled
22 connected as a slave to another interrupt controller. This is
24 connected as a slave to the Cortex-A9 GIC. The provided interrupt
|
| D | nvidia,tegra-ictlr.txt | 4 interrupts to the GIC, and also serves as a wakeup source. It is also
5 referred to as "ictlr", hence the name of the binding.
19 - interrupt-controller : Identifies the node as an interrupt controller.
29 - Only SPIs can use the ictlr as an interrupt parent. SGIs and PPIs
|
| /linux-4.4.14/drivers/crypto/caam/ |
| D | Kconfig | 6 and Assurance Module (CAAM), also known as the SEC version 4 (SEC4).
8 to operate as a DPAA component automatically, depending
11 To compile this driver as a module, choose M here: the module
24 To compile this driver as a module, choose M here: the module
33 Select size of Job Rings as a power of 2, within the
84 scatterlist crypto API (such as the linux native IPSec
87 To compile this as a module, choose M here: the module
99 To compile this as a module, choose M here: the module
112 To compile this as a module, choose M here: the module
|
| /linux-4.4.14/net/ipv6/netfilter/ |
| D | Kconfig | 26 To compile it as a module, choose M here. If unsure, say N.
42 fields such as the source, destination, flowlabel, hop-limit and
94 packet transformations such as the source, destination address and
134 To compile it as a module, choose M here. If unsure, say N.
145 To compile it as a module, choose M here. If unsure, say N.
155 To compile it as a module, choose M here. If unsure, say N.
164 To compile it as a module, choose M here. If unsure, say N.
173 To compile it as a module, choose M here. If unsure, say N.
191 To compile it as a module, choose M here. If unsure, say N.
199 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-4.4.14/drivers/staging/iio/trigger/ |
| D | Kconfig | 13 clocks as IIO triggers.
15 To compile this driver as a module, choose M here: the
23 Provides support for using a Blackfin timer as IIO triggers.
26 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/drivers/staging/iio/accel/ |
| D | Kconfig | 15 To compile this driver as a module, say M here: the module will
27 To compile this driver as a module, say M here: the module will be
39 To compile this driver as a module, say M here: the module will be
51 To compile this driver as a module, say M here: the module will be
62 To compile this driver as a module, say M here: the module will be
74 To compile this driver as a module, say M here: the module will be
88 To compile this driver as a module, say M here: the module will be
99 To compile this driver as a module, say M here: the module will be
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-xilinx.txt | 4 (from 1 to 32 per channel). Every pin can be configured as
13 - gpio-controller : Marks the device node as a GPIO controller.
24 - xlnx,all-inputs-2 : as above but for the second channel
25 - xlnx,dout-default-2 : as above but the second channel
26 - xlnx,gpio2-width : as above but for the second channel
27 - xlnx,tri-default-2 : as above but for the second channel
|
| D | spear_spics.txt | 6 released as soon as transfer is over and TxFIFO becomes empty. This is not
10 Chipselects can be controlled by software by turning them as GPIOs. SPEAr
13 the control of this interface as gpio.
17 * compatible: should be defined as "st,spear-spics-gpio"
24 * gpio-controller: Marks the device node as gpio controller
|
| D | gpio-sx150x.txt | 20 - gpio-controller: Marks the device as a GPIO controller.
22 - interrupt-controller: Marks the device as a interrupt controller.
24 The GPIO expander can optionally be used as an interrupt controller, in
25 which case it uses the default two cell specifier as described in
|
| D | gpio-altera.txt | 10 - gpio-controller : Marks the device node as a GPIO controller.
11 - interrupt-controller: Mark the device node as an interrupt controller
17 used has IRQ enabled as the interrupt type is not software controlled,
18 but hardware synthesized. Required if GPIO is used as an interrupt
|
| /linux-4.4.14/net/caif/ |
| D | Kconfig | 12 with its modems. It is accessed from user space as sockets (PF_CAIF).
15 MeeGo ) that uses CAIF as transport, if unsure say N.
17 If you select to build it as module then CAIF_NETDEV also needs to be
18 built as modules. You will also need to say yes to any CAIF physical
40 If you select to build it as a built-in then the main CAIF device must
51 If you select to build it as a built-in then the main CAIF device must
|
| /linux-4.4.14/drivers/staging/iio/meter/ |
| D | Kconfig | 13 To compile this driver as a module, choose M here: the
23 To compile this driver as a module, choose M here: the
35 To compile this driver as a module, choose M here: the
45 To compile this driver as a module, choose M here: the
55 To compile this driver as a module, choose M here: the
65 To compile this driver as a module, choose M here: the
75 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/drivers/net/ethernet/sun/ |
| D | Kconfig | 25 systems and as an option on older Sbus systems. This driver supports
29 To compile this driver as a module, choose M here: the module
37 This driver supports the "be" interface available as an Sbus option.
40 To compile this driver as a module, choose M here: the module
48 This driver supports the "qe" 10baseT Ethernet device, available as
49 an Sbus option. Note that this is not the same as Quad FastEthernet
52 To compile this driver as a module, choose M here: the module
|
| /linux-4.4.14/drivers/iio/trigger/ |
| D | Kconfig | 11 Provides support for using an interrupt of any type as an IIO
14 To compile this driver as a module, choose M here: the
22 Provides support for using SYSFS entries as IIO triggers.
25 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/Documentation/devicetree/bindings/power_supply/ |
| D | max17042_battery.txt | 15 as cold (in tenths of degree Celsius).
17 as over heated (in tenths of degree Celsius).
19 as dead (in mV).
21 as over voltage (in mV).
|
| /linux-4.4.14/Documentation/timers/ |
| D | timekeeping.txt | 16 on this timeline, providing facilities such as high-resolution timers.
31 It will ideally NEVER stop ticking as long as the system is running. It
34 The clock source shall have as high resolution as possible, and the frequency
35 shall be as stable and correct as possible as compared to a real-world wall
54 into a nanosecond value as an unsigned long long (unsigned 64 bit) number.
56 mathematical sense is not desirable: instead the number is taken as close as
63 to aid in providing these mult and shift values, such as
67 factors using the frequency of the clock source as the only input.
94 fire interrupts, so as to trigger events on the system timeline. On an SMP
114 implementation is not provided, the system jiffy counter will be used as
[all …]
|
| /linux-4.4.14/drivers/usb/misc/ |
| D | Kconfig | 15 This code is also available as a module ( = code which can be
17 The module will be called audio. If you want to compile it as a
29 To compile this driver as a module, choose M here: the
38 To compile this driver as a module, choose M here. The module
46 To compile this driver as a module, choose M here: the
56 To compile this driver as a module, choose M here: the
65 This code is also available as a module ( = code which can be
67 The module will be called legousbtower. If you want to compile it as
79 To compile this driver as a module, choose M here: the
88 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/Documentation/virtual/kvm/arm/ |
| D | vgic-mapped-irqs.txt | 7 OS sees as regular interrupts. The code is famously known as the VGIC.
15 event as a virtual interrupt to the guest. Another example could be a
23 referred to as 'virtualized physical interrupts' and 'mapped interrupts'.
59 - LR.Pending will stay set as long as the guest has not acked the interrupt.
60 - LR.Pending transitions to LR.Active on the guest read of the IAR, as
70 handled on the host (see details on the timer as an example below). For other
89 interrupt will exit the guest as soon as we switch into the guest,
90 preventing the guest from ever making progress as the process repeats
93 the pending interrupt to the CPU. As soon as the guest deactivates the
100 from a physical device as pure virtual interrupts. But that would
[all …]
|
| /linux-4.4.14/drivers/s390/net/ |
| D | Kconfig | 11 To compile as a module, choose M. The module name is lcs.
25 To compile as a module, choose M. The module name is ctcm.
38 running on the other VM guest. To compile as a module, choose M.
51 prompt "Deliver IUCV special messages as uevents (VM only)"
54 Select this option to deliver CP special messages (SMSGs) as
58 To compile as a module, choose M. The module name is "smsgiucv_app".
72 To compile this driver as a module, choose M.
81 To compile as a module, choose M. The module name is qeth_l2.
90 To compile as a module choose M. The module name is qeth_l3.
|
| /linux-4.4.14/drivers/staging/iio/adc/ |
| D | Kconfig | 15 To compile this driver as a module, choose M here: the
25 To compile this driver as a module, choose M here: the
36 To compile this driver as a module, choose M here: the
49 To compile this driver as a module, choose M here: the
69 To compile this driver as a module, choose M here: the
79 To compile this driver as a module, choose M here: the
88 LPC32XX SoC. Note that this feature uses the same hardware as the
105 To compile this driver as a module, choose M here: the
116 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/drivers/iio/accel/ |
| D | Kconfig | 17 To compile this driver as a module, choose M here: the
54 To compile this driver as a module, choose M here: the
69 This driver can also be built as a module. If so, these modules
94 To compile this driver as a module, choose M here: the module
107 To compile this driver as a module, choose M here: the module will
119 To compile this driver as a module, choose M here: the module
134 To compile this driver as a module, choose M here: the module
145 To compile this driver as a module, choose M here: the module
158 To compile this driver as a module, choose M. The module will be
170 Choosing M will build the driver as a module. If so, the module
[all …]
|
| /linux-4.4.14/drivers/char/tpm/ |
| D | Kconfig | 17 compile this driver as a module, choose M here; the module
34 within Linux. To compile this driver as a module, choose M here;
43 To compile this driver as a module, choose M here; the module will
54 To compile this driver as a module, choose M here; the module
64 To compile this driver as a module, choose M here; the module
73 compile this driver as a module, choose M here; the module
82 as a module, choose M here; the module will be called tpm_atmel.
91 To compile this driver as a module, choose M here; the module
102 as a module, choose M here; the module will be called tpm_ibmvtpm.
113 To compile this driver as a module, choose M here; the module
[all …]
|
| /linux-4.4.14/fs/cramfs/ |
| D | README | 7 a given directory are contiguous, as this is used by readdir).
25 The order of inode traversal is described as "width-first" (not to be
28 same order as `ls -AUR' (but without the /^\..*:$/ directory header
29 lines); put another way, the same order as `find -type d -exec
48 same as the start of the (i+1)'th <block> if there is one). The first
53 tree, i.e. the same order as `find -size +0 \( -type f -o -type l \)
96 Currently, mkcramfs #define's PAGE_CACHE_SIZE as 4096 and uses that
98 turn is defined as PAGE_SIZE (which can be as large as 32KB on arm).
119 etc. macros as used by ext2fs. We don't need to swab the compressed
138 value don't get as good compression as they can.
[all …]
|
| /linux-4.4.14/drivers/net/ppp/ |
| D | Kconfig | 15 To use PPP, you need an additional program called pppd as described
22 asynchronous lines, such as regular analog phone lines, and
32 compile it as a module. To compile this driver as a module, choose M
45 method as well for this to be useful. Even if they don't support it,
52 Note that the BSD compression code will always be compiled as a
66 Deflate compression method as well for this to be useful. Even if
69 To compile this driver as a module, choose M here.
76 PPP interfaces. This allows you to control which packets count as
92 Support for the MPPE Encryption protocol, as employed by the
106 This has to be supported at the other end as well and you need a
[all …]
|
| /linux-4.4.14/drivers/mcb/ |
| D | Kconfig | 16 If build as a module, the module is called mcb.ko
26 FPGAs as well as CompactPCI attached MCB FPGAs are supported with
29 If build as a module, the module is called mcb-pci.ko
|
| /linux-4.4.14/drivers/memstick/host/ |
| D | Kconfig | 16 probably also need appropriate card reader host adapter, such as
20 To compile this driver as a module, choose M here: the
31 To compile this driver as a module, choose M here: the
43 To compile this driver as a module, choose M here: the module will
53 To compile this driver as a module, choose M here: the module will
63 To compile this driver as a module, choose M here: the module will
|
| /linux-4.4.14/sound/oss/dmasound/ |
| D | Kconfig | 10 This driver is also available as a module ( = code which can be
12 want). If you want to compile it as a module, say M here and read
24 This driver is also available as a module ( = code which can be
26 want). If you want to compile it as a module, say M here and read
38 This driver is also available as a module ( = code which can be
40 want). If you want to compile it as a module, say M here and read
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | ring.txt | 3 This document is intended as a general overview of the functionality
19 is enabled or disabled (along with enabling triggering etc. as appropriate).
23 as much buffer functionality as possible. Note almost all of these
36 as much data as requested.
|
| /linux-4.4.14/Documentation/gpio/ |
| D | sysfs.txt | 60 "direction" ... reads as either "in" or "out". This value may
61 normally be written. Writing as "out" defaults to
62 initializing the value as low. To ensure glitch free
64 configure the GPIO as an output with that initial value.
71 "value" ... reads as either 0 (low) or 1 (high). If the GPIO
72 is configured as an output, this value may be written;
73 any nonzero value is treated as high.
75 If the pin can be configured as interrupt-generating interrupt
85 "edge" ... reads as either "none", "rising", "falling", or
89 This file exists only if the pin can be configured as an
[all …]
|
| D | gpio-legacy.txt | 20 non-dedicated pin can be configured as a GPIO; and most chips have at least
36 of pins configured as "output", which is very useful in such "wire-OR"
40 - Inputs can often be used as IRQ signals, often edge triggered but
41 sometimes level triggered. Such IRQs may be configurable as system
44 - Usually a GPIO will be configurable as either input or output, as needed
67 One platform might implement it as simple inline functions accessing chip
71 in this document, but drivers acting as clients to the GPIO interface must
78 GPIO calls are available, either as "real code" or as optimized-away stubs,
93 reserves "negative" numbers for other purposes like marking signals as
95 touch the underlying hardware treats these integers as opaque cookies.
[all …]
|
| /linux-4.4.14/drivers/auxdisplay/ |
| D | Kconfig | 28 parport, you will be able to compile this as a module (M)
29 and built-in as well (Y).
31 To compile this as a module, choose M here:
55 If you compile this as a module, you can still override this
70 If you compile this as a module, you can still override this
96 To compile this as a module, choose M here:
114 You can freeze the computer, or the LCD maybe can't draw as fast as you
119 If you compile this as a module, you can still override this
|
| /linux-4.4.14/drivers/net/wireless/realtek/rtlwifi/ |
| D | Kconfig | 23 If you choose to build it as a module, it will be called rtl8192ce
34 If you choose to build it as a module, it will be called rtl8192se
45 If you choose to build it as a module, it will be called rtl8192de
58 If you choose to build it as a module, it will be called rtl8723ae
71 If you choose to build it as a module, it will be called rtl8723be
82 If you choose to build it as a module, it will be called rtl8188ee
94 If you choose to build it as a module, it will be called rtl8192ee
106 If you choose to build it as a module, it will be called rtl8821ae
118 If you choose to build it as a module, it will be called rtl8192cu
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | lm83 | 21 The LM83 is a digital temperature sensor. It senses its own temperature as
22 well as the temperature of up to three external diodes. The LM82 is
24 Both are compatible with many other devices such as the LM84 and all
34 contact us. Note that the LM90 can easily be misdetected as a LM83.
54 sensors. This means that temperature-only chips are usually used as
55 secondary chips coupled with another chip such as an IT8705F or similar
61 chip such as the LM83. The only case where using an LM83 would make
62 sense is on SMP systems, such as the above-mentioned Iwill MPX2,
80 all four sensors. There is no hysteresis mechanism as found on most
|
| /linux-4.4.14/drivers/misc/ |
| D | Kconfig | 31 This driver can also be built as a module. If so, the module
40 To compile this driver as a module, choose M here: the
51 To compile this driver as a module, choose M here: the
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
106 service processor board as a regular serial port. To make use of
159 host adapter, such as 'TI Flash Media PCI74xx/PCI76xx host adapter
166 To compile this driver as a module, choose M here: the module will
177 flash card format drivers, as outlined in the TIFM_CORE Help.
179 To compile this driver as a module, choose M here: the module will
[all …]
|
| /linux-4.4.14/net/netfilter/ |
| D | Kconfig | 55 To compile it as a module, choose M here. If unsure, say N.
92 connections using the same identity, as long as they are
165 If you want to compile it as a module, say M here and read
176 To compile it as a module, choose M here. If unsure, say N.
191 To compile it as a module, choose M here. If unsure, say N.
205 To compile it as a module, choose M here. If unsure, say N.
225 To compile it as a module, choose M here. If unsure, say N.
240 To compile it as a module, choose M here. If unsure, say N.
249 NetBIOS name service requests are sent as broadcast messages from an
262 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-4.4.14/drivers/mtd/devices/ |
| D | Kconfig | 14 If this driver is compiled as a module you get the ability to select
17 will use a 1G memory map as its view of the device. As a module,
20 particularly useful on the 2.2 kernels on PPC architectures as there
44 backed-up NVRAM module. The module was originally meant as an NFS
48 If you want to compile this driver as a module ( = code which can be
77 (once) with up to 64 bytes of data, such as a serial number or
88 are supported as well. See the driver source for the current list,
120 registered by bcma as platform devices. This enables driver for
128 present it to the system as a Memory Technology Device.
161 as a module, it is also possible to specify this as a parameter when
[all …]
|
| /linux-4.4.14/net/netlabel/ |
| D | Kconfig | 11 protocols such as CIPSO and RIPSO. For more information see
12 Documentation/netlabel as well as the NetLabel SourceForge project
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-driver-usb-usbtmc | 6 These files show the various USB TMC capabilities as described
20 These files show the various USB TMC capabilities as described
35 device as described by the document, "Universal Serial Bus Test
37 (USBTMC) Revision 1.0" as published by the USB-IF.
50 Measurement Class Specification (USBTMC) Revision 1.0" as
62 (USBTMC) Revision 1.0" as published by the USB-IF.
|
| /linux-4.4.14/drivers/net/team/ |
| D | Kconfig | 12 To compile this driver as a module, choose M here: the module
25 To compile this team mode as a module, choose M here: the module
37 To compile this team mode as a module, choose M here: the module
49 To compile this team mode as a module, choose M here: the module
62 To compile this team mode as a module, choose M here: the module
73 To compile this team mode as a module, choose M here: the module
|
| /linux-4.4.14/drivers/net/wireless/ |
| D | Kconfig | 32 To compile this driver as a module, choose M here: the module will be
65 - with or without encryption) as well as card before the Cisco
72 The driver can be compiled as a module and will be named "airo".
127 802.11 wireless cards. This driver is the same as the Aironet
130 - with or without encryption) as well as card before the Cisco
132 supports OEM of Cisco such as the DELL TrueMobile 4800 and Xircom
159 p54pci supports FullMAC PCI/Cardbus devices as well.
167 When built as module you get the module prism54
179 This driver makes the adapter appear as a normal Ethernet interface,
185 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/drivers/usb/misc/sisusbvga/ |
| D | Kconfig | 13 To compile this driver as a module, choose M here; the module will be
30 the first and last consoles (starting at 1) as driver parameters.
32 For example, if the driver is compiled as a module:
37 the "options" keyword, such as eg.
42 must be given in the kernel command like, such as
|
| /linux-4.4.14/drivers/staging/nvec/ |
| D | Kconfig | 9 To compile this driver as a module, say M here: the module will be
19 To compile this driver as a module, say M here: the module will be
29 To compile this driver as a module, say M here: the module will be
40 To compile this driver as a module, say M here: the module will be
51 To compile this driver as a module, say M here: the module will be
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | qcom,msm8960-pinctrl.txt | 24 Definition: identifies this node as an interrupt controller
29 Definition: must be 2. Specifying the pin number and flags, as defined
35 Definition: identifies this node as a gpio controller
40 Definition: must be 2. Specifying the pin number and flags, as defined
50 The pin configuration nodes act as a container for an arbitrary number of
54 parameters, such as pull-up, drive strength, etc.
69 The following generic properties as defined in pinctrl-bindings.txt are valid
119 Definition: The specified pins should be configued as no pull.
124 Definition: The specified pins should be configued as pull down.
129 Definition: The specified pins should be configued as pull up.
|
| D | qcom,apq8084-pinctrl.txt | 24 Definition: identifies this node as an interrupt controller
29 Definition: must be 2. Specifying the pin number and flags, as defined
35 Definition: identifies this node as a gpio controller
40 Definition: must be 2. Specifying the pin number and flags, as defined
50 The pin configuration nodes act as a container for an arbitrary number of
54 parameters, such as pull-up, drive strength, etc.
69 The following generic properties as defined in pinctrl-bindings.txt are valid
117 Definition: The specified pins should be configued as no pull.
122 Definition: The specified pins should be configued as pull down.
127 Definition: The specified pins should be configued as pull up.
|
| D | qcom,msm8916-pinctrl.txt | 24 Definition: identifies this node as an interrupt controller
29 Definition: must be 2. Specifying the pin number and flags, as defined
35 Definition: identifies this node as a gpio controller
40 Definition: must be 2. Specifying the pin number and flags, as defined
50 The pin configuration nodes act as a container for an arbitrary number of
54 parameters, such as pull-up, drive strength, etc.
69 The following generic properties as defined in pinctrl-bindings.txt are valid
125 Definition: The specified pins should be configued as no pull.
130 Definition: The specified pins should be configued as pull down.
135 Definition: The specified pins should be configued as pull up.
|
| D | pinctrl-mt65xx.txt | 13 - gpio-controller : Marks the device node as a gpio controller.
15 binding is used, the amount of cells must be specified as 2. See the below
25 - Flags: bit field of flags, as defined in <dt-bindings/gpio/gpio.h>.
33 - interrupt-controller: Marks the device node as an interrupt controller
54 as macros in boot/dts/<soc>-pinfunc.h directly.
62 resistors available, but for user, it's only need to set R1R0 as 00, 01, 10 or 11.
64 Some macros have been defined for this usage, such as MTK_PUPD_SET_R1R0_00.
67 When config drive-strength, it can support some arguments, such as
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig.devices | 11 bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || Q40
14 Use the power-on LED on your machine as a load meter. The exact
31 This option enables support for ARAnyM native features, such as
32 access to a disk image as /dev/hda.
94 To compile this driver as a module, choose M here.
103 To compile this driver as a module, choose M here.
123 If you say Y here, it will be possible to use a serial port as the
130 (/dev/tty0) will still be used as the system console by default, but
131 you can alter that using a kernel command line option such as
137 kernel will automatically use the first serial line, /dev/ttyS0, as
|
| /linux-4.4.14/arch/x86/ |
| D | Makefile | 163 cfi := $(call as-instr,.cfi_startproc\n.cfi_rel_offset $(sp-y)$(comma)0\n.cfi_endproc,-DCONFIG_AS_C…
165 cfi-sigframe := $(call as-instr,.cfi_startproc\n.cfi_signal_frame\n.cfi_endproc,-DCONFIG_AS_CFI_SIG…
166 cfi-sections := $(call as-instr,.cfi_sections .debug_frame,-DCONFIG_AS_CFI_SECTIONS=1)
169 asinstr := $(call as-instr,fxsaveq (%rax),-DCONFIG_AS_FXSAVEQ=1)
170 asinstr += $(call as-instr,pshufb %xmm0$(comma)%xmm0,-DCONFIG_AS_SSSE3=1)
171 asinstr += $(call as-instr,crc32l %eax$(comma)%eax,-DCONFIG_AS_CRC32=1)
172 avx_instr := $(call as-instr,vxorps %ymm0$(comma)%ymm1$(comma)%ymm2,-DCONFIG_AS_AVX=1)
173 avx2_instr :=$(call as-instr,vpbroadcastb %xmm0$(comma)%ymm1,-DCONFIG_AS_AVX2=1)
174 sha1_ni_instr :=$(call as-instr,sha1msg1 %xmm0$(comma)%xmm1,-DCONFIG_AS_SHA1_NI=1)
175 sha256_ni_instr :=$(call as-instr,sha256msg1 %xmm0$(comma)%xmm1,-DCONFIG_AS_SHA256_NI=1)
|
| /linux-4.4.14/drivers/firewire/ |
| D | Kconfig | 18 To compile this driver as a module, say M here: the module will be
29 To compile this driver as a module, say M here: The module will be
41 To compile this driver as a module, say M here: The module will be
52 with other implementations of RFC 2734/3146 as found on several
55 To compile this driver as a module, say M here: The module will be
67 link layer controller TSB12LV21/A/B as a low-budget bus analyzer.
77 To compile this driver as a module, say M here: The module will be
|
| /linux-4.4.14/drivers/media/radio/ |
| D | Kconfig | 44 To compile this driver as a module, choose M here: the
56 To compile this driver as a module, choose M here: the
68 To compile this driver as a module, choose M here: the
77 found as Gemtek PCI FM.
84 To compile this driver as a module, choose M here: the
102 To compile this driver as a module, choose M here: the
119 To compile this driver as a module, choose M here: the
129 To compile this driver as a module, choose M here: the
143 To compile this driver as a module, choose M here: the
155 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/fs/coda/ |
| D | Kconfig | 7 with regular Unix commands as if they were sitting on your hard
13 If you say Y here, your Linux box will be able to act as a Coda
14 *client*. You will need user level code as well, both for the
20 To compile the coda client support as a module, choose M here: the
|
| /linux-4.4.14/Documentation/arm/Samsung/ |
| D | GPIO.txt | 22 The gpio implementation uses gpiolib as much as possible, only providing
24 as pin special-function or pull resistor control.
34 implementation to configure pins as necessary.
|
| /linux-4.4.14/drivers/staging/lustre/lnet/ |
| D | Kconfig | 20 as a module, choose M here: the module will be called lnet_selftest.
22 To compile this as a kernel modules, choose M here and it will be
34 This option allows the LNET users to use infiniband as an
37 To compile this as a kernel module, choose M here and it will be
|
| /linux-4.4.14/drivers/net/ethernet/mellanox/mlxsw/ |
| D | Kconfig | 10 To compile this driver as a module, choose M here: the
20 To compile this driver as a module, choose M here: the
31 To compile this driver as a module, choose M here: the
42 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/arch/mips/loongson32/ |
| D | Kconfig | 42 Use PWM Timer 0 as the default clockevent/clocksourcer.
47 Use PWM Timer 1 as the default clockevent/clocksourcer.
52 Use PWM Timer 2 as the default clockevent/clocksourcer.
57 Use PWM Timer 3 as the default clockevent/clocksourcer.
|
| /linux-4.4.14/drivers/pci/hotplug/ |
| D | Kconfig | 24 To compile this driver as a module, choose M here: the
46 To compile this driver as a module, choose M here: the
67 To compile this driver as a module, choose M here: the
87 To compile this driver as a module, choose M here: the
97 hotswap signal as a bit in a system register that can be read through
100 To compile this driver as a module, choose M here: the
111 To compile this driver as a module, choose M here: the
122 To compile this driver as a module, choose M here: the
134 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/Documentation/leds/ |
| D | leds-class.txt | 37 and the aim is to keep a small amount of code giving as much functionality
38 as possible. Please keep this in mind when suggesting enhancements.
48 There have been calls for LED properties such as colour to be exported as
49 individual led class attributes. As a solution which doesn't incur as much
61 however, it is better to use the API function led_blink_set(), as it
65 as that will not just set the LED brightness but also stop any software
81 The LED Trigger core cannot be a module as the simple trigger functions
82 would cause nightmare dependency issues. I see this as a minor issue
|
| /linux-4.4.14/drivers/net/ethernet/smsc/ |
| D | Kconfig | 32 To compile this driver as a module, choose M here. The module
48 This driver is also available as a module ( = code which can be
50 The module will be called smc91x. If you want to compile it as a
62 To compile this driver as a module, choose M here: the module will be
86 This driver is also available as a module. The module will be
87 called smc911x. If you want to compile it as a module, say M
100 To compile this driver as a module, choose M here. The module
121 This driver is also available as a module. The module will be
122 called smsc9420. If you want to compile it as a module, say M
|
| /linux-4.4.14/drivers/media/rc/ |
| D | Kconfig | 150 To compile this driver as a module, choose M here: the module will be
164 To compile this driver as a module, choose M here: the
172 To compile this driver as a module, choose M here: the module will be
186 To compile this driver as a module, choose M here: the
198 To compile this driver as a module, choose M here: the
211 To compile this driver as a module, choose M here: the
223 To compile this driver as a module, choose M here: the
234 To compile this driver as a module, choose M here: the
244 found in the ASRock ION 330HT, as well as assorted Intel
247 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | intel-bts.txt | 7 Intel BTS could be regarded as a predecessor to Intel PT and has some
9 notable difference is that Intel BTS has no timing information and as a
39 The snapshot option is the same as Intel PT (refer Intel PT documentation).
45 The mmap size option is the same as Intel PT (refer Intel PT documentation).
53 the same as Intel PT (refer Intel PT documentation) except that neither
76 This can be further controlled by new option --itrace exactly the same as
|
| /linux-4.4.14/drivers/mtd/onenand/ |
| D | Kconfig | 44 One Block of the NAND Flash Array memory is reserved as
46 Also, 1st Block of NAND Flash Array can be used as OTP.
49 operations as any other NAND Flash Array memory block.
60 of 4KiB. Plane1 has only even blocks such as block0, block2, block4
61 while Plane2 has only odd blocks such as block1, block3, block5.
62 So MTD regards it as 4KiB page size and 256KiB block size
|
| /linux-4.4.14/drivers/usb/atm/ |
| D | Kconfig | 15 To compile this driver as a module, choose M here: the
29 To compile this driver as a module, choose M here: the
41 To compile this driver as a module, choose M here: the
53 To compile this driver as a module, choose M here: the
62 and reception as module parameters. You may need to initialize
65 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/Documentation/laptops/ |
| D | toshiba_haps.txt | 27 userspace tools or daemons act accordingly, as well as providing a sysfs
44 any "protection" as well as failing during the evaluation of the _STA method
71 level, as well as set the desired protection level, the
|
| /linux-4.4.14/drivers/i2c/muxes/ |
| D | Kconfig | 18 This driver can also be built as a module. If so, the module
30 This driver can also be built as a module. If so, the module
39 This driver can also be built as a module. If so, the module
49 This driver can also be built as a module. If so, the module
61 This driver can also be built as a module. If so, the module will be
72 This driver can also be built as a module. If so, the module
|
| /linux-4.4.14/drivers/net/wan/ |
| D | Kconfig | 8 Wide Area Networks (WANs), such as X.25, Frame Relay and leased
34 The driver will be compiled as a module: the
37 # The COSA/SRP driver has not been tested as non-modular yet.
46 V.36 interface) to your Linux box. The cards can work as the
56 The driver will be compiled as a module: the
81 To change setting such as clock source you will need lmcctl.
84 To compile this driver as a module, choose M here: the
94 The driver will be compiled as a module: the
110 To compile this driver as a module, choose M here: the
178 To compile this as a module, choose M here: the
[all …]
|
| /linux-4.4.14/drivers/net/irda/ |
| D | Kconfig | 11 discipline. To compile it as a module, choose M here: the module
31 Saying M, it will be built as a module named bfin_sir.
94 JetEye PC dongle. To compile it as a module, choose M here. The ESI
105 IR220L+ dongles. To compile it as a module, choose M here. The
116 dongle. To compile it as a module, choose M here. The Tekram dongle
128 To compile it as a module, choose M here.
135 dongle. To compile it as a module, choose M here. The Parallax
146 dongle. To compile it as a module, choose M here. The MA600 dongle
159 dongle. If you want to compile it as a module, choose M here.
170 dongle. If you want to compile it as a module, choose M here.
[all …]
|
| /linux-4.4.14/Documentation/power/ |
| D | opp.txt | 35 We can represent these as three OPPs as the following {Hz, uV} tuples:
46 CONFIG_PM as certain SoCs such as Texas Instrument's OMAP framework allows to
49 Typical usage of the OPP library is as follows:
73 be used for dev_pm_opp_enable/disable functions to make an opp available as required.
78 dependent subsystems such as cpufreq are left to the discretion of the SoC
86 intensive operations on data structure as the OPP library caters to.
88 To ensure that the data retrieved are sane, the users such as SoC framework
112 used by SoC framework to define a optimal list as per the demands of
133 High level framework such as cpufreq operates on frequencies. To map the
138 error checks such as IS_ERR() and appropriate actions taken by the caller.
[all …]
|
| D | suspend-and-interrupts.txt | 22 of suspended devices and cause unpredictable behavior to ensue as a result.
37 devices as well as during the time when nonboot CPUs are taken offline and
43 leave the corresponding IRQ enabled so as to allow the interrupt to work as
50 for it will be executed as usual after suspend_device_irqs(), even if the
60 from sleep states, especially if they are used for different purposes (e.g. as
64 (such as an SoC) so that signals from a given line are routed in a different way
65 during system sleep so as to trigger a system wakeup when needed. For example,
75 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
80 it will be disabled, marked as pending and "suspended" so that it will be
97 Suspend-to-idle (also known as the "freeze" sleep state) is a relatively new
[all …]
|
| /linux-4.4.14/drivers/misc/lis3lv02d/ |
| D | Kconfig | 16 the laptop to act as a pinball machine-esque joystick.
18 This driver can also be built as modules. If so, the core module
33 the device to act as a pinball machine-esque joystick.
35 This driver can also be built as modules. If so, the core module
|
| /linux-4.4.14/drivers/net/wireless/mwifiex/ |
| D | Kconfig | 8 If you choose to build it as a module, it will be called
20 If you choose to build it as a module, it will be called
32 If you choose to build it as a module, it will be called
43 If you choose to build it as a module, it will be called
|
| /linux-4.4.14/drivers/net/hamradio/ |
| D | Kconfig | 16 To compile this driver as a module, choose M here: the module
24 PC and your TNC (the Terminal Node Controller acts as a kind of
26 microphone input and speaker output). This protocol can be used as
34 To compile this driver as a module, choose M here: the module
53 computer to an amateur radio modem (such as the WA4DSY 56kbps
63 compile it as a module (by saying M instead of Y), it will be called
68 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
73 certain parameters, such as channel access timing, clock mode, and
77 get at least version 1.27 of dmascc_cfg, as older versions will not
91 To compile this driver as a module, choose M here: the module
[all …]
|
| /linux-4.4.14/drivers/scsi/ |
| D | Kconfig | 32 To compile this driver as a module, choose M here and read
36 However, do not compile this as a module if your root file system
85 To compile this driver as a module, choose M here and read
89 Do not compile this driver as a module if your root file system
92 (below) as a module either.
104 To compile this driver as a module, choose M here and read
114 you may be able to drive the USB-x0 and DI-x0 drives as well.
123 Please also have a look at the standard st docu, as most of it
124 applies to osst as well.
126 To compile this driver as a module, choose M here and read
[all …]
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-iov-howto.txt | 14 capability which makes one physical device appear as multiple virtual
15 devices. The physical device is referred to as Physical Function (PF)
16 while the virtual devices are referred to as Virtual Functions (VF).
19 not enabled and the PF behaves as traditional PCIe device. Once it's
23 operates on the register set so it can be functional and appear as a
48 The VF is treated as hot-plugged PCI devices in the kernel, so they
49 should be able to work in the same way as real PCI devices. The VF
50 requires device driver that is same as a normal PCI device's.
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/ |
| D | atmel,lcdc.txt | 23 as specified below.
53 Required properties (as per of_videomode_helper):
60 Optional properties (as per of_videomode_helper):
64 - atmel,power-control-gpio: gpio to power on or off the LCD (as many as needed)
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | clocking.txt | 11 Every audio subsystem is driven by a master clock (sometimes referred to as MCLK
24 as BCLK). This clock is used to drive the digital audio data across the link
28 clock is sometimes referred to as LRC (left right clock) or FRAME. This clock
31 Bit Clock can be generated as follows:-
48 audio clocks as it usually gives more accurate sample rates than the CPU.
|
| /linux-4.4.14/Documentation/ia64/ |
| D | serial.txt | 13 as a serial console. If the user specified "console=ttyS0"
15 kernel registered the device described by the HCDP as
20 the kernel registered those as /dev/ttyS0 and /dev/ttyS1.
23 after /dev/ttyS0 as they were discovered.
56 card) as the console. Then you don't need to tell Linux
95 - Multiple UARTs selected as EFI console devices. EFI and
101 selected as EFI console device. EFI uses the MP as a
123 "login:" prompt, but can't login as root:
137 The table was originally defined as the "HCDP" for "Headless
142 several UARTs. One of the UARTs is often used as a console; the
[all …]
|
| /linux-4.4.14/drivers/net/ethernet/8390/ |
| D | Kconfig | 28 To compile this driver as a module, choose M here: the module will be
55 To compile this driver as a module, choose M here: the module
82 some SnapGear routers do as well.
85 on them then choose Y. To compile this driver as a module, choose M
101 To compile this driver as a module, choose M here. The module
119 To compile this driver as a module, choose M here. The module
130 To compile this driver as a module, choose M here: the module
141 To compile this driver as a module, choose M here: the module will be
165 such as some BusLogic models) causes corruption problems with many
170 To compile this driver as a module, choose M here. The module
[all …]
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | timekeeping.txt | 46 speaker. Now the PIT is typically integrated as part of an emulated chipset
51 available, but not all modes are available to all timers, as only timer 2
53 controlled by port 61h, bit 0, as illustrated in the following diagram.
146 0100 - Latch Timer 1 count for port 0x41 - as described above
147 0101 - Set Timer 1 LSB mode for port 0x41 - as described above
148 0110 - Set Timer 1 MSB mode for port 0x41 - as described above
149 0111 - Set Timer 1 16-bit mode for port 0x41 - as described above
151 1000 - Latch Timer 2 count for port 0x42 - as described above
152 1001 - Set Timer 2 LSB mode for port 0x42 - as described above
153 1010 - Set Timer 2 MSB mode for port 0x42 - as described above
[all …]
|
| /linux-4.4.14/drivers/bluetooth/ |
| D | Kconfig | 31 kernel or say M to compile it as module (btusb).
64 kernel or say M to compile it as module (btsdio).
77 kernel or say M to compile it as module (hci_uart).
182 kernel or say M to compile it as module (bcm203x).
194 kernel or say M to compile it as module (bpa10x).
207 kernel or say M to compile it as module (bfusb).
220 kernel or say M to compile it as module (dtl1_cs).
234 kernel or say M to compile it as module (bt3c_cs).
247 kernel or say M to compile it as module (bluecard_cs).
263 kernel or say M to compile it as module (btuart_cs).
[all …]
|
| /linux-4.4.14/drivers/staging/rtl8188eu/ |
| D | Kconfig | 7 This option adds the Realtek RTL8188EU USB device such as TP-Link TL-WN725N.
8 If built as a module, it will be called r8188eu.
17 will never be used as an AP, or the target system has limited memory,
|
| /linux-4.4.14/drivers/net/ |
| D | Kconfig | 16 two machines with parallel ports using PLIP needs this, as well as
55 To compile this driver as a module, choose M here: the module
71 To compile this driver as a module, choose M here: the module
82 to be supported at the other end as well, either with a similar EQL
90 To compile this driver as a module, choose M here: the module
112 To compile this driver as a module, choose M here: the module
114 device at a time, you need to compile this driver as a module.
132 To compile this driver as a module, choose M here: the module
142 can be added in the same way as a macvlan device, using 'type
145 To compile this driver as a module, choose M here: the module
[all …]
|
| /linux-4.4.14/arch/ia64/kernel/ |
| D | efi.c | 975 u64 as = 0, ae; in find_memmap_space() local
1017 as = max(contig_low, md->phys_addr); in find_memmap_space()
1021 as = max(as, min_addr); in find_memmap_space()
1023 if (ae <= as) in find_memmap_space()
1027 if (total_mem + (ae - as) > mem_limit) in find_memmap_space()
1028 ae -= total_mem + (ae - as) - mem_limit; in find_memmap_space()
1030 if (ae <= as) in find_memmap_space()
1033 if (ae - as > space_needed) in find_memmap_space()
1039 return __va(as); in find_memmap_space()
1052 u64 as, ae, lim; in efi_memmap_init() local
[all …]
|
| /linux-4.4.14/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 20 commonly referred to as "guest drivers" or "client drivers". All drivers
23 to as "function drivers".
29 as the "service partition", "IO partition" (for virtual network and scsi disk
65 implementation for struct visor_driver and struct visor_device, as well
66 as utility functions for communicating with the back-end.
69 as a module it will typically be loaded automatically via standard udev or
73 devices it discovers, as it includes a MODALIAS environment variable of this
98 exchange is as follows:
100 * the GUID(s) of the channel type(s) that are handled by this driver, as
101 well as a "friendly name" identifying each (this will be published under
[all …]
|
| /linux-4.4.14/drivers/staging/media/bcm2048/ |
| D | TODO | 10 The sysfs stuff should be replaced by controls as well. A lot of the RDS
11 support is now available as controls (although there may well be some
16 Correct Coding Style, as this driver also violates several Style
22 radio-si4713/si4713-i2c.c as a good example. But I would wait with that
|
| /linux-4.4.14/drivers/iio/temperature/ |
| D | Kconfig | 13 This driver can also be built as a module. If so, the module will
23 This driver can also be built as a module. If so, the module will
34 This driver can also be built as a module. If so, the module will
45 This driver can also be built as a module. If so, the module will
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | timer.txt | 13 optionally as well, 2 watchdog interrupts, in that order.
18 must appear in the same order as the clock names.
20 - clock-names: The name of the clocks as free-form strings. They should be in
21 the same order as the clocks.
|
| /linux-4.4.14/drivers/media/pci/ivtv/ |
| D | Kconfig | 25 This is used in devices such as the Hauppauge PVR-150/250/350/500
28 To compile this driver as a module, choose M here: the
36 This driver provides an ALSA interface as another method for user
44 To compile this driver as a module, choose M here: the
63 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/drivers/w1/masters/ |
| D | Kconfig | 14 This support is also available as a module. If so, the module
24 This support is also available as a module. If so, the module
34 This driver can also be built as a module. If so, the module
46 Say Y here to enable the DS1WM 1-wire driver, such as that
57 This support is also available as a module. If so, the module
|
| /linux-4.4.14/drivers/net/ieee802154/ |
| D | Kconfig | 20 This driver can also be built as a module. To do so say M here.
32 This driver can also be built as a module. To do so, say M here.
51 This driver can also be built as a module. To do so, say M here.
62 This driver can also be built as a module. To do so, say M here.
72 This driver can also be built as a module. To do so say M here.
|
| /linux-4.4.14/drivers/input/gameport/ |
| D | Kconfig | 19 To compile this driver as a module, choose M here: the
31 To compile this driver as a module, choose M here: the
39 To compile this driver as a module, choose M here: the
49 To compile this driver as a module, choose M here: the
60 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/Documentation/virtual/kvm/devices/ |
| D | mpic.txt | 9 MPIC will act as the system interrupt controller, connecting to each
21 Access an MPIC register, as if the access were made from the guest.
42 be instantiated. Once that device has been created, it's available as
48 The numbering is the same as the MPIC device tree binding -- based on
50 regard to any subdivisions in chip documentation such as "internal"
|
| /linux-4.4.14/drivers/net/ethernet/atheros/ |
| D | Kconfig | 27 To compile this driver as a module, choose M here. The module
39 To compile this driver as a module, choose M here. The module
50 To compile this driver as a module, choose M here. The module
61 To compile this driver as a module, choose M here. The module
78 To compile this driver as a module, choose M here. The module
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | cpia2_overview.txt | 9 be referred to as the 410 and the 500 sensors, or the CIF and VGA sensors.
15 header files are marked with VP4 or VP5 as part of the symbol name.
17 The cameras appear externally as three sets of registers. Setting register
19 interdependant, such as the sequence required to power up the camera. I will
24 registers that control housekeeping functions such as powering up the video
29 compressed as Motion JPEG (JPEGA). The VC controls all of the compression
|
| /linux-4.4.14/drivers/net/appletalk/ |
| D | Kconfig | 11 so that your Linux box can act as a print and file server for Macs as
12 well as access AppleTalk printers. Check out
23 information as well.
25 To compile this driver as a module, choose M here: the module will be
26 called appletalk. You almost certainly want to compile it as a
46 networks. The card is also known as the Farallon PhoneNet PC card.
86 you want your Linux box to act as an Internet gateway for a zoo of
95 To compile the AppleTalk-IP support as a module, choose M here: the
|
| /linux-4.4.14/drivers/net/ethernet/amd/ |
| D | Kconfig | 30 To compile this driver as a module, choose M here: the module
42 To compile this driver as a module, choose M here. The module
52 To compile this driver as a module, choose M here: the module
64 To compile this driver as a module, choose M here. The module
74 To compile this driver as a module, choose M here: the module
127 To compile this driver as a module, choose M here.
136 To compile this driver as a module, choose M here: the module will be
145 To compile this driver as a module, choose M here. The module
167 systems, on some older Ultra systems and as an Sbus option. These
171 To compile this driver as a module, choose M here: the module
[all …]
|
| /linux-4.4.14/drivers/input/mouse/ |
| D | Kconfig | 24 includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
38 To compile this driver as a module, choose M here: the
118 Say Y here if you have a laptop (such as MSI WIND Netbook)
174 To compile this driver as a module, choose M here: the
195 To compile this driver as a module, choose M here: the
218 To compile this driver as a module, choose M here: the
231 To compile this driver as a module, choose M here: the module will be
242 To compile this driver as a module, choose M here: the module will be
271 To compile this driver as a module, choose M here: the
287 To compile this driver as a module, choose M here: the
[all …]
|
| /linux-4.4.14/arch/powerpc/kvm/ |
| D | e500_mmu.c | 84 gva_t eaddr, int tlbsel, unsigned int pid, int as) in kvmppc_e500_tlb_index() argument
120 if (get_tlb_ts(tlbe) != as && as != -1) in kvmppc_e500_tlb_index()
130 gva_t eaddr, int as) in kvmppc_e500_deliver_tlb_miss() argument
143 vcpu->arch.shared->mas1 = MAS1_VALID | (as ? MAS1_TS : 0) in kvmppc_e500_deliver_tlb_miss()
151 | (as ? MAS6_SAS : 0); in kvmppc_e500_deliver_tlb_miss()
347 int as = !!get_cur_sas(vcpu); in kvmppc_e500_emul_tlbsx() local
353 esel = kvmppc_e500_tlb_index(vcpu_e500, ea, tlbsel, pid, as); in kvmppc_e500_emul_tlbsx()
457 gva_t eaddr, unsigned int pid, int as) in kvmppc_e500_tlb_search() argument
463 esel = kvmppc_e500_tlb_index(vcpu_e500, eaddr, tlbsel, pid, as); in kvmppc_e500_tlb_search()
478 u8 as; in kvmppc_core_vcpu_translate() local
[all …]
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | paride.txt | 9 to personal computers, many external devices such as portable hard-disk,
20 device registers, as well as data block transfer functions. Sometimes,
50 as well as most of the clone and no-name products on the market.
91 the PARIDE drivers into your kernel, or to build them as modules.
94 as well as at least one of the high-level drivers and at least one
126 configure them as loadable modules, before attempting to compile a
148 paride: bpck registered as protocol 0
149 paride: epat registered as protocol 1
152 different protocol selections. You should note these numbers as you
177 2.2 Loading and configuring PARIDE as modules
[all …]
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | cxlflash.txt | 6 on Power 8 systems. CAPI can be thought of as a special tunneling
15 devices as a PCI device by implementing a virtual PCI host bridge.
26 SCSI stack as a low level device driver (below the SCSI disk and
31 as described in Documentation/powerpc/cxl.txt.
36 - Any flash device (LUN) can be configured to be accessed as a
42 either raw access to the entire LUN (referred to as direct
44 partition of the LUN (referred to as virtual LUN access). The
76 This driver configures itself into the SCSI software stack as an
94 virtual LUNs. The virtual LUNs may be resized as long as the sum of
112 space should use the block library, as it abstracts the details of
[all …]
|
| /linux-4.4.14/Documentation/target/ |
| D | tcmu-design.txt | 26 allows userspace programs to be written which act as iSCSI targets.
31 modules for file, block device, RAM or using another SCSI device as
33 built-in modules are implemented entirely as kernel code.
39 the actual data storage as well. These are referred to as "backstores"
43 these are implemented entirely as kernel code.
46 use case that other non-kernel target solutions, such as tgt, are able
47 to support is using Gluster's GLFS or Ceph's RBD as a backstore. The
48 target then serves as a translator, allowing initiators to store data
73 fatal if we're careful to keep things as simple as possible.
105 expressed as an offset from the region's starting address. This allows
[all …]
|
| /linux-4.4.14/Documentation/ide/ |
| D | ide.txt | 54 This is the multiple IDE interface driver, as evolved from hd.c.
57 14 & 15). There can be up to two drives per interface, as per the ATA-6 spec.
93 specified, though the "original" geometry may be retained as the "logical"
107 jumpered as "single" or "master", *not* "slave". Many folks have had
113 such as the NEC-260 and the new MITSUMI triple/quad speed drives.
118 via LILO, such as:
158 provided it is mounted with the default block size of 1024 (as above).
164 drivers can always be compiled as loadable modules, the chipset drivers
166 compiled as a loadable module provided no chipset support is needed.
168 When using ide.c as a module in combination with kmod, add:
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-gpio.txt | 9 - i2c-gpio,sda-open-drain: sda as open drain
10 - i2c-gpio,scl-open-drain: scl as open drain
11 - i2c-gpio,scl-output-only: scl as output only
|
| /linux-4.4.14/net/mac80211/ |
| D | Kconfig | 57 Select Minstrel as the default rate control algorithm.
80 possible, as drafts leave a number of identifiers to be defined after
142 on production systems as some of the messages are
153 should not be selected on production systems as some
174 It should not be selected on production systems as some
185 be selected on production systems as those messages
196 be selected on production systems as those messages
208 It should not be selected on production systems as those
221 It should not be selected on production systems as those
234 It should not be selected on production systems as those
[all …]
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Kconfig | 4 # PARIDE doesn't need PARPORT, but if PARPORT is configured as a module,
19 it as a loadable module. The module will be called pd. You
33 build it as a loadable module. The module will be called pcd. You
49 to build it as a loadable module. The module will be called pf.
63 to build it as a loadable module. The module will be called pt.
74 programs, such as cdrtools, to send ATAPI commands directly to a
79 otherwise you should answer M to build it as a loadable module. The
103 protocol driver, otherwise you should answer M to build it as a
122 answer M to build it as a loadable module. The module will be
141 answer M to build it as a loadable module. The module will be
[all …]
|
| /linux-4.4.14/Documentation/hid/ |
| D | hid-transport.txt | 12 The HID subsystem is designed as a bus. Any I/O subsystem may provide HID
48 Everything below "HID Core" is simplified in this graph as it is only of
67 HID core will operate a device as long as it is registered regardless of any
81 driver in whatever way they like. They might just be the same as asynchronous
92 will describe them as two bi-directional channels as they have several
129 on the intr channel as this channel is asynchronous.
131 INPUT and OUTPUT reports can be sent as pure data reports on the intr channel.
133 this is rarely done as OUTPUT reports are normally quite scarce. But devices are
141 - GET_REPORT: A GET_REPORT request has a report ID as payload and is sent
143 requested report ID on the ctrl channel as a synchronous acknowledgement.
[all …]
|
| /linux-4.4.14/net/ipv4/netfilter/ |
| D | Kconfig | 26 To compile it as a module, choose M here. If unsure, say N.
53 fields such as the source, destination, type of service and
116 packet transformations such as the source, destination address and
156 This is the "basic" form of SNMP-ALG, as described in RFC 2962
158 To compile it as a module, choose M here. If unsure, say N.
187 To compile it as a module, choose M here. If unsure, say N.
199 To compile it as a module, choose M here. If unsure, say N.
218 To compile it as a module, choose M here. If unsure, say N.
239 To compile it as a module, choose M here. If unsure, say N.
251 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-4.4.14/drivers/media/usb/go7007/ |
| D | Kconfig | 20 To compile this driver as a module, choose M here: the
30 To compile this driver as a module, choose M here: the
41 To compile this driver as a module, choose M here: the
50 To compile this driver as a module, choose M here: the
|
| /linux-4.4.14/firmware/keyspan/ |
| D | usa19.HEX | 88 as an unpublished work. This notice does not imply unrestricted or
90 derived. Except as noted below this firmware image may not be
95 image as part of a Linux or other Open Source operating system kernel
96 in text or binary form as required.
|
| D | usa19qi.HEX | 88 as an unpublished work. This notice does not imply unrestricted or
90 derived. Except as noted below this firmware image may not be
95 image as part of a Linux or other Open Source operating system kernel
96 in text or binary form as required.
|
| /linux-4.4.14/sound/firewire/ |
| D | Kconfig | 23 To compile this driver as a module, choose M here: the module
43 To compile this driver as a module, choose M here: the module
53 To compile this driver as a module, choose M here: the module
64 To compile this driver as a module, choose M here: the module
80 To compile this driver as a module, choose M here: the module
121 To compile this driver as a module, choose M here: the module
136 To compile this driver as a module, choose M here: the module
148 To compile this driver as a module, choose M here: the module
|