| /linux-4.4.14/net/can/ |
| D | Makefile | 5 obj-$(CONFIG_CAN) += can.o
6 can-y := af_can.o proc.o
8 obj-$(CONFIG_CAN_RAW) += can-raw.o
9 can-raw-y := raw.o
11 obj-$(CONFIG_CAN_BCM) += can-bcm.o
12 can-bcm-y := bcm.o
14 obj-$(CONFIG_CAN_GW) += can-gw.o
15 can-gw-y := gw.o
|
| D | Kconfig | 14 is contained in <Documentation/networking/can.txt>.
37 interaction. The BCM can be 'programmed' via the BSD socket API and
49 msg sending and can optionally modify routed CAN frames on the fly.
50 CAN frames can be routed between CAN network interfaces (one hop).
51 They can be modified with AND/OR/XOR/SET operations as configured
54 source "drivers/net/can/Kconfig"
|
| /linux-4.4.14/Documentation/power/regulator/ |
| D | consumer.txt | 11 A consumer driver can get access to its supply regulator by calling :-
24 Consumers can be supplied by more than one regulator e.g. codec consumer with
37 A consumer can enable its power supply by calling:-
45 A consumer can determine if a regulator is enabled by calling :-
52 A consumer can disable its supply when no longer needed by calling :-
59 Finally, a regulator can be forcefully disabled in the case of an emergency :-
71 voltage to match system operating points. e.g. CPUfreq drivers can scale
75 Consumers can control their supply voltage by calling :-
82 NOTE: this can be called when the regulator is enabled or disabled. If called
87 The regulators configured voltage output can be found by calling :-
[all …]
|
| D | regulator.txt | 11 Drivers can register a regulator by calling :-
19 Regulators can be unregistered by calling :-
26 Regulators can send events (e.g. overtemperature, undervoltage, etc) to
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/can/ |
| D | rcar_can.txt | 5 - compatible: "renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC.
6 "renesas,can-r8a7779" if CAN controller is a part of R8A7779 SoC.
7 "renesas,can-r8a7790" if CAN controller is a part of R8A7790 SoC.
8 "renesas,can-r8a7791" if CAN controller is a part of R8A7791 SoC.
17 - renesas,can-clock-select: R-Car CAN Clock Source Select. Valid values are:
27 can0: can@e6e80000 {
28 compatible = "renesas,can-r8a7791";
|
| D | sun4i_can.txt | 5 - compatible: "allwinner,sun4i-a10-can"
17 allwinner,function = "can";
22 can0: can@01c2bc00 {
23 compatible = "allwinner,sun4i-a10-can";
32 can0: can@01c2bc00 {
|
| D | atmel-can.txt | 4 - compatible: Should be "atmel,at91sam9263-can" or "atmel,at91sam9x5-can"
10 can0: can@f000c000 {
11 compatible = "atmel,at91sam9x5-can";
|
| D | xilinx_can.txt | 5 - compatible : Should be "xlnx,zynq-can-1.0" for Zynq CAN
6 controllers and "xlnx,axi-can-1.00.a" for Axi CAN
24 zynq_can_0: can@e0008000 {
25 compatible = "xlnx,zynq-can-1.0";
35 axi_can_0: axi-can@40000000 {
36 compatible = "xlnx,axi-can-1.00.a";
|
| D | mpc5xxx-mscan.txt | 9 In addition to the required compatible-, reg- and interrupt-properties, you can
20 In addition to the required compatible-, reg- and interrupt-properties, you can
33 clock divider can be specified. By default, a
39 can@1300 {
46 can@1380 {
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | Kconfig | 9 kernel, it can speak everything on the text console from
13 can subscribe to.
21 that can be used with a plain text terminal.
23 Speakup can either be built in or compiled as a module
27 the synthesizer drivers below can only be built as
35 The Dectalk pc driver can only be built as a module, and
37 the module can be loaded. See the decpc choice below
48 synthesizer. You can say y to build it into the kernel,
57 synthesizer. You can say y to build it into the kernel,
65 synthesizer. You can say y to build it into the kernel,
[all …]
|
| /linux-4.4.14/drivers/hwmon/ |
| D | Kconfig | 12 can include temperature sensors, voltage sensors, fan speed
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
62 chip can be found on Abit uGuru featuring motherboards (most modern
67 This driver can also be built as a module. If so, the module
77 uGuru chip can be found on recent Abit motherboards (since end
81 This driver can also be built as a module. If so, the module
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
[all …]
|
| /linux-4.4.14/net/netfilter/ipset/ |
| D | Kconfig | 8 ipset(8). You can use the sets in netfilter via the "set" match
21 You can define here default value of the maximum number
24 The value can be overridden by the 'max_sets' module
32 can store IPv4 addresses (or network addresse) from a range.
41 can store IPv4 address and (source) MAC address pairs from a range.
50 can store TCP/UDP port numbers from a range.
59 can store arbitrary IPv4 or IPv6 addresses (or network addresses)
69 can store IPv4/IPv6 address and mark pairs.
78 can store IPv4/IPv6 address and protocol/port pairs.
87 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
[all …]
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Transition-notes | 2 If ps_tq is scheduled, ps_tq_active is 1. ps_tq_int() can be called
5 under ps_spinlock. There are three places where that can happen:
7 Consider the sequnce of these events. A can not be preceded by
9 ps_spinlock. C is always preceded by B, since we can't reach it
11 IOW, the sequence is A?(BA|BC|B)*. OTOH, number of B can not exceed
16 since at any time number of B can not exceed the number of these
17 moments which, in turn, can not exceed the number of A and C.
49 1) at any time at most one thread of execution can be in that area or
60 (1) can become not true if some thread enters that area while another is there.
61 a) do_pd_request1() can be called from next_request() or do_pd_request()
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/usb/ |
| D | atmel-usb.txt | 102 - atmel,can-dma: Boolean to specify if the endpoint support DMA.
103 - atmel,can-isoc: Boolean to specify if the endpoint support ISOC.
126 atmel,can-dma;
127 atmel,can-isoc;
134 atmel,can-dma;
135 atmel,can-isoc;
142 atmel,can-dma;
149 atmel,can-dma;
156 atmel,can-dma;
157 atmel,can-isoc;
[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/drivers/net/can/sja1000/ |
| D | sja1000.c | 127 priv->can.state = CAN_STATE_STOPPED; in set_reset_mode()
150 priv->can.state = CAN_STATE_ERROR_ACTIVE; in set_normal_mode()
152 if (priv->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING) in set_normal_mode()
161 if (priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) in set_normal_mode()
163 if (priv->can.ctrlmode & CAN_CTRLMODE_PRESUME_ACK) in set_normal_mode()
209 if (priv->can.state != CAN_STATE_STOPPED) in sja1000_start()
247 struct can_bittiming *bt = &priv->can.bittiming; in sja1000_set_bittiming()
253 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) in sja1000_set_bittiming()
324 if (priv->can.ctrlmode & CAN_CTRLMODE_ONE_SHOT) in sja1000_start_xmit()
327 if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) in sja1000_start_xmit()
[all …]
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi.txt | 7 It can also be found at:
12 The scsi support in the linux kernel can be modularized in a number of
17 support. Without it you can do nothing with any of the other scsi drivers.
18 The scsi core support can be a module (scsi_mod.o), or it can be built into
25 The individual upper and lower level drivers can be loaded in any order
29 level drivers to support the various assorted devices which can be
30 controlled. You can for example load the tape driver to use the tape drive,
38 Adaptec. Almost all lower level drivers can be built either as modules or
|
| D | scsi-generic.txt | 36 and pdf. This document can also be found at:
39 Documentation for the version 2 sg driver found in the lk 2.2 series can
43 The original documentation for the sg driver (prior to lk 2.2.6) can be
47 A changelog with brief notes can be found in the
51 can be found at the top of the /usr/src/linux/drivers/scsi/sg.c file.
54 part can be found at http://www.tldp.org/HOWTO/SCSI-2.4-HOWTO .
64 capabilities. They can be found at: http://sg.danny.cz/sg/sg3_utils.html and
|
| /linux-4.4.14/drivers/rtc/ |
| D | Kconfig | 67 one can sleep when setting time, because it runs in the workqueue
110 can be accessed as /dev/rtc, which is a name
132 RTC test driver. It's a software RTC which can be
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
212 This driver can also be built as a module. If so, the module
[all …]
|
| /linux-4.4.14/fs/nls/ |
| D | Kconfig | 42 The Microsoft FAT file system family can deal with filenames in
47 only, not to the file contents. You can include several codepages;
54 The Microsoft FAT file system family can deal with filenames in
59 only, not to the file contents. You can include several codepages;
66 The Microsoft FAT file system family can deal with filenames in
71 only, not to the file contents. You can include several codepages;
79 The Microsoft FAT file system family can deal with filenames in
84 only, not to the file contents. You can include several codepages;
95 The Microsoft FAT file system family can deal with filenames in
100 only, not to the file contents. You can include several codepages;
[all …]
|
| /linux-4.4.14/Documentation/hid/ |
| D | hid-sensor.txt | 16 and also the individual data fields. Each sensor can have variable number of
18 example a part of report descriptor can look like:
47 for different sensors. For example an accelerometer can send X,Y and Z data, whereas
48 an ambient light sensor can send illumination data.
61 function will be called. So an accelerometer processing driver can register
64 The core driver provides a set of APIs which can be used by the processing
71 the report and get the indexes of the fields and also can get events. This driver
72 can use IIO interface to use the standard ABI defined for a type of sensor.
79 Each processing driver can use this structure to set some callbacks.
83 int (*send_event)(..): One complete event is received which can have
[all …]
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-powercap | 17 controlled. A <control type> can contain multiple power zones.
32 A power zone is a single or a collection of devices, which can
45 power zone for a whole CPU package, each CPU core in it can
61 If the counter can not be reset, then this attribute is
91 Each power zone can define one or more constraints. Each
92 constraint can have an optional name. Here "X" can have values
102 Here "X" can have values from 0 to max integer.
111 Here "X" can have values from 0 to max integer.
120 Here "X" can have values from 0 to max integer.
128 Here "X" can have values from 0 to max integer.
[all …]
|
| D | sysfs-class-mic.txt | 69 OS can shutdown because of various reasons. When read, this
89 boot the card OS. This entry can be written to change the
102 card can be found. The entry can be written to change the
112 OS boot can be found. The entry can be written to change
121 the card. This sysfs entry can be written with the following
132 debugging purpose and early kernel boot messages, the user can
135 OS log buffer can be read. This entry is written by the host
137 log buffer address to be written can be found in the System.map
146 debugging purpose and early kernel boot messages, the user can
149 length can be read. This entry is written by host configuration
[all …]
|
| D | sysfs-devices-mmc | 6 eMMC4.4 or later card can support such feature. This kind of
7 area can help to improve the card performance. If the feature
17 eMMC4.4 or later card can support such feature. This kind of
18 area can help to improve the card performance. If the feature
|
| D | sysfs-hypervisor-pmu | 9 "self" -- The guest can profile itself
10 "hv" -- The guest can profile itself and, if it is
12 "all" -- The guest can profile itself, the hypervisor
|
| D | sysfs-driver-samsung-laptop | 6 that are can be modified by a function key, and by this
11 file can change this value.
25 Description: Max battery charge level can be modified, battery cycle
26 life can be extended by reducing the max battery charge
|
| D | sysfs-bus-iio-adc-hi8435 | 23 Hysteresis between low and high thresholds can not be lower then 2 and
24 can not be odd.
40 Hysteresis between low and high thresholds can not be lower then 2 and
41 can not be odd.
|
| /linux-4.4.14/drivers/net/can/ |
| D | grcan.c | 253 struct can_priv can; /* must be the first member */ member
411 struct can_bittiming *bt = &priv->can.bittiming; in grcan_set_bittiming()
475 priv->can.state = CAN_STATE_STOPPED; in grcan_reset()
567 !(priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY)) { in grcan_lost_one_shot_frame()
595 if (priv->can.ctrlmode & CAN_CTRLMODE_ONE_SHOT) in grcan_err()
613 enum can_state state = priv->can.state; in grcan_err()
638 priv->can.can_stats.bus_off++; in grcan_err()
643 if (!priv->can.restart_ms) in grcan_err()
651 priv->can.can_stats.error_passive++; in grcan_err()
662 priv->can.can_stats.error_warning++; in grcan_err()
[all …]
|
| D | Kconfig | 9 This driver can also be built as a module. If so, the module
25 slcand) can be found in the can-utils at the SocketCAN SVN, see
29 can be changed by the 'maxdev=xx' module option. This driver can
96 This driver can also be built as a module. If so, the module will be
111 This driver can access CAN bus.
150 source "drivers/net/can/mscan/Kconfig"
152 source "drivers/net/can/sja1000/Kconfig"
154 source "drivers/net/can/c_can/Kconfig"
156 source "drivers/net/can/m_can/Kconfig"
158 source "drivers/net/can/cc770/Kconfig"
[all …]
|
| D | sun4i_can.c | 204 struct can_priv can; member
277 struct can_bittiming *bt = &priv->can.bittiming; in sun4ican_set_bittiming()
284 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) in sun4ican_set_bittiming()
337 if (priv->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING) in sun4i_can_start()
345 if (priv->can.ctrlmode & CAN_CTRLMODE_PRESUME_ACK) in sun4i_can_start()
347 else if (priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) in sun4i_can_start()
362 priv->can.state = CAN_STATE_ERROR_ACTIVE; in sun4i_can_start()
372 priv->can.state = CAN_STATE_STOPPED; in sun4i_can_stop()
453 if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) in sun4ican_start_xmit()
516 enum can_state state = priv->can.state; in sun4i_can_err()
[all …]
|
| D | xilinx_can.c | 133 struct can_priv can; member
253 struct can_bittiming *bt = &priv->can.bittiming; in xcan_set_bittiming()
320 if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) { in xcan_chip_start()
342 priv->can.state = CAN_STATE_ERROR_ACTIVE; in xcan_chip_start()
558 priv->can.state = CAN_STATE_BUS_OFF; in xcan_err_interrupt()
559 priv->can.can_stats.bus_off++; in xcan_err_interrupt()
566 priv->can.state = CAN_STATE_ERROR_PASSIVE; in xcan_err_interrupt()
567 priv->can.can_stats.error_passive++; in xcan_err_interrupt()
577 priv->can.state = CAN_STATE_ERROR_WARNING; in xcan_err_interrupt()
578 priv->can.can_stats.error_warning++; in xcan_err_interrupt()
[all …]
|
| D | bfin_can.c | 142 struct can_priv can; /* must be the first member */ member
175 struct can_bittiming *bt = &priv->can.bittiming; in bfin_can_set_bittiming()
186 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) in bfin_can_set_bittiming()
253 priv->can.state = CAN_STATE_STOPPED; in bfin_can_set_reset_mode()
304 if (priv->can.state != CAN_STATE_STOPPED) in bfin_can_start()
439 enum can_state state = priv->can.state; in bfin_can_err()
458 priv->can.can_stats.bus_off++; in bfin_can_err()
473 if (state != priv->can.state && (state == CAN_STATE_ERROR_WARNING || in bfin_can_err()
481 priv->can.can_stats.error_warning++; in bfin_can_err()
486 priv->can.can_stats.error_passive++; in bfin_can_err()
[all …]
|
| D | rcar_can.c | 86 struct can_priv can; /* Must be the first member! */ member
300 priv->can.can_stats.bus_error++; in rcar_can_error()
307 priv->can.state = CAN_STATE_ERROR_WARNING; in rcar_can_error()
308 priv->can.can_stats.error_warning++; in rcar_can_error()
317 priv->can.state = CAN_STATE_ERROR_PASSIVE; in rcar_can_error()
318 priv->can.can_stats.error_passive++; in rcar_can_error()
330 priv->can.state = CAN_STATE_BUS_OFF; in rcar_can_error()
333 priv->can.can_stats.bus_off++; in rcar_can_error()
425 struct can_bittiming *bt = &priv->can.bittiming; in rcar_can_set_bittiming()
487 (priv->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING ? in rcar_can_start()
[all …]
|
| D | at91_can.c | 130 struct can_priv can; /* must be the first member! */ member
359 const struct can_bittiming *bt = &priv->can.bittiming; in at91_set_bittiming()
362 reg_br = ((priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) ? 1 << 24 : 0) | in at91_set_bittiming()
402 if (priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) in at91_chip_start()
408 priv->can.state = CAN_STATE_ERROR_ACTIVE; in at91_chip_start()
427 priv->can.state = state; in at91_chip_stop()
732 priv->can.can_stats.bus_error++; in at91_poll_err_frame()
740 priv->can.can_stats.bus_error++; in at91_poll_err_frame()
756 priv->can.can_stats.bus_error++; in at91_poll_err_frame()
765 priv->can.can_stats.bus_error++; in at91_poll_err_frame()
[all …]
|
| D | pch_can.c | 172 struct can_priv can; member
235 if (priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) in pch_can_set_optmode()
238 if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) in pch_can_set_optmode()
497 enum can_state state = priv->can.state; in pch_can_error()
508 priv->can.can_stats.bus_off++; in pch_can_error()
516 priv->can.can_stats.error_warning++; in pch_can_error()
527 priv->can.can_stats.error_passive++; in pch_can_error()
542 priv->can.can_stats.bus_error++; in pch_can_error()
547 priv->can.can_stats.bus_error++; in pch_can_error()
552 priv->can.can_stats.bus_error++; in pch_can_error()
[all …]
|
| D | Makefile | 8 obj-$(CONFIG_CAN_DEV) += can-dev.o
9 can-dev-y := dev.o
11 can-dev-$(CONFIG_CAN_LEDS) += led.o
|
| D | ti_hecc.c | 212 struct can_priv can; /* MUST be first member/field */ member
290 struct can_bittiming *bit_timing = &priv->can.bittiming; in ti_hecc_set_btc()
296 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) { in ti_hecc_set_btc()
421 priv->can.state = CAN_STATE_ERROR_ACTIVE; in ti_hecc_start()
432 priv->can.state = CAN_STATE_STOPPED; in ti_hecc_stop()
679 priv->can.state = CAN_STATE_ERROR_WARNING; in ti_hecc_error()
680 ++priv->can.can_stats.error_warning; in ti_hecc_error()
694 priv->can.state = CAN_STATE_ERROR_PASSIVE; in ti_hecc_error()
695 ++priv->can.can_stats.error_passive; in ti_hecc_error()
712 priv->can.state = CAN_STATE_BUS_OFF; in ti_hecc_error()
[all …]
|
| D | flexcan.c | 251 struct can_priv can; member
337 return (priv->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING) && in flexcan_has_and_handle_berr()
382 unsigned int timeout = 1000 * 1000 * 10 / priv->can.bittiming.bitrate; in flexcan_chip_freeze()
558 priv->can.can_stats.bus_error++; in do_bus_err()
608 if (likely(new_state == priv->can.state)) in flexcan_poll_state()
775 const struct can_bittiming *bt = &priv->can.bittiming; in flexcan_set_bittiming()
795 if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) in flexcan_set_bittiming()
797 if (priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) in flexcan_set_bittiming()
799 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) in flexcan_set_bittiming()
874 priv->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING) in flexcan_chip_start()
[all …]
|
| /linux-4.4.14/tools/usb/usbip/ |
| D | INSTALL | 23 you can run in the future to recreate the current configuration, and a
27 It can also use an optional file (typically called `config.cache'
35 diffs or instructions to the address given in the `README' so they can
61 5. You can remove the program binaries and object files from the
63 files that `configure' created (so you can compile the package for
70 6. Often, you can also type `make uninstall' to remove the installed
80 You can give `configure' initial values for configuration parameters
91 You can compile the package for more than one kind of computer at the
93 own directory. To do this, you can use GNU `make'. `cd' to the
108 can specify an installation prefix other than `/usr/local' by giving
[all …]
|
| /linux-4.4.14/Documentation/isdn/ |
| D | syncPPP.FAQ | 7 Q04: MPPP?? What's that and how can I use it ...
9 Q06: can I use asynchronous PPP encapsulation with network devices
10 Q07: A SunISDN machine can't connect to my i4l system
14 Q11: I can't connect. How can I check where the problem is.
15 Q12: How can I reduce login delay?
50 (you can check this e.g with the program 'ifconfig')
70 Q04: MPPP?? What's that and how can I use it ...
82 the 'master' or initial call. Now you can add
103 Q06: can I use asynchronous PPP encapsulation
118 can't understand this ... try to use the ttyI*
[all …]
|
| D | README.icn | 3 You can get the ICN-ISDN-card from:
16 1. A range of 4 successive port-addresses, whose base address can be
18 2. A memory window with 16KB-256KB size, which can be setup in 16k steps
20 The base address of the window can be configured when loading
70 The ICN driver can be configured using the commandline-feature while
85 If you like to use more than one card, you can use the program
90 Using the "icnctrl"-utility, portbase and shared memory can also be
99 The module icn.o can be configured during "insmod'ing" it by
122 can be found in the subdirectory icnctrl/firmware/
|
| D | README.FAQ | 10 you can have a look at my website:
15 As the extension tells, the FAQ is in SGML format, and you can convert it
17 Alternatively, you can also do a 'configure; make all' in the FAQ directory.
|
| D | README.gigaset | 51 ISDN4Linux subsystem, so it can be used with any software which is able
67 can also be triggered manually using the modprobe(8) command, for example
74 can be used for that purpose, for example:
104 The device can be accessed from user space (eg. by the user space tools
114 You can also set a "default device" for the user space tools to use when
158 corresponding driver module is loaded, and can then be used with CAPI 2.0
179 after loading the module. It can then be used with ISDN4Linux
181 for setting up that subsystem. Otherwise you can use some HOWTOs like
202 You can use some configuration tool of your distribution to configure this
210 flag_time=0. You can do this e.g. by adding a line like
[all …]
|
| /linux-4.4.14/Documentation/input/ |
| D | walkera0701.txt | 15 At back side of transmitter S-video connector can be found. Modulation
16 pulses from processor to HF part can be found at pin 2 of this connector,
17 pin 3 is GND. Between pin 3 and CPU 5k6 resistor can be found. To get
41 cable and run jstest /dev/input/js0 to see values from TX. If no value can
85 One binary and octal value can be grouped to nibble. 24 nibbles + one binary
86 values can be sampled between sync pulses.
88 Values for first four channels (analog joystick values) can be found in
93 Next nibbles 12 .. 21 represents four channels (not all channels can be
99 binary value can be sampled. This bit and magic number is not used in
100 software driver. Some details about this magic numbers can be found in
|
| D | ff.txt | 43 All interactions are done using the event API. That is, you can use ioctl()
61 - FF_CONSTANT can render constant force effects
62 - FF_PERIODIC can render periodic effects with the following waveforms:
69 - FF_RAMP can render ramp effects
70 - FF_SPRING can simulate the presence of a spring
71 - FF_FRICTION can simulate friction
72 - FF_DAMPER can simulate damper effects
74 - FF_INERTIA can simulate inertia
88 Returns the number of effects the device can keep in its memory.
169 type. But you can enable it if you want.
[all …]
|
| D | gameport-programming.txt | 18 If your hardware supports more than one io address, and your driver can
36 ->close() callback. You also can select the io address in the ->open()
43 When a gameport can be accessed through MMIO, this way is preferred, because
66 There are gameports that can report the axis values as numbers, that means
93 gameports can set this to zero, most common have fuzz between 8 and 32.
101 Gameports can support both raw and cooked modes. In that case combine either
102 examples 1+2 or 1+3. Gameports can support internal calibration - see below,
170 in cooked mode, the open() callback can decide which modes are supported.
171 Second, resource allocation can happen here. The port can also be enabled
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | locking.txt | 15 the mmu-lock on x86. Currently, the page fault can be fast only if the
28 is safe because whenever changing these bits can be detected by cmpxchg.
32 The mapping from gfn to pfn may be changed since we can only ensure the pfn
61 For direct sp, we can easily avoid it since the spte of direct sp is fixed
64 - We have held the refcount of pfn that means the pfn can not be freed and
66 - The pfn is writable that means it can not be shared between different gfns
69 Then, we can ensure the dirty bitmaps is correctly set for a gfn.
75 In the origin code, the spte can be fast updated (non-atomically) if the
77 Accessed bit and Dirty bit can not be lost.
79 But it is not true after fast page fault since the spte can be marked
[all …]
|
| D | cpuid.txt | 5 A guest running on a kvm host, can check some of its features using
6 cpuid. This is not always guaranteed to work, since userspace can
43 KVM_FEATURE_ASYNC_PF || 4 || async pf can be enabled by
46 KVM_FEATURE_STEAL_TIME || 5 || steal time can be enabled by
50 || || handler can be enabled by writing
|
| D | hypercalls.txt | 5 instruction. The hypervisor can replace it with instructions that are
43 Purpose: Trigger guest exit so that the host can check for pending
60 mechanism (which is this hypercall) can be used.
68 The guest can map this shared page to access its supervisor register through
77 kernel mode for an event to occur (ex: a spinlock to become available) can
81 same guest can wakeup the sleeping vcpu by issuing KVM_HC_KICK_CPU hypercall,
|
| /linux-4.4.14/drivers/net/wireless/iwlegacy/ |
| D | Kconfig | 23 image for it. You can obtain the microcode from:
27 The microcode is typically installed in /lib/firmware. You can
32 If you want to compile the driver as a module ( = code which can be
49 image for it. You can obtain the microcode from:
53 The microcode is typically installed in /lib/firmware. You can
58 If you want to compile the driver as a module ( = code which can be
73 This will result in the kernel module being ~100k larger. You can
85 You can find the list of debug mask values in:
89 as the debug information can assist others in helping you resolve
|
| /linux-4.4.14/scripts/coccinelle/api/ |
| D | ptr_ret.cocci | 65 coccilib.org.print_todo(p[0], "WARNING: PTR_ERR_OR_ZERO can be used")
72 coccilib.org.print_todo(p[0], "WARNING: PTR_ERR_OR_ZERO can be used")
78 coccilib.org.print_todo(p[0], "WARNING: PTR_ERR_OR_ZERO can be used")
84 coccilib.report.print_report(p[0], "WARNING: PTR_ERR_OR_ZERO can be used")
90 coccilib.report.print_report(p[0], "WARNING: PTR_ERR_OR_ZERO can be used")
96 coccilib.report.print_report(p[0], "WARNING: PTR_ERR_OR_ZERO can be used")
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | Jack-Controls.txt | 5 to user space. This means userspace applications like pulseaudio can
14 can be read by any process.
16 This can be combined with UCM to allow userspace to route audio more
22 Each jack will have a kcontrol list, so that we can create a kcontrol
23 and attach it to the jack, at jack creation stage. We can also add a
38 HDA jacks can set phantom_jack to true in order to create a phantom
|
| /linux-4.4.14/security/tomoyo/ |
| D | Kconfig | 37 audit logs that the kernel can hold on memory.
38 You can read the log via /sys/kernel/security/tomoyo/audit.
48 operations which can lead to the hijacking of the boot sequence are
49 needed before loading the policy. For example, you can activate
53 loading the variant part of policy. Since you can start using
54 enforcing mode from the beginning, you can reduce the possibility of
64 activation. You can override this setting via TOMOYO_loader= kernel
74 You can override this setting via TOMOYO_trigger= kernel command line
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/reset/ |
| D | keystone-reset.txt | 6 The Keystone SoCs can contain up to 4 watchdog timers to reset
8 block. The Reset Mux block can be configured to cause reset or not.
10 Additionally soft or hard reset can be configured.
29 - ti,wdt-list: WDT list that can cause SoC reset. It's not related
32 in format: <0>, <2>; It can be in random order and
33 begins from 0 to 3, as keystone can contain up to 4 SoC
34 reset watchdogs and can be in random order.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 7.AdvancedTopics | 5 number of topics which can be helpful for developers wanting to become a
19 Managing patches with git can make life much easier for the developer,
42 heads, etc. It can all be a little intimidating at the outset, but the
45 Using git to generate patches for submission by email can be a good
49 will, of course, need a server that can be pulled from. Setting up such a
53 developers can get an account on kernel.org, but those are not easy to come
57 of development can be separated into a separate "topic branch" and
65 Git provides some powerful tools which can allow you to rewrite your
67 say, or which has some other sort of obvious bug) can be fixed in place or
68 made to disappear from the history entirely. A patch series can be
[all …]
|
| D | 4.Coding | 10 number of ways in which kernel developers can go wrong. Then the focus
11 will shift toward doing things right and the tools which can help in that
37 win before the code can be merged. Putting code into the kernel means
52 can never be transgressed. If there is a good reason to go against the
63 But experience has shown that excessive or premature abstraction can be
103 Conditionally-compiled code can be confined to functions which, if the code
118 Inline functions present a hazard of their own, though. Programmers can
121 however, can actually reduce performance. Since their code is replicated
123 That, in turn, creates pressure on the processor's memory caches, which can
174 One final hazard worth mentioning is this: it can be tempting to make a
[all …]
|
| D | 8.Conclusion | 9 mechanism; "make htmldocs" or "make pdfdocs" can be used to generate those
16 information on many specific kernel topics can be found via the LWN kernel
43 Documentation for git can be found at:
54 Linux kernel is developed and how you can participate in that process.
60 working to make it better. The kernel is a premier example of what can be
63 The kernel can always benefit from a larger developer base, though. There
65 participants in the Linux ecosystem can benefit through contributing to the
|
| /linux-4.4.14/Documentation/networking/ |
| D | regulatory.txt | 7 More up to date information can be obtained at the project's web page:
26 A currently available userspace agent which can accomplish this
32 it needs a new regulatory domain. A udev rule can be put in place
36 Below is an example udev rule which can be used:
48 Users can use iw:
71 set they can inform the wireless core using regulatory_hint().
73 crda can provide back a regulatory domain for that country or
74 they can build their own regulatory domain based on internal
75 custom knowledge so the wireless core can respect it.
79 check that can be used to ensure compliance based on custom EEPROM
[all …]
|
| D | can.txt | 3 can.txt
38 5.1 can.ko module params
98 controller can be passed up to the network layer and on to the CAN
101 that any number of transport protocols can be loaded or unloaded
102 dynamically. In fact, the can core module alone does not provide any
104 protocol module. Multiple sockets can be opened at the same time,
105 on different or the same protocol module and they can listen/send
110 selects that protocol when opening the socket, and then can read and
165 For this reason a CAN-ID can be treated best as a kind of source address.
177 CAN-IDs can be done for specific CAN interfaces or for all(!) known
[all …]
|
| D | batman-adv.txt | 11 cols won't be affected by any changes within the network. You can
17 network driver, and can be used on wifi as well as ethernet lan,
29 terfaces on which batman can operate. After loading the module
54 By reading the "iface_status" file you can check its status:
65 All mesh wide settings can be found in batman's own interface
82 ing the mesh network. For example, you can view the table of
88 requirements. For instance, you can check the current originator
114 The "bat0" interface can be used like any other regular inter-
115 face. It needs an IP address which can be either statically con-
133 this can be read in one of a number of ways. Try using the com-
[all …]
|
| D | 6lowpan.txt | 12 To access the LL_PRIV_6LOWPAN_DATA structure you can cast:
25 Example to evaluate the private usually you can do:
48 In case of generic 6lowpan branch ("net/6lowpan") you can remove the check
49 on ARPHRD_6LOWPAN, because you can be sure that these function are called
|
| D | decnet.txt | 28 that you need it, in general you won't and it can cause ifconfig to
44 You can set a DECnet address on the kernel command line for compatibility
51 can be used to loop back to the local machine. Of course this does not
73 using /proc/sys/net/decnet/conf/<dev>/forwarding. This file can be
76 There are also equivalent options for modules. The node address can
77 also be set through the /proc/sys/net/decnet/ files, as can other system
84 FTP sites called dn2ethaddr which can compute the correct ethernet
85 address to use. The address can be set by ifconfig either before or
86 at the time the device is brought up. If you are using RedHat you can
94 DECnet address which matches to be added to the interface (which you can
[all …]
|
| D | operstates.txt | 12 to be performed before user data can be transferred. Operational state
17 split into two parts: Two flags that can be set by the driver only, and
24 Both admin and operational state can be queried via the netlink
34 backward compatibility, routing daemons, dhcp clients can use this
64 Interface is operational up and can be used.
66 This TLV can also be queried via sysfs.
73 This TLV can also be queried via sysfs.
79 IFF_DORMANT. These flags can be set from everywhere, even from
95 netif_carrier_ok() can be used to query that bit.
114 otherwise. Kernel can recognise stacked interfaces because their
[all …]
|
| D | phonet.txt | 8 and RPC. With the Linux Phonet socket family, Linux host processes can
12 Phonet packets can be exchanged through various hardware connections
41 the 8-bit object identifiers. As such, Phonet can be considered as a
61 type (ETH_P_PHONET) which is out of the Ethernet type range. They can
64 The virtual TUN tunnel device driver can also be used for Phonet. This
92 Applications can send Phonet messages using the Phonet datagram socket
94 2^10 object IDs available, and can send and receive packets with any
118 A Phonet datagram socket can be subscribed to any number of 8-bits
127 Note that no more than one socket can be subcribed to any given
137 ID. Each listening socket can handle up to 255 simultaneous
[all …]
|
| D | packet_mmap.txt | 10 You can find the latest version of this document at:
13 Howto can be found at:
30 configurable circular buffer mapped in user space that can be used to either
33 transmission, multiple packets can be sent through one system call to get the
44 card can also be an advantage.
93 information can be captured or SOCK_DGRAM for the cooked
102 for capture and transmission. This can be done by mapping the
125 The flag MSG_DONTWAIT can be used to return
136 The protocol can optionally be 0 in case we only want to transmit
188 can set tp_net (with SOCK_DGRAM) or tp_mac (with SOCK_RAW). In order
[all …]
|
| D | netdev-features.txt | 74 set can be reduced further by networking core imposed limitations (as coded
79 stateless). It can be called multiple times between successive
89 should not be altered unless some error condition happens that can't
108 It means that device can fill TCP/UDP-like checksum anywhere in the packets
113 NETIF_F_TSO_ECN means that hardware can properly split packets with CWR bit
119 ndo_start_xmit can handle skbs with frags in high memory.
123 Those features say that ndo_start_xmit can handle fragmented skbs:
151 NETIF_F_VLAN_CHALLENGED should be set for devices which can't cope with VLAN
152 headers. Some drivers set this because the cards can't handle the bigger MTU.
165 frames (such as bad FCS, etc). This can be helpful when sniffing a link with
|
| /linux-4.4.14/Documentation/early-userspace/ |
| D | README | 30 You can create a cpio archive that contains the early userspace image.
38 The kernel build process can also build an early userspace image from
44 CONFIG_INITRAMFS_SOURCE. Sources can be either directories or files -
49 directory, limited user and group ID translation can be performed.
50 INITRAMFS_ROOT_UID can be set to a user ID that needs to be mapped to
51 user root (0). INITRAMFS_ROOT_GID can be set to a group ID that needs
61 can create a 'root-image' directory and install all files into it.
63 special files can be listed in a 'root-files' file. Both 'root-image'
64 and 'root-files' can be listed in CONFIG_INITRAMFS_SOURCE and a complete
65 early userspace image can be built by an unprivileged user.
[all …]
|
| /linux-4.4.14/drivers/net/can/usb/ |
| D | usb_8dev.c | 133 struct can_priv can; /* must be the first member */ member
254 struct can_bittiming *bt = &priv->can.bittiming; in usb_8dev_cmd_open()
257 u32 ctrlmode = priv->can.ctrlmode; in usb_8dev_cmd_open()
373 priv->can.state = CAN_STATE_ERROR_ACTIVE; in usb_8dev_rx_err_msg()
378 priv->can.state = CAN_STATE_BUS_OFF; in usb_8dev_rx_err_msg()
380 priv->can.can_stats.bus_off++; in usb_8dev_rx_err_msg()
389 priv->can.state = CAN_STATE_ERROR_WARNING; in usb_8dev_rx_err_msg()
391 priv->can.can_stats.bus_error++; in usb_8dev_rx_err_msg()
429 priv->can.state = CAN_STATE_ERROR_WARNING; in usb_8dev_rx_err_msg()
433 priv->can.can_stats.error_warning++; in usb_8dev_rx_err_msg()
[all …]
|
| D | gs_usb.c | 154 struct can_priv can; /* must be the first member */ member
254 struct can_device_stats *can_stats = &dev->can.can_stats; in gs_update_state()
257 dev->can.state = CAN_STATE_ERROR_ACTIVE; in gs_update_state()
260 dev->can.state = CAN_STATE_BUS_OFF; in gs_update_state()
265 dev->can.state = CAN_STATE_ERROR_WARNING; in gs_update_state()
269 dev->can.state = CAN_STATE_ERROR_PASSIVE; in gs_update_state()
272 dev->can.state = CAN_STATE_ERROR_ACTIVE; in gs_update_state()
397 struct can_bittiming *bt = &dev->can.bittiming; in gs_usb_set_bittiming()
639 ctrlmode = dev->can.ctrlmode; in gs_can_open()
676 dev->can.state = CAN_STATE_ERROR_ACTIVE; in gs_can_open()
[all …]
|
| D | esd_usb2.c | 213 struct can_priv can; /* must be the first member */ member
251 priv->can.state = CAN_STATE_BUS_OFF; in esd_usb2_rx_event()
253 priv->can.can_stats.bus_off++; in esd_usb2_rx_event()
257 priv->can.state = CAN_STATE_ERROR_WARNING; in esd_usb2_rx_event()
258 priv->can.can_stats.error_warning++; in esd_usb2_rx_event()
261 priv->can.state = CAN_STATE_ERROR_PASSIVE; in esd_usb2_rx_event()
262 priv->can.can_stats.error_passive++; in esd_usb2_rx_event()
265 priv->can.state = CAN_STATE_ERROR_ACTIVE; in esd_usb2_rx_event()
269 priv->can.can_stats.bus_error++; in esd_usb2_rx_event()
293 if (priv->can.state == CAN_STATE_ERROR_WARNING || in esd_usb2_rx_event()
[all …]
|
| D | ems_usb.c | 249 struct can_priv can; /* must be the first member */ member
354 dev->can.state = CAN_STATE_BUS_OFF; in ems_usb_rx_err()
357 dev->can.can_stats.bus_off++; in ems_usb_rx_err()
360 dev->can.state = CAN_STATE_ERROR_WARNING; in ems_usb_rx_err()
361 dev->can.can_stats.error_warning++; in ems_usb_rx_err()
363 dev->can.state = CAN_STATE_ERROR_ACTIVE; in ems_usb_rx_err()
364 dev->can.can_stats.error_passive++; in ems_usb_rx_err()
372 dev->can.can_stats.bus_error++; in ems_usb_rx_err()
396 if (dev->can.state == CAN_STATE_ERROR_WARNING || in ems_usb_rx_err()
397 dev->can.state == CAN_STATE_ERROR_PASSIVE) { in ems_usb_rx_err()
[all …]
|
| /linux-4.4.14/drivers/net/can/m_can/ |
| D | m_can.c | 280 struct can_priv can; /* must be the first member */ member
478 priv->can.can_stats.bus_error++; in m_can_handle_lec_err()
577 priv->can.can_stats.error_warning++; in m_can_handle_state_change()
578 priv->can.state = CAN_STATE_ERROR_WARNING; in m_can_handle_state_change()
582 priv->can.can_stats.error_passive++; in m_can_handle_state_change()
583 priv->can.state = CAN_STATE_ERROR_PASSIVE; in m_can_handle_state_change()
587 priv->can.state = CAN_STATE_BUS_OFF; in m_can_handle_state_change()
589 priv->can.can_stats.bus_off++; in m_can_handle_state_change()
645 (priv->can.state != CAN_STATE_ERROR_WARNING)) { in m_can_handle_state_errors()
652 (priv->can.state != CAN_STATE_ERROR_PASSIVE)) { in m_can_handle_state_errors()
[all …]
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | amc6821 | 20 The pwm can be controlled either from software or automatically.
45 fan1_div rw Fan divisor can be either 2 or 4.
64 pwm1 = pwm1_auto_point2_pwm. It can go from
69 speed. It can go from temp1_auto_point2_temp.
70 It can only have certain discrete values
81 pwm1 = pwm1_auto_point2_pwm. It can go from
86 speed. It can only have certain discrete
99 different settings, you can set the following parameters:
|
| D | emc2103 | 21 readings can be divided by a programmable divider (1, 2, 4 or 8) to give
22 the readings more range or accuracy. Not all RPM values can accurately be
29 The 2103-2 and 2103-4 variants have a third temperature sensor, which can
30 be connected to two anti-parallel diodes. These values can be read
32 will show as "fault". The module parameter "apd=0" can be used to suppress
|
| D | pc87427 | 20 monitoring capabilities. It can monitor up to 18 voltages, 8 fans and
35 signal. Speeds down to 83 RPM can be measured.
45 Fan speed can be controlled by PWM outputs. There are 4 possible modes:
47 by the driver: you can only return to that mode if it was the original
56 connected. The integer part can be 8-bit or 9-bit, and can be signed or
|
| D | lm85 | 57 outputs that can be used to control fan speed.
60 voltage can be measured without external resistors:
67 423 or socket 478 package. They can also measure temperature using a
75 This feature can also be disabled for manual control of the PWM's.
91 TACH signal from the fans. The ADM1027 can be configured to measure the
102 The ADM1027, ADT7463 and ADT7468 have a 10-bit ADC and can therefore
105 measurement. This offset can be used to zero out any errors due to traces
117 between 10 and 100 Hz, which can then be tuned separately.
126 of limit conditions and can automatically control the speeds of multiple
142 The LM85 can be jumpered for 3 different SMBus addresses. There are
[all …]
|
| D | adm1026 | 43 limit. If the limit is exceeded, an interrupt (#SMBALERT) can be
44 generated. The interrupts can be masked. In addition, there are over-temp
52 can be generated. Each fan can be programmed to divide the reference clock
53 by 1, 2, 4 or 8. Not all RPM values can accurately be represented, so some
60 measurements. Several inputs have integrated attenuators so they can measure
71 seconds since the last update). This means that you can easily miss
76 divisor. It can take as long as 1.5 seconds to measure all fan speeds.
79 temperature sensor inputs. Both the PWM output and the DAC output can be
|
| D | adt7410 | 32 -55°C to +150°C. It has a high accuracy of +/-0.5°C and can be operated at a
36 critical temperature set point has been exceeded. Both pins can be set up with a
38 Both pins can individually set to be active-low or active-high, while the whole
39 device can either run in comparator mode or interrupt mode. The ADT7410 supports
41 second or even just get one sample on demand for power saving. Besides, it can
56 maximum and critical temperature, it can only be set for temp#_max_hyst.
|
| D | lm95245 | 21 Management Bus (SMBus) interface and TruTherm technology that can monitor
23 The chips can be used to very accurately monitor the temperature of
35 can be set from user-space, and the same delta applies to the remote
38 The lm95245 driver can change its update interval to a fixed set of values.
|
| /linux-4.4.14/drivers/net/can/mscan/ |
| D | mscan.c | 101 priv->can.state = CAN_STATE_SLEEPING; in mscan_set_mode()
114 priv->can.state = CAN_STATE_STOPPED; in mscan_set_mode()
131 priv->can.state = CAN_STATE_ERROR_ACTIVE; in mscan_set_mode()
165 priv->can.state = state_map[max(MSCAN_STATE_RX(canrflg), in mscan_start()
182 priv->can.state = CAN_STATE_ERROR_ACTIVE; in mscan_restart()
189 if (priv->can.state <= CAN_STATE_BUS_OFF) in mscan_restart()
300 return priv->can.state; in get_new_state()
364 if (new_state != priv->can.state) { in mscan_get_err_frame()
369 if (priv->can.state == CAN_STATE_BUS_OFF) { in mscan_get_err_frame()
429 if (priv->can.state < CAN_STATE_BUS_OFF) in mscan_rx_poll()
[all …]
|
| /linux-4.4.14/Documentation/dvb/ |
| D | lmedm04.txt | 7 The Sharp 7395 driver can be found in windows/system32/drivers
18 An alternative but older firmware can be found on the driver
31 The LG firmware can be found on the driver
46 Other LG firmware can be extracted manually from US280D.sys
58 The Sharp 0194 tuner driver can be found in windows/system32/drivers
71 The m88rs2000 tuner driver can be found in windows/system32/drivers
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | max77686.txt | 4 More information can be found in ../mfd/max77686.txt file.
7 regulators that can be controlled over I2C.
24 -LDOn : for LDOs, where n can lie in range 1 to 26.
26 -BUCKn : for BUCKs, where n can lie in range 1 to 9.
29 Regulators which can be turned off during system suspend:
34 LDO20, LDO21, LDO22, BUCK8 and BUCK9 can be configured to GPIO enable
|
| D | max77802.txt | 4 More information can be found in bindings/mfd/max77802.txt file.
7 regulators that can be controlled over I2C.
44 -LDOn : for LDOs, where n can lie in ranges 1-15, 17-21, 23-30
47 -BUCKn : for BUCKs, where n can lie in range 1 to 10.
53 mode during system suspend. The standard regulator suspend states binding can
64 header and can be included by device tree source files.
66 The standard "regulator-mode" property can only be used for regulators that
|
| /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
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/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
58 This is useful for SoCs whose I2C module's signals can be routed to
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/Documentation/block/ |
| D | pr.txt | 27 Only the initiator that owns the reservation can write to the
28 device. Any initiator can read from the device.
32 Only the initiator that owns the reservation can access the
37 Only initiators with a registered key can write to the device,
38 Any initiator can read from the device.
42 Only initiators with a registered key can access the device.
46 Only initiators with a registered key can write to the device,
47 Any initiator can read from the device.
55 Only initiators with a registered key can access the device.
|
| D | cmdline-partition.txt | 6 It has no MBR, so saves storage space. Bootloader can be easily accessed
8 Users can easily change the partition.
27 partition name, kernel send uevent with "PARTNAME". application can create
29 user space application can access partition by partition name.
|
| D | switching-sched.txt | 6 tunables control how the io scheduler works. You can find these entries
12 you can do so by typing:
20 can improve that device's throughput).
29 The list of defined schedulers can be found by simply doing
|
| /linux-4.4.14/Documentation/fault-injection/ |
| D | provoke-crashes.txt | 4 crashing points, but can also crash the kernel directly without KRPOBE
8 You can provide the way either through module arguments when inserting
16 cpoint_name : Crash point where the kernel is to be crashed. It can be
22 It can be one of PANIC, BUG, EXCEPTION, LOOP, OVERFLOW,
29 You can also induce failures by mounting debugfs and writing the type to
|
| /linux-4.4.14/Documentation/arm/sunxi/ |
| D | clocks.txt | 12 steps, one can gate it and keep the system running. Consider this
36 Finally you can gate the main oscillator
46 Q: Were can I learn more about the sunxi clocks?
49 you can find it at
54 released by Allwinner, you can find it at
|
| /linux-4.4.14/drivers/net/ieee802154/ |
| D | Kconfig | 17 Say Y here to enable the fake driver that can emulate a net
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/Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets | 4 This document describes how the numa=fake x86_64 command-line option can be used
6 you can create fake NUMA nodes that represent contiguous chunks of memory and
12 There are a number of different configurations you can use for your needs. For
18 four equal chunks of 512M each that we can now use to assign to cpusets. As
36 Documentation/cgroups/cpusets.txt, you can assign fake nodes (i.e. contiguous memory
49 You can now assign tasks to these cpusets to limit the memory resources
65 cpusets. Since cpusets can form a hierarchy, you can create some pretty
|
| D | uefi.txt | 13 support. Elilo with x86_64 support can be used.
31 can be found in the elilo sourceforge project.
34 - If some or all EFI runtime services don't work, you can try following
40 you can include those entries in the kernels memory map of available
|
| /linux-4.4.14/Documentation/vm/ |
| D | zswap.txt | 6 for potentially reduced swap I/O. This trade-off can also result in a
16 * Desktop/laptop users with limited RAM capacities can mitigate the
18 * Overcommitted guests that share a common I/O resource can
22 * Users with SSDs as swap devices can extend the life of the device by
29 Zswap is disabled by default but can be enabled at boot time by setting
31 can also be enabled and disabled at runtime using the sysfs interface.
57 zbud is created, but it can be selected at boot time by setting the "zpool"
58 attribute, e.g. zswap.zpool=zbud. It can also be changed at runtime using the
66 storage method, and it can achieve greater storage densities. However,
68 cannot evict the oldest page, it can only reject new pages.
[all …]
|
| D | transhuge.txt | 13 future it can expand over the pagecache layer starting with tmpfs.
31 TLB can be mapped of larger size only if both KVM and the Linux guest
73 Applications however can be further optimized to take advantage of
76 is by far not mandatory and khugepaged already can take care of long
97 Transparent Hugepage Support can be entirely disabled (mostly for
100 wide. This can be achieved with one of:
139 You can also control how many pages khugepaged should scan at each
145 can set this to 0 to run khugepaged at 100% utilization of one core):
154 The khugepaged progress can be seen in the number of pages collapsed:
163 not already mapped) can be allocated when collapsing a group
[all …]
|
| /linux-4.4.14/drivers/auxdisplay/ |
| D | Kconfig | 47 You can specify a different address if you need.
50 and execute "dmesg" or "cat /proc/ioports". You can see there how
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
92 The LCD framebuffer driver can be attached to a console.
93 It will work fine. However, you can't attach it to the fbdev driver
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/Documentation/frv/ |
| D | clock.txt | 14 can be rewritten, to set or clear the CLKC_P0 bit respectively, hence
17 The 'cm' file should also be available on all boards. '0' can be written to it
18 to shift the board into High-Speed mode (normal), and '1' can be written to
30 The current state and the available masks can be found in /proc/cpuinfo. For
56 The PM-Controls line, if present, will indicate which /proc/sys/pm files can
58 "suspend=0x9" indicates that 0 and 3 can be written validly to
64 the file can be read, then the suspend value must be 0, and so that's not
|
| D | booting.txt | 9 First of all, a root filesystem must be made available. This can be done in
15 the target board can reach. This directory should then be NFS exported
16 such that the target board can read and write into it as root.
21 can be used. A complete image can be built using the mkfs.jffs2 or
30 boot loader) before it can be run. The kernel image (arch/frv/boot/Image) may
35 This is the simplest. RedBoot can store an image in the flash (see the
89 serial port <x> (which can be "0" or "1").
121 Authoritative information can be found in
152 The NFS version to use can also be specified. v2 and v3 are supported by
165 This can be used as an alternative to the "console=ttyS..." listed
[all …]
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | machine.txt | 9 The machine driver can contain codec and platform specific code. It registers
52 The machine DAI configuration glues all the codec and CPU DAIs together. It can
54 initialisation e.g. the machine audio map can be connected to the codec audio
55 map, unconnected codec pins can be set as such.
84 The machine driver can optionally extend the codec power map and to become an
86 of speaker/HP amplifiers, etc. Codec pins can be connected to the machines jack
93 Machine specific audio mixer controls can be added in the DAI init function.
|
| D | pops_clicks.txt | 9 Pops and clicks can be more frequent on portable systems with DAPM. This is
11 depending on the audio usage and this can subsequently cause a small pop or
20 suppression. Pops can be reduced within playback by powering the audio
35 Capture artifacts are somewhat easier to get rid as we can delay activating the
47 An unwanted zipper noise can occur within the audio playback or capture stream
50 amplitude too quickly. It can be minimised by enabling the zero cross setting
|
| D | dapm.txt | 10 such, can easily co-exist with the other PM systems.
26 can be set at stream time if power is not needed for sidetone, etc.
79 Widgets can be added to the sound card by any of the component driver types.
80 There are convenience macros defined in soc-dapm.h that can be used to quickly
121 Any widget kcontrols can be set using the controls and num_controls members.
136 you can use SND_SOC_DAPM_MIXER_NAMED_CTL instead. the parameters are the same
145 machine audio component (non codec or DSP) that can be independently
152 A machine widget can have an optional call back.
183 This can be used to merge to signal paths together in software.
185 After all the widgets have been defined, they can then be added to the DAPM
[all …]
|
| /linux-4.4.14/drivers/net/can/cc770/ |
| D | cc770_platform.c | 92 priv->can.clock.freq = clkext; in cc770_get_of_node_data()
95 if (priv->can.clock.freq > 10000000) { in cc770_get_of_node_data()
97 priv->can.clock.freq /= 2; in cc770_get_of_node_data()
101 if (priv->can.clock.freq > 8000000) in cc770_get_of_node_data()
157 priv->can.clock.freq = pdata->osc_freq; in cc770_get_platform_data()
159 priv->can.clock.freq /= 2; in cc770_get_platform_data()
216 priv->reg_base, dev->irq, priv->can.clock.freq, in cc770_platform_probe()
|
| D | cc770.c | 213 priv->can.state = CAN_STATE_STOPPED; in set_reset_mode()
244 priv->can.state = CAN_STATE_ERROR_ACTIVE; in set_normal_mode()
340 if (priv->can.state != CAN_STATE_STOPPED) in cc770_start()
365 struct can_bittiming *bt = &priv->can.bittiming; in cc770_set_bittiming()
371 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) in cc770_set_bittiming()
537 priv->can.state = CAN_STATE_BUS_OFF; in cc770_err()
538 priv->can.can_stats.bus_off++; in cc770_err()
546 priv->can.state = CAN_STATE_ERROR_PASSIVE; in cc770_err()
547 priv->can.can_stats.error_passive++; in cc770_err()
551 priv->can.state = CAN_STATE_ERROR_WARNING; in cc770_err()
[all …]
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | at91sam9x5_can.dtsi | 30 can0: can@f8000000 {
31 compatible = "atmel,at91sam9x5-can";
41 can1: can@f8004000 {
42 compatible = "atmel,at91sam9x5-can";
|
| D | sama5d3_can.dtsi | 51 can0: can@f000c000 {
52 compatible = "atmel,at91sam9x5-can";
62 can1: can@f8010000 {
63 compatible = "atmel,at91sam9x5-can";
|
| D | sama5d2.dtsi | 7 * This file is dual-licensed: you can use it either under the terms
12 * a) This file is free software; you can redistribute it and/or
131 atmel,can-dma;
132 atmel,can-isoc;
139 atmel,can-dma;
140 atmel,can-isoc;
147 atmel,can-dma;
148 atmel,can-isoc;
155 atmel,can-dma;
156 atmel,can-isoc;
[all …]
|
| D | s3c6400.dtsi | 7 * based board files can include this file and provide values for board specfic
12 * nodes can be added to this file.
14 * This program is free software; you can redistribute it and/or modify
|
| /linux-4.4.14/Documentation/i2c/ |
| D | writing-clients | 5 some things can be done slightly or completely different. Use this as a
55 should match the module name (if the driver can be compiled as a module),
56 although you can use MODULE_ALIAS (passing "foo" in this example) to add
67 Each client structure has a special `data' field that can point to any
91 but many chips have some kind of register-value idea that can easily
124 can be sufficiently configured using only such probe primitives.
130 that can't be distinguished by protocol probing, or which need some board
166 you can instantiate that device by simply filling an i2c_board_info
170 If a driver supports different device types, you can specify the type you
171 want using the type field. You can also specify an IRQ and platform data
[all …]
|
| /linux-4.4.14/Documentation/trace/ |
| D | tracepoint-analysis.txt | 9 Tracepoints (see Documentation/trace/tracepoints.txt) can be used without
13 Simplistically, tracepoints represent important events that can be
17 this document describes some of the methods that can be used.
59 can be enabled system-wide. A short example of enabling all events related
93 for a duration of time can be examined.
119 Events can be activated and tracked for the duration of a process on a local
144 Any workload can exhibit variances between runs and it can be important
147 occurrences are useful to the performance analyst, then perf can be used.
186 When events are enabled the events that are triggering can be read from
188 options exist as well. By post-processing the output, further information can
[all …]
|
| D | kprobetrace.txt | 10 this is based on kprobes (kprobe and kretprobe). So it can probe wherever
11 kprobes can probe (this means, all functions body except for __kprobes
12 functions). Unlike the Tracepoint based event, this can be added and removed
36 FETCHARGS : Arguments. Each probe can have up to 128 args.
71 under tracing/events/kprobes/<EVENT>, at the directory you can see 'id',
75 You can enable/disable the probe by writing 1 or 0 on it.
81 You can write filtering rules of this event.
89 You can check the total number of probe hits and probe miss-hits via
105 the ABI, please try to use probe subcommand of perf-tools (you can find it
107 As this example shows, users can choose more familiar names for each arguments.
[all …]
|
| D | events.txt | 9 Tracepoints (see Documentation/trace/tracepoints.txt) can be used
13 Not all tracepoints can be traced using the event tracing system;
24 The events which are available for tracing can be found in the file
51 file. All of the events in a subsystem can be specified via the syntax
52 "<subsystem>:*"; for example, to enable all irq events, you can use the
105 a description of each field in a logged event. This information can
107 find the field names that can be used in event filters (see section 5).
155 Trace events can be filtered in the kernel by associating boolean
167 A filter expression consists of one or more 'predicates' that can be
175 Parentheses can be used to provide arbitrary logical groupings and
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-stp-xway.txt | 5 3 groups of 8 bits can be driven. The hardware is able to allow the DSL modem
22 - lantiq,dsl : The dsl core can control the 2 LSBs of the gpio cascade. This 2 bit
23 property can enable this feature.
24 - lantiq,phy1 : The gphy1 core can control 3 bits of the gpio cascade.
25 - lantiq,phy2 : The gphy2 core can control 3 bits of the gpio cascade.
|
| /linux-4.4.14/Documentation/timers/ |
| D | hpet.txt | 4 by Intel and Microsoft which can be found at
10 each of which can generate oneshot interrupts and at least one of which has
12 also called "timers", which can be misleading since usually timers are
15 HPET devices can support two interrupt routing modes. In one mode, the
25 initialization. An example of this initialization can be found in
|
| /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/Documentation/gpio/ |
| D | consumer.txt | 12 Drivers that can't work without standard GPIO calls should have Kconfig entries
36 device that displays digits), an additional index argument can be specified:
46 for the GPIO. Values can be:
61 gpiod_get_index_optional() functions can be used. These functions return NULL
73 For a function using multiple GPIOs all of those can be obtained with one call:
121 A GPIO descriptor can be disposed of using the gpiod_put() function:
125 For an array of GPIOs this function can be used:
161 A driver can also query the current direction of a GPIO:
174 Most GPIO controllers can be accessed with memory read/write instructions. Those
175 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ
[all …]
|
| D | board.txt | 4 This document explains how GPIOs can be assigned to given devices and functions.
12 is mandatory) or ARCH_WANT_OPTIONAL_GPIOLIB (if GPIO support can be omitted) in
14 describe its hardware layout. Currently, mappings can be defined through device
19 GPIOs can easily be mapped to devices and functions in the device tree. The
67 The above DT example can be converted to an equivalent ACPI description
106 Finally, GPIOs can be bound to devices and functions using platform data. Board
122 can be NULL, in which case it will be matched for calls to gpiod_get()
125 can be NULL, in which case it will match any function.
136 A lookup table can then be defined as follows, with an empty entry defining its
150 And the table can be added by the board code as follows:
|
| D | gpio-legacy.txt | 16 which GPIOs. Drivers can be written generically, so that board setup code
20 non-dedicated pin can be configured as a GPIO; and most chips have at least
21 several dozen of them. Programmable logic devices (like FPGAs) can easily
40 - Inputs can often be used as IRQ signals, often edge triggered but
47 - Most GPIOs can be accessed while holding spinlocks, but those accessed
48 through a serial bus normally can't. Some systems support both types.
61 glue logic that may even change between board revisions, and can't ever be
63 functionality can be very portable. Other features are platform-specific,
64 and that can be critical for glue logic.
76 ARCH_WANT_OPTIONAL_GPIOLIB in their Kconfig. Drivers that can't work without
[all …]
|
| D | gpio.txt | 29 which GPIOs. Drivers can be written generically, so that board setup code
33 non-dedicated pin can be configured as a GPIO; and most chips have at least
34 several dozen of them. Programmable logic devices (like FPGAs) can easily
53 - Inputs can often be used as IRQ signals, often edge triggered but
60 - Most GPIOs can be accessed while holding spinlocks, but those accessed
61 through a serial bus normally can't. Some systems support both types.
101 support it, there's a common idiom you can use to emulate it with any GPIO pin
102 that can be used as either an input or an output:
110 The same logic can be applied to emulate open source signaling, by driving the
112 source emulation can be handled transparently by the GPIO framework.
|
| /linux-4.4.14/Documentation/ |
| D | media-framework.txt | 24 An entity is a basic media hardware building block. It can correspond to
30 A pad is a connection endpoint through which an entity can interact with
102 although drivers can allocate entities directly.
109 The media_entity name, type, flags, revision and group_id fields can be
111 higher-level standard structures can have some of those fields set by the
132 Entities are identified by a unique positive integer ID. Drivers can provide an
159 This can be used to report the default audio and video devices or the
162 Logical entity groups can be defined by setting the group ID of all member
212 MEDIA_LNK_FL_ENABLED indicates that the link is enabled and can be used
214 one of them can be enabled at a time.
[all …]
|
| D | md.txt | 1 Tools that manage md devices can be found at
8 You can boot with your md device with the following kernel command
49 superblock can be autodetected and run at boot time.
82 The md driver can support a variety of different superblock formats.
99 particular md virtual device. Once it is completely assembled, it can
105 can create appropriate redundancy (copying in raid1, parity
121 Once started, new devices can be added. They should have an
125 Devices that have failed or are not yet active can be detached from an
133 An array can be 'created' by describing the array (level, chunksize
137 Then uninitialized devices can be added with ADD_NEW_DISK. The
[all …]
|
| D | coccinelle.txt | 26 You can get the latest version released from the Coccinelle homepage at
106 The optional make variable COCCI can be used to check a single
121 To apply Coccinelle to a specific directory, M= can be used.
142 The "report" mode is the default. You can select another one with the
148 Additional flags can be passed to spatch through the SPFLAGS
165 New semantic patches can be proposed and submitted by kernel
197 msg="ERR_CAST can be used with %s" % (x)
204 /home/user/linux/crypto/ctr.c:188:9-16: ERR_CAST can be used with alg
205 /home/user/linux/crypto/authenc.c:619:9-16: ERR_CAST can be used with auth
206 /home/user/linux/crypto/xts.c:227:9-16: ERR_CAST can be used with alg
[all …]
|
| D | initrd.txt | 9 This RAM disk can then be mounted as the root file system and programs
10 can be run from it. Afterwards, a new root file system can be mounted
12 to a directory and can be subsequently unmounted.
19 discussion of the boot process can be found in [1].
35 5) /sbin/init is executed (this can be any valid executable, including
36 shell scripts; it is run with uid 0 and can do basically everything
37 init can do).
65 the "normal" root file system is mounted. initrd data can be read
66 from /dev/initrd. Note that the data in initrd can have any structure
70 Note: /dev/initrd is read-only and it can only be used once. As soon
[all …]
|
| D | vme_api.txt | 62 driver. The bridge number (or bus number) can be accessed using
82 The driver can request ownership of one or more master windows, slave windows
100 such any combination of the attributes can be requested for a single window,
105 This is typically VME-to-MEM and/or MEM-to-VME, though some hardware can
107 If an unallocated window fitting the requirements can not be found a NULL
126 the underlying chipset. A window must be configured before it can be used.
132 Once a master window has been assigned the following functions can be used to
153 The following functions can be used to read from and write to configured master
174 Parts of a VME window can be mapped into user space memory using the following
185 local memory. The number of windows available and the access modes that can be
[all …]
|
| D | bus-virt-phys-mapping.txt | 32 things any more complex than necessary, so you can assume that all
55 PPC, you can end up with a setup like this:
85 pointer from the kernel. So you can have something like this:
115 And you generally _never_ want to use the physical address, because you can't
117 you can't use it from the bus master.
132 of a video graphics card it can be normal DRAM that is just used for a frame
133 buffer), but can be things like a packet buffer in a network card etc.
138 there is really nothing you can do with such an address: it's not
144 For such memory, you can do things like
156 * size 1MB, so that we can access it: We can directly
[all …]
|
| D | braille-console.txt | 4 readers can start), you first need to compile the support for the usual serial
15 So for instance you can use console=brl,ttyS0 if the braille device is connected
25 Sound feedback can be obtained by adding the braille_console.sound=1 kernel
28 For simplicity, only one braille console can be enabled, other uses of
|
| D | crc32.txt | 5 CRC polynomial. To check the CRC, you can either check that the
6 CRC matches the recomputed value, *or* you can check that the
38 When computing a CRC, we don't care about the quotient, so we can
61 can be precomputed, and merging in the final 32 zero bits to make room
62 for the CRC can be skipped entirely. This changes the code to:
84 We can do it 8 bits at a time rather than 1 bit at a time:
102 If the input is a multiple of 32 bits, you can even XOR in a 32-bit
105 You can also mix and match the two loop styles, for example doing the
115 in the correct multiple to subtract, we can shift a byte at a time.
122 When space is more constrained, smaller tables can be used, e.g. two
[all …]
|
| D | ManagementStyle | 56 small one is whether you can fix your decision afterwards. Any decision
57 can be made small by just always making sure that if you were wrong (and
58 you _will_ be wrong), you can always undo the damage later by
66 things that can't be undone. Don't get ushered into a corner from which
74 thing you can backtrack on is a technical decision, and there
87 wasn't worthwhile after all can be hard on the poor lowly engineers
94 Happily, both of these reasons can be mitigated effectively by just
114 thing you can do as a manager is not to instill confidence, but rather a
117 Btw, another way to avoid a decision is to plaintively just whine "can't
151 The problem with #1 is that it's very easy to do, since you can say
[all …]
|
| D | memory-hotplug.txt | 71 this phase is triggered automatically. ACPI can notify this event. If not,
86 phases can be execute in seamless way.)
123 This option can be kernel module.
129 This option can be kernel module too.
152 Under each memory block, you can see 5 files:
163 at write: user can specify "online_kernel",
175 can be onlined to.
178 can be onlined to ZONE_NORMAL by default and to ZONE_MOVABLE
181 can be onlined to ZONE_MOVABLE by default and to ZONE_NORMAL
187 If CONFIG_NUMA is enabled the memoryXXX/ directories can also be accessed
[all …]
|
| D | binfmt_misc.txt | 11 bits) you have supplied. Binfmt_misc can also recognise a filename extension
18 :name:type:offset:magic:mask:interpreter:flags (where you can choose the ':'
36 - 'mask' is an (optional, defaults to all 0xff) mask. You can mask out some
53 interp has to be aware of this so it can execute /usr/local/bin/blah
77 To use binfmt_misc you have to mount it first. You can mount it with
78 "mount -t binfmt_misc none /proc/sys/fs/binfmt_misc" command, or you can add
104 You can enable/disable binfmt_misc or one binary type by echoing 0 (to disable)
108 You can remove one entry or all entries by echoing -1 to /proc/.../the_name
115 If you want to pass special arguments to your interpreter, you can
120 passes it the full filename (or the file descriptor) to use. Using $PATH can
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | maxim,max77686.txt | 4 More information can be found in bindings/mfd/max77686.txt file.
6 The MAX77686 contains three 32.768khz clock outputs that can be controlled
18 Each clock is assigned an identifier and client nodes can use this identifier
25 header and can be used in device tree sources.
|
| D | maxim,max77802.txt | 4 More information can be found in bindings/mfd/max77802.txt file.
6 The MAX77802 contains two 32.768khz clock outputs that can be controlled
17 Each clock is assigned an identifier and client nodes can use this identifier
23 header and can be used in device tree sources.
|
| /linux-4.4.14/Documentation/usb/ |
| D | bulk-streams.txt | 5 device driver to overload a bulk endpoint so that multiple transfers can be
10 Protocol, which uses streams to queue multiple SCSI commands, can be found on
20 can also initiate a transfer on a stream without the device asking, but the
21 device can refuse that transfer. Devices can switch between streams at any
33 allocate memory so the driver can use up to num_streams stream IDs. They must
41 declares how many stream IDs it can support, and each bulk endpoint on a
42 SuperSpeed device will say how many stream IDs it can handle. Therefore,
|
| D | gadget_configfs.txt | 16 A USB Linux Gadget is a device which has a UDC (USB Device Controller) and can
51 made available through configfs can be seen here:
87 Then the strings can be specified:
101 where <name> can be any string which is legal in a filesystem and the
115 Then the configuration string can be specified:
119 Some attributes can also be set for a configuration, e.g.:
151 function can be used in multiple configurations). This is achieved with
203 Such a gadget must be finally enabled so that the USB host can enumerate it.
296 The difference between an item and a group is that a group can contain
298 Both items and groups can have attributes, which are represented as files.
[all …]
|
| D | ohci.txt | 18 - interrupt transfers can be larger, and can be queued
24 types can be queued. That was also true in "usb-ohci", except for interrupt
27 risks can be minimized by making sure the hardware always has transfers to
|
| D | authorization.txt | 6 This feature allows you to control if a USB device can be used (or
44 can be connected (for example, it is a kiosk machine with a visible
65 security verification you can make (or the best, for someone willing
73 # FIXME: make sure none can mount it
80 # Other stuff so others can use it
90 can fake descriptors and device info. Don't trust that. You are
106 on a particular USB bus can be changed, too.
|
| D | dma.txt | 8 The big picture is that USB drivers can continue to ignore most DMA issues,
13 OR: they can now be DMA-aware.
33 It's good to avoid making CPUs copy data needlessly. The costs can add up,
34 and effects like cache-trashing can impose subtle penalties.
37 the time, that can really burn up resources on systems which use an
38 IOMMU to manage the DMA mappings. It can cost MUCH more to set up and
81 high memory to "normal" DMA memory. If you can come up with a good way
90 driver can safely be used with such DMA mapping. (See the first section
93 - When you're using scatterlists, you can map everything at once. On some
132 calls (where the underlying DMA primitives have changed), most of them can
|
| D | proc_usb_info.txt | 27 You can then issue `cat /proc/bus/usb/devices` to extract
28 USB device information, and user mode drivers can use usbfs
41 of the USB Guide can be found at http://www.linux-usb.org/
48 of these numbers are assigned sequentially, and can be reused, so
49 you can't rely on them for stable access to devices. For example,
55 These files can be read as binary data. The binary data consists
76 root, only root can write such user mode drivers. You can selectively
87 can obtain some useful data from it without the use of an
90 Lev, Prnt, Port, Cnt) can be used to build a USB topology diagram.
201 | can't be shared with any other device.
[all …]
|
| /linux-4.4.14/Documentation/acpi/ |
| D | method-customizing.txt | 9 Users can use this to
16 rebuild/reboot is not needed and test result can be got in minutes.
18 Note: Only ACPI METHOD can be overridden, any other object types like
20 Note: The same ACPI control method can be overridden for many times,
59 right now, i.e. we can not remove a method currently.
65 Note: We can use a kernel with multiple custom ACPI method running,
66 But each individual write to debugfs can implement a SINGLE
70 Note: Be aware that root can mis-use this driver to modify arbitrary
|
| D | debug.txt | 4 The ACPI CA, the Linux ACPI core, and some ACPI drivers can generate debug
17 When CONFIG_ACPI_DEBUG=y, you can select the component and level of messages
19 acpi.debug_level kernel command line options. After boot, you can use the
30 You can set the debug_layer mask at boot-time using the acpi.debug_layer
31 command line argument, and you can change it after boot by writing values
78 You can set the debug_level mask at boot-time using the acpi.debug_level
79 command line argument, and you can change it after boot by writing values
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | user-guide.txt | 123 On these systems, all you can do is select the lower and upper
151 frequency the processor can run at(in kHz)
153 frequency the processor can run at(in kHz)
160 Using this information can be useful
170 available in this kernel. You can see the
174 governor you can change it. Please note
188 files, you can change these limits.
205 lower frequencies, the user can read out the
207 This typically can happen through (often not
212 which can be detected through the generic
[all …]
|
| /linux-4.4.14/Documentation/leds/ |
| D | leds-class.txt | 12 is a kernel based source of led events. Triggers can either be simple or
21 LED_OFF and the current brightness setting. The "on" and "off" time can
23 You can change the brightness value of a LED independently of the timer
27 You can change triggers in a similar manner to the way an IO scheduler
29 parameters can appear in /sys/class/leds/<device> once a given trigger is
58 Some LEDs can be programmed to blink without any CPU interaction. To
59 support this feature, a LED driver can optionally implement the
84 rest of the LED subsystem can be modular.
90 At the moment, a trigger can't be created specifically for a single LED.
|
| D | leds-lp5521.txt | 13 LP5521 can drive up to 3 channels. Leds can be controlled directly via
17 All three channels can be also controlled using the engine micro programs.
18 More details of the instructions can be found from the public data sheet.
52 Note: chan_nr can have values between 0 and 2.
53 The name of each channel can be configurable.
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | kconfig-language.txt | 37 Every line starts with a key word and can be followed by multiple
39 define attributes for this config option. Attributes can be the type of
41 values. A config option can be defined multiple times with the same
42 name, but every definition can have only a single input prompt and the
48 A menu entry can have a number of attributes. Not all of them are
63 Every menu entry can have at most one prompt, which is used to display
64 to the user. Optionally dependencies only for this prompt can be added
68 A config option can have any number of default values. If multiple
71 defined. This means the default can be defined somewhere else or be
75 prompt is visible the default value is presented to the user and can
[all …]
|
| D | kbuild.txt | 67 The directory can be specified in several ways:
77 The output directory can also be specified using "O=...".
100 CROSS_COMPILE can be a part of the filename or the full path.
114 images. Default is /boot, but you can set it to other values.
140 The value can be overridden in which case the default value is ignored.
146 makefile but the argument can be passed to make if needed.
162 The value can be overridden in which case the default value is ignored.
175 The value can be overridden in which case the default value is ignored.
184 KBUILD_MODPOST_WARN can be set to avoid errors in case of undefined
190 KBUILD_MODPOST_NOFINAL can be set to skip the final link of modules.
[all …]
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | cxl.txt | 16 Coherent in this context means that the accelerator and CPUs can
70 this mode, only one userspace process can use the accelerator at
73 When using AFU directed mode, up to 16K simultaneous contexts can
78 associated with each operation. If the PSL can't translate an
79 operation, the ID can also be accessed by the kernel so it can
86 A portion of the accelerator MMIO space can be directly mapped
87 from the AFU to userspace. Either the whole space can be mapped or
89 the kernel can determine the offset and size of the per context
111 and userspace can share control and status information.
149 An AFU directed mode AFU can have many contexts, the device can be
[all …]
|
| D | pmu-ebb.txt | 11 One type of event for which EBBs can be configured is PMU exceptions. This
21 attr.config. All events which can be configured on the hardware PMU are
29 EBBs can only sensibly be used by programs for self-monitoring.
31 It is a feature of the perf_events API that events can be created on other
37 actually configure any events. At a later time another process can come along
44 events can be configured. This means that EBB events can not be run
70 Note that if you are creating a group of EBB events, only the leader can have
90 perf_events API. This can be achieved either via the ioctl() interface, or the
116 When an EBB event is finished with, you can close it using close() as for any
126 are live (possibly) and so must be saved somehow before the handler can invoke
|
| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-konepure | 4 Description: The mouse can store 5 profiles which can be switched by the
25 When written, the device can be reset.
32 Description: The mouse can store a macro with max 500 key/button strokes
43 Description: The mouse can store 5 profiles which can be switched by the
58 Description: The mouse can store 5 profiles which can be switched by the
75 can be activated/deactivated and the lift-off distance can be
92 can be initiated/cancelled. Also lets one read/write sensor
|
| D | sysfs-driver-hid-roccat-koneplus | 40 When written, the device can be reset.
47 Description: The mouse can store a macro with max 500 key/button strokes
58 Description: The mouse can store 5 profiles which can be switched by the
73 Description: The mouse can store 5 profiles which can be switched by the
85 Description: The mouse can store 5 profiles which can be switched by the
101 Description: The mouse can store 5 profiles which can be switched by the
115 can be activated/deactivated and the lift-off distance can be
132 can be initiated/cancelled. Also lets one read/write sensor
|
| D | sysfs-driver-hid-roccat-savu | 4 Description: The mouse can store 5 profiles which can be switched by the
27 Description: The mouse can store 5 profiles which can be switched by the
43 When written, the device can be reset.
61 Description: The mouse can store 5 profiles which can be switched by the
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | debugfs.txt | 6 debugfs has no rules at all. Developers can put any information they want
20 options can be used.
33 dentry pointer which can be used to create files in the directory (and to
50 operations should be provided; others can be included as needed. Again,
54 Create a file with an initial size, the following function can be used
67 for simple situations. Files containing a single integer value can be
82 the following functions can be used instead:
94 value to be exported. Some types can have different widths on different
105 Boolean values can be placed in debugfs with:
114 Also, atomic_t values can be placed in debugfs with:
[all …]
|
| D | dlmfs.txt | 47 your lockspace can access. The easiest way to do this is via
49 that an OCFS2 file system be in place so that it can automatically
56 Once you're heartbeating, DLM lock 'domains' can be easily created /
62 Users may access dlmfs via standard file system calls, or they can use
77 Lock value blocks can be read and written to a resource via read(2)
80 OCFS2 DLM limitation). Through this mechanism, users of dlmfs can share
116 supported locally as well. This means you can use them to restrict
120 Exclusive modes via the read(2) system call. It can be written via
|
| D | seq_file.txt | 11 Virtual files can provide human-readable output that is easy to get at
12 without any special utility programs; they can also make life easier for
45 better to do. The file is seekable, in that one can do something like the
54 wanting to see the full source for this module can find it at
75 Positioning can thus be done in whatever way makes the most sense for the
104 structure can be used. There is also a special value which can be returned
105 by the start() function called SEQ_START_TOKEN; it can be used if you wish
112 example module can simply increment the position by one; more useful
145 passed back to user space. This function can also return SEQ_SKIP, which
165 the seq_file code. It can thus be anything that is useful in stepping
[all …]
|
| D | relay.txt | 36 At this point, userspace can be notified so it empties the first
41 message couldn't fit into a sub-buffer. Userspace can use this
44 After copying it, userspace can notify the kernel that a sub-buffer
47 A relay channel can operate in a mode where it will overwrite data not
101 klog and the relay-apps examples can be found in the relay-apps
114 memory space. Note that you can't do a partial mmap - you
120 in no-overwrite mode (the default), it can be read at any
194 created for it in the host filesystem, which can be and mmapped or
263 easily implement random-access-on-buffer-boundary schemes, which can
273 The create_buf_file() implementation can also be defined in such a way
[all …]
|
| /linux-4.4.14/tools/perf/ |
| D | design.txt | 8 without slowing down the kernel or applications. These registers can also
9 trigger interrupts when a threshold number of events have passed - and can
28 The syscall returns the new fd. The fd can be used via the normal
29 VFS system calls: read() can be used to read the counter, fcntl()
30 can be used to set the blocking mode, etc.
32 Multiple counters can be kept open at a time, and the counters
33 can be poll()ed.
145 tracer is available, and event_id values can be obtained from
160 * Bits that can be set in hw_event.read_format to request that
169 Using these additional values one can establish the overcommit ratio for a
[all …]
|
| /linux-4.4.14/drivers/net/can/c_can/ |
| D | c_can.c | 491 const struct can_bittiming *bt = &priv->can.bittiming; in c_can_set_bittiming()
561 if ((priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) && in c_can_chip_config()
562 (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK)) { in c_can_chip_config()
566 } else if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) { in c_can_chip_config()
570 } else if (priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) { in c_can_chip_config()
606 priv->can.state = CAN_STATE_ERROR_ACTIVE; in c_can_start()
629 priv->can.state = CAN_STATE_STOPPED; in c_can_stop()
867 priv->can.can_stats.error_warning++; in c_can_handle_state_change()
868 priv->can.state = CAN_STATE_ERROR_WARNING; in c_can_handle_state_change()
872 priv->can.can_stats.error_passive++; in c_can_handle_state_change()
[all …]
|
| /linux-4.4.14/arch/cris/boot/compressed/ |
| D | README | 4 This can be slightly confusing because it's a process with many steps.
10 Those files together with a ROM filesystem can be catted together and
13 They can also be catted together and compressed with gzip, which is what
18 into the file vmlinuz. It can be executed in an arbitrary place in flash.
|
| /linux-4.4.14/fs/nilfs2/ |
| D | Kconfig | 7 file system, users can even restore files mistakenly overwritten or
8 destroyed just a few seconds ago. Since this file system can keep
13 synchronous write basis (unless there is no change). Users can
15 and can change them into snapshots which will be preserved for long
|
| /linux-4.4.14/Documentation/fb/ |
| D | ep93xx-fb.txt | 5 The EP93xx LCD controller can drive both standard desktop monitors and
7 can use the standard Linux video mode database. In your board file:
24 Note that the pixel clock value is in pico-seconds. You can use the
39 The framebuffer device can be registered by adding the following to
48 The ep93xxfb_mach_info structure has a flags field which can be used
66 The physical address of the framebuffer can be controlled using the
89 an argument. The fb_info and ep93xxfb_mach_info structures can be
129 error is returned. The check can be disabled by adding the following
|
| D | framebuffer.txt | 44 The frame buffer devices are also `normal' memory devices, this means, you can
45 read and write their contents. You can, for example, make a screen snapshot by
49 There also can be more than one frame buffer at a time, e.g. if you have a
54 use /dev/fb0 by default (older software uses /dev/fb0current). You can specify
72 it has the same features. You can read it, write it, seek to some location in
78 the hardware can be queried and set. The color map handling works via ioctls,
82 - You can request unchangeable information about the hardware, like name,
86 - You can request and change variable information about the hardware, like
92 - You can get and set parts of the color map. Communication is done with 16
107 the like can be implemented as kernel modules that are loaded at runtime. Such
[all …]
|
| D | sstfb.txt | 19 with the vga passthrou cable, I can only suggest borrowing a screen
28 You can apply the patches found in sstfb/kernel/*-2.{2|4}.x.patch,
44 the commands, or you can blindly use sst_dbg_vgapass
60 the device will be /dev/fb0. You can check this by doing a
61 cat /proc/fb. You can find a copy of con2fb in tools/ directory.
68 bind the tty to the old frame buffer so the module can be removed.
75 You can pass some options to the sstfb module, and via the kernel
117 These tools are mostly for debugging purposes, but you can
155 console subsystem can cause some troubles, specifically, you should
156 disable software scrollback, as it can oops badly ...
[all …]
|
| /linux-4.4.14/Documentation/filesystems/configfs/ |
| D | configfs.txt | 29 mkdir(2) time, and can be read or modified via read(2) and write(2).
31 symlink(2) can be used to group items together. Unlike sysfs, the
35 Both sysfs and configfs can and should exist together on the same
40 configfs can be compiled as a module or into the kernel. You can access
52 appear at this time. readdir(3) can determine what the attributes are,
53 read(2) can query their default values, and write(2) can store new
66 symlink(2)). Links can be removed via unlink(2).
82 A fakenbd connection can be created with mkdir(2). The name is
118 subsystem is also a config_group, and can do everything a config_group
119 can.
[all …]
|
| /linux-4.4.14/drivers/net/wireless/ipw2x00/ |
| D | Kconfig | 23 You can obtain the firmware from
37 this driver into your kernel image, you can avoid this problem by
45 With this feature compiled into the driver, you can switch to
47 mode, no packets can be sent.
55 This will result in the kernel module being ~60k larger. You can
85 You can obtain the firmware from
99 this driver into your kernel image, you can avoid this problem by
107 With this feature compiled into the driver, you can switch to
109 mode, no packets can be sent.
185 can control which debug output is sent to the kernel log by
[all …]
|
| /linux-4.4.14/drivers/iio/temperature/ |
| D | Kconfig | 13 This driver can also be built as a module. If so, the module will
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/thermal/ |
| D | x86_pkg_temperature_thermal | 21 user mode can receive notification via thermal notification mechanism and can
35 User can set any temperature between 0 to TJ-Max temperature. Temperature units
39 Any value other than 0 in these trip points, can trigger thermal notifications.
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | gpio-keys.txt | 18 Note that either "interrupts" or "gpios" properties can be omitted, but not
26 - wakeup-source: Boolean, button can wake-up the system.
28 - linux,can-disable: Boolean, indicates that button is connected
29 to dedicated (not shared) interrupt which can be disabled to
|
| D | gpio-matrix-keypad.txt | 4 The matrix keypad supports multiple row and column lines, a key can be
6 keypad can sense a key-press and key-release by means of GPIO lines and
17 - linux,keymap: The definition can be found at
26 before we can scan keypad after activating column gpio
|
| /linux-4.4.14/fs/pstore/ |
| D | Kconfig | 8 persistent storage via "pstore" filesystem that can
30 data can be retrieved from /sys/fs/pstore/pmsg-ramoops-[ID].
41 ram buffer that can be decoded and dumped after reboot through
42 pstore filesystem. It can be used to determine what function
57 buffer in RAM where it can be read back at some later point.
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 3 System on chip designs are often divided into multiple PM domains that can be
7 This device tree binding can be used to bind PM domain consumer devices with
8 their PM domains provided by PM domain providers. A PM domain provider can be
9 represented by any node in the device tree and can provide one or more PM
10 domains. A consumer node can refer to the provider by a phandle and a set of
19 providing multiple PM domains (e.g. power controllers), but can be any value
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | common.txt | 7 Many LED devices expose more than one current output that can be connected
9 can influence the way of the LED device initialization, the LED components
19 a device, i.e. no other LED class device can be assigned the same
33 can be made mandatory for the board configurations
46 property can be omitted.
48 property can be omitted.
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-crypt.txt | 25 You can only use key sizes that are valid for the selected cipher
27 Note that for some iv modes the key string can contain additional
32 Multi-key compatibility mode. You can define <keycount> keys and
42 encrypted data. You can specify it as a path like /dev/xxx or a device
50 the optional paramaters section can be skipped or #opt_params can be zero.
63 used space etc.) if the discarded blocks can be located easily on the
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | pnfs.txt | 4 The are several inter-related caches. We have layouts which can
5 reference multiple devices, each of which can reference multiple data servers.
6 Each data server can be referenced by multiple devices. Each device
7 can be referenced by multiple layouts. To keep all of this straight,
37 justification, but seems reasonable given that we can have multiple
41 hashing and variations of this algorithm can be found at:
80 This name can be overridden by the Kernel module parameter:
84 and will not attempt farther logins. An admin can then write new value
95 (More protocols can be defined in the future.
|
| /linux-4.4.14/Documentation/RCU/ |
| D | rcu_dereference.txt | 3 Most of the time, you can use values from rcu_dereference() or one of
13 will complain. Worse yet, your code can see random memory-corruption
14 bugs due to games that compilers and DEC Alpha can play.
16 can reload the value, and won't your code have fun with two
18 DEC Alpha can load a pointer, dereference that pointer, and
25 for an example where the compiler can in fact deduce the exact
50 Please note that single-bit operands to bitwise "&" can also
52 resulting value can only take on one of two possible values.
54 allow the compiler to deduce the exact value, which again can
80 do order stores after such branches, they can speculate loads,
[all …]
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | GPIO.txt | 49 it can use it.
54 2) The s3c2410_gpio_cfgpin() can be directly replaced with s3c_gpio_cfgpin()
55 as they have the same arguments, and can either take the pin specific
59 s3c2410_gpio_pullup(x, 1) can be easily translated to the
68 4) s3c2410_gpio_setpin() can be replaced by gpio_set_value(), the old call
126 The current configuration of a pin can be read by using standard
131 The return value will be from the same set of values which can be
138 A large proportion of the GPIO pins on the S3C2410 can have weak
139 pull-up resistors enabled. This can be configured by the following
159 A standard gpiolib function can map the given pin number to an IRQ
|
| /linux-4.4.14/Documentation/arm/ |
| D | tcm.txt | 11 and a DTCM (data TCM). The DTCM can not contain any
12 instructions, but the ITCM can actually contain data.
18 defines a CPUID_TCM register that you can read out from the
19 system control coprocessor. Documentation from ARM can be found
21 to see documents for all CPUs. Reading this register you can
26 Registers" at the ARM site) that can report and modify the location
34 The TCM memory can then be remapped to another address again using
80 Functions to go into itcm can be tagged like this:
88 Variables to go into dtcm can be tagged like this:
91 Constants can be tagged like this:
|
| /linux-4.4.14/scripts/coccinelle/misc/ |
| D | warn.cocci | 34 cocci.print_main("printk + WARN_ON can be just WARN",p)
40 msg = "SUGGESTION: printk + WARN_ON can be just WARN"
83 cocci.print_main("printk + WARN_ON_ONCE can be just WARN_ONCE",p)
89 msg = "SUGGESTION: printk + WARN_ON_ONCE can be just WARN_ONCE"
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | packet-writing.txt | 19 - Now you can mount /dev/pktcdvd/dev_name and copy files to it. Enjoy!
26 DVD-RW discs can be written to much like CD-RW discs if they are in
32 You can then use the disc the same way you would use a CD-RW disc:
56 Both problems can be solved by using the pktcdvd driver, which always
69 necessary. However, using the pktcdvd driver can improve performance
76 - CD-RW media can usually not be overwritten more than about 1000
85 device with a 2KB block size, you can put any filesystem you like on
97 and can be controlled by it. For example the "pktcdvd" tool uses
|
| /linux-4.4.14/drivers/net/can/spi/ |
| D | mcp251x.c | 244 struct can_priv can; member
544 priv->can.state = CAN_STATE_ERROR_ACTIVE; in mcp251x_do_set_mode()
546 if (priv->can.restart_ms == 0) in mcp251x_do_set_mode()
567 if (priv->can.ctrlmode & CAN_CTRLMODE_LOOPBACK) { in mcp251x_set_normal_mode()
570 } else if (priv->can.ctrlmode & CAN_CTRLMODE_LISTENONLY) { in mcp251x_set_normal_mode()
588 priv->can.state = CAN_STATE_ERROR_ACTIVE; in mcp251x_set_normal_mode()
595 struct can_bittiming *bt = &priv->can.bittiming; in mcp251x_do_set_bittiming()
601 (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES ? in mcp251x_do_set_bittiming()
718 priv->can.state = CAN_STATE_STOPPED; in mcp251x_stop()
752 if (priv->can.state == CAN_STATE_BUS_OFF) { in mcp251x_tx_work_handler()
[all …]
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-list.txt | 15 This command displays the symbolic event types which can be selected in the
22 Events can optionally have a modifier by appending a colon and one or
37 The 'p' modifier can be used for specifying how precise the instruction
38 address should be. The 'p' modifier can be specified multiple times:
40 0 - SAMPLE_IP can have arbitrary skid
63 it can be encoded in a per processor specific way.
70 Note: Only the following bit fields can be set in x86 counter
86 raw encoding of 0x1A8 can be used:
131 One or more types can be used at the same time, listing the events for the
|
| D | itrace.txt | 14 can be specified in units of:
23 transactions events can be specified.
26 instructions or transactions events can be specified.
|
| /linux-4.4.14/Documentation/s390/ |
| D | CommonIO | 20 An ignored device can be un-ignored later; see the "/proc entries"-section for
27 You can use the 'all' keyword to ignore all devices. The 'ipldev' and 'condev'
28 keywords can be used to refer to the CCW based boot device and CCW console
51 You can un-ignore certain or all devices by piping to /proc/cio_ignore.
69 You can also add ranges of devices to be ignored by piping to
73 Note: While already known devices can be added to the list of devices to be
83 You can remove already known but now ignored devices via
88 The devices can be specified either by bus id (0.x.abcd) or, for 2.4 backward
122 The level of logging can be changed to be more or less verbose by piping to
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | ESS | 19 For ESS chips an additional parameter "esstype" can be specified. This controls
20 the (auto) detection of the ESS chips. It can have 3 kinds of values:
32 Because Full Duplex is supported for ES1887 you can specify a second DMA
33 channel by specifying module parameter dma16. It can be one of: 0, 1, 3 or 5.
|
| D | PSS-updates | 23 address can be specified to enable the CDROM port, except for 0x0 and -1 as
25 port will require that an appropriate CDROM driver be loaded before you can make
42 This module parameter is a flag that can be used to tell the driver to
45 parameter can be used by a user who only wished to use the builtin joystick
47 parameter and with the parameter below set to true then a user can safely unload
56 This parameter can be used to specify whether you want the driver to reset
57 all emulations whenever its unloaded. This can be useful for those who are
59 flag can also be useful in that future versions of this driver may reset all
67 This parameter can be used to specify the file containing the firmware
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | devres.txt | 50 a release function. A devres can be released in several ways. No
100 driver can have much simpler init and exit code. Init path basically
130 As shown above, low level drivers can be simplified a lot by using
133 shared with exit path, both can get more testing.
139 Devres entries can be grouped using devres group. When a group is
168 Each group is identified by void *id. It can either be explicitly
172 can be passed to other devres functions to select the target group.
176 For example, you can do something like the following.
212 All devres interface functions can be called without context if the
222 up to ull alignment). If singly linked list is used, it can be
[all …]
|
| /linux-4.4.14/Documentation/security/ |
| D | Yama.txt | 3 selectable at build-time with CONFIG_SECURITY_YAMA, and can be controlled
37 prctl(PR_SET_PTRACER, pid, ...) can be used. An inferior can declare which
39 against it. Only one such declared debugging process can exists for
43 restrictions, it can call prctl(PR_SET_PTRACER, PR_SET_PTRACER_ANY, ...)
49 0 - classic ptrace permissions: a process can PTRACE_ATTACH to any other
59 inferior can call prctl(PR_SET_PTRACER, debugger, ...) to declare
|
| /linux-4.4.14/arch/m68k/q40/ |
| D | README | 12 It seems IRQ unmasking can't be safely done on a Q40. IRQ probing
21 it can make the floppy very slow or practically stop. Other Q40 OS' simply
22 poll the floppy for this reason - something that can't be done in Linux.
44 Various other PC drivers can be enabled simply by adding them to
60 SRAM can also be used as additional console device, use debug=mem.
65 Serial console works and can also be used for debugging, see loader_txt
89 or from some ISA devices, EIRQ_REG can distinguish up to 8 ISA IRQs.
112 because only irq's 4-15 can be disabled - and only all of them at once.
113 Thus disable_irq() can effectively block the machine if the driver goes
130 There is still hope that it can be fixed completely though. If you encounter
|
| /linux-4.4.14/Documentation/console/ |
| D | console.txt | 7 to exist. The system driver is persistent and it can never be unloaded, though
11 'modular driver' by this document. Multiple modular drivers can coexist at
16 of driver occupying the consoles.) They can only take over the console that is
30 If sysfs is enabled, the contents of /sys/class/vtconsole can be
67 In this case, '(M)' stands for a (M)odular driver, one that can be
87 developers. By unbinding the driver from the console layer, one can unload the
127 ensured because con->con_startup() can be called again when a request to
134 5. do_unregister_con_driver() can also be called on conditions which make it
135 impossible for the driver to service console requests. This can happen
139 and unbinding them may cause problems. With minimal fixes, these drivers can
|
| /linux-4.4.14/Documentation/pps/ |
| D | pps.txt | 7 This program is free software; you can redistribute it and/or modify
27 can use it to adjust system clock time.
29 A PPS source can be connected to a serial port (usually to the Data
51 ok for the serial and parallel port, where you can do something
58 The problem can be simply solved if you consider that a PPS source is
78 If your device doesn't report PPS, you can check that the feature is
116 Once you have registered a new PPS source into the system you can
145 Inside each "assert" and "clear" file you can find the timestamp and a
167 In order to test the PPS support even without specific hardware you can use
223 so it is used for PPS assert edge. PPS clear edge can be determined only
[all …]
|
| /linux-4.4.14/Documentation/arm/OMAP/ |
| D | DSS | 11 currently side by side, you can choose which one to use.
23 - All pieces can be compiled as a module or inside kernel
43 drivers can use.
48 managers. These can be used when updating a display with CPU or system DMA.
106 These framebuffers can be routed flexibly to any overlays, thus allowing very
139 A framebuffer can be connected to multiple overlays to show the same pixel data
141 the same, but, in case of video overlays, the output size can be different. Any
142 framebuffer can be connected to any overlay.
144 An overlay can be connected to one overlay manager. Also DISPC overlays can be
145 connected only to DISPC overlay managers, and virtual overlays can be only
[all …]
|
| /linux-4.4.14/Documentation/locking/ |
| D | ww-mutex-design.txt | 10 can be shared across contexts/processes, exist in different memory
12 PRIME / dmabuf, they can even be shared across devices. So there are
24 simplified understanding of the problem you can ignore this.
36 The older tasks waits until it can acquire the contended lock. The younger tasks
73 very first lock operation can never fail.
77 slowpath until the contended lock can be acquired).
110 Furthermore the lock helper can use propagate the -EALREADY return code back to
157 Method 2, using a list in execbuf->buffers that can be reordered. Same semantics
211 and edges can only be changed when holding the locks of all involved nodes. w/w
213 - They can handle lock-acquisition in any order which allows us to start walking
[all …]
|
| /linux-4.4.14/Documentation/networking/mac80211_hwsim/ |
| D | README | 4 This program is free software; you can redistribute it and/or modify
11 mac80211_hwsim is a Linux kernel module that can be used to simulate
12 arbitrary number of IEEE 802.11 radios for mac80211. It can be used to
24 since all radio operation is simulated, any channel can be used in
27 mac80211_hwsim kernel module has a parameter 'radios' that can be used
41 mac80211. This interface can be used to monitor all transmitted frames
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | v4l2-framework.txt | 19 more I2C busses, but other busses can also be used. Such devices are
40 framework. It can be used as a template for real PCI video capture driver.
86 Very simple devices can just allocate this struct, but most of the time you
108 You can use v4l2_device_set_name() to set the name based on a driver name and
118 You can also supply a notify() callback that can be called by sub-devices to
146 You can iterate over all registered devices as follows:
186 If you have multiple device nodes then it can be difficult to know when it is
191 callback is called. You can do your final cleanup there.
193 If other device nodes (e.g. ALSA) are created, then you can increase and
209 Many drivers need to communicate with sub-devices. These devices can do all
[all …]
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | lis3lv02d | 21 models (full list can be found in drivers/platform/x86/hp_accel.c) will have
22 their axis automatically oriented on standard way (eg: you can directly play
35 the laptop to act as a pinball machine-esque joystick. Joystick device can be
36 calibrated. Joystick device can be in two different modes.
38 mode, joystick and sysfs position entry have the same scale. There can be
71 (aka "can play neverball out of the box"):
79 If your laptop model is not recognized (cf "dmesg"), you can send an
91 A: The sensor is pretty sensitive, so your hands can do it. Lift it
|
| /linux-4.4.14/Documentation/devicetree/bindings/timer/ |
| D | ti,keystone-timer.txt | 4 architecture devices. The timer can be configured as a general-purpose 64-bit
6 timers, each half can operate in conjunction (chain mode) or independently
9 It is global timer is a free running up-counter and can generate interrupt
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | provider.txt | 13 Requests and channels are pretty much orthogonal. Channels can be used
34 is why most if not all of the DMA controllers can adjust this, using a
38 or destination, can group the reads or writes in memory into a buffer,
129 - This can be either:
187 - Even though a plain memcpy can look like a particular case of a
201 - The device can handle device to memory transfers, including
211 - The device can handle cyclic transfers.
219 - These transfers can transfer data from a non-contiguous buffer
220 to a non-contiguous buffer, opposed to DMA_SLAVE that can
254 - These functions can sleep.
[all …]
|
| /linux-4.4.14/Documentation/cpuidle/ |
| D | governor.txt | 17 * reflect() called after returning from the idle state, which can be used
20 More than one governor can be registered at the same time and
21 users can switch between drivers using /sysfs interface (when enabled).
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,vic.txt | 3 One or more Vectored Interrupt Controllers (VIC's) can be connected in an ARM
4 system for interrupt routing. For multiple controllers they can either be
25 - valid-wakeup-mask : A one cell big bit mask of interrupt sources that can be
27 valid-mask property. A set bit means that this interrupt source can be
|
| /linux-4.4.14/drivers/infiniband/ulp/ipoib/ |
| D | Kconfig | 6 transports IP packets over InfiniBand so you can use your IB
32 IPoIB driver. The output can be turned on via the
34 can also be set after the driver is loaded through sysfs).
46 of the IPoIB driver. The output can be turned on via the
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | dma.txt | 38 integrated with DMA requests than what the DMA controller can handle directly.
42 the DMA controllers the router can direct the signal to.
48 - dma-requests: Number of incoming request lines the router can handle.
75 channel number, but can contain any data that is
78 the dmas property. The specific strings that can be used
80 Multiple DMA specifiers can be used to represent
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-rt-group.txt | 21 Fiddling with these settings can result in an unstable system, the knobs are
26 * very small values in sched_rt_period_us can result in an unstable
30 * very small values in sched_rt_runtime_us can result in an unstable
45 of the CPU time available. Without a minimum guarantee a realtime group can
52 CPU time is divided by means of specifying how much time can be spent running
63 time dedicated for the graphics. We can then give this group a run time of 0.8
68 needs only about 3% CPU time to do so, it can do with a 0.03 * 0.005s =
69 0.00015s. So this group can be scheduled with a period of 0.005s and a run time
74 their tasks, buffer underruns in the graphics or audio can be eliminated.
143 For now, this can be simplified to just the following (but see Future plans):
[all …]
|
| /linux-4.4.14/Documentation/ABI/ |
| D | README | 23 The interface can be changed to add new features, but the
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
30 these interfaces, so that the kernel developers can easily
38 why it is obsolete and when it can be expected to be removed.
53 the "testing" stage, so that kernel developers can work
69 Interfaces in the testing state can move to the stable state when the
|