| /linux-3.4.99/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
|
| /linux-3.4.99/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 …]
|
| /linux-3.4.99/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,
56 synthesizer. You can say y to build it into the kernel,
64 synthesizer. You can say y to build it into the kernel,
[all …]
|
| /linux-3.4.99/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
49 chip can be found on Abit uGuru featuring motherboards (most modern
54 This driver can also be built as a module. If so, the module
64 uGuru chip can be found on recent Abit motherboards (since end
68 This driver can also be built as a module. If so, the module
78 This driver can also be built as a module. If so, the module
88 This driver can also be built as a module. If so, the module
98 This driver can also be built as a module. If so, the module
114 This driver can also be built as a module. If so, the module
[all …]
|
| /linux-3.4.99/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-3.4.99/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 overriden 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 protocol/port pairs.
78 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
88 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
[all …]
|
| /linux-3.4.99/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
|
| /linux-3.4.99/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
57 This driver can also be built as a module. If so, the module will
67 This driver can also be built as a module. If so, the module will
77 This driver can also be built as a module. If so, the module will
87 This driver can also be built as a module. If so, the module will
98 This driver can also be built as a module. If so, the module will
109 This driver can also be built as a module. If so, the module will
[all …]
|
| /linux-3.4.99/drivers/net/can/mscan/ |
| D | mscan.c | 102 priv->can.state = CAN_STATE_SLEEPING; in mscan_set_mode()
115 priv->can.state = CAN_STATE_STOPPED; in mscan_set_mode()
132 priv->can.state = CAN_STATE_ERROR_ACTIVE; in mscan_set_mode()
166 priv->can.state = state_map[max(MSCAN_STATE_RX(canrflg), in mscan_start()
183 priv->can.state = CAN_STATE_ERROR_ACTIVE; in mscan_restart()
190 if (priv->can.state <= CAN_STATE_BUS_OFF) in mscan_restart()
297 enum can_state state, old_state = priv->can.state; in check_set_state()
302 priv->can.state = state; in check_set_state()
369 if (old_state != priv->can.state) { in mscan_get_err_frame()
370 switch (priv->can.state) { in mscan_get_err_frame()
[all …]
|
| /linux-3.4.99/drivers/net/can/sja1000/ |
| D | sja1000.c | 127 priv->can.state = CAN_STATE_STOPPED; in set_reset_mode()
148 priv->can.state = CAN_STATE_ERROR_ACTIVE; in set_normal_mode()
150 if (priv->can.ctrlmode & CAN_CTRLMODE_BERR_REPORTING) in set_normal_mode()
172 if (priv->can.state != CAN_STATE_STOPPED) in sja1000_start()
208 struct can_bittiming *bt = &priv->can.bittiming; in sja1000_set_bittiming()
214 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) in sja1000_set_bittiming()
376 enum can_state state = priv->can.state; in sja1000_err()
408 priv->can.can_stats.bus_error++; in sja1000_err()
446 priv->can.can_stats.arbitration_lost++; in sja1000_err()
452 if (state != priv->can.state && (state == CAN_STATE_ERROR_WARNING || in sja1000_err()
[all …]
|
| /linux-3.4.99/drivers/net/can/ |
| D | Kconfig | 11 This driver can also be built as a module. If so, the module
27 slcand) can be found in the can-utils at the SocketCAN SVN, see
31 can be changed by the 'maxdev=xx' module option. This driver can
93 This driver can also be built as a module. If so, the module will be
111 This driver can access CAN bus.
113 source "drivers/net/can/mscan/Kconfig"
115 source "drivers/net/can/sja1000/Kconfig"
117 source "drivers/net/can/c_can/Kconfig"
119 source "drivers/net/can/cc770/Kconfig"
121 source "drivers/net/can/usb/Kconfig"
[all …]
|
| D | bfin_can.c | 35 struct can_priv can; /* must be the first member */ member
68 struct can_bittiming *bt = &priv->can.bittiming; in bfin_can_set_bittiming()
79 if (priv->can.ctrlmode & CAN_CTRLMODE_3_SAMPLES) in bfin_can_set_bittiming()
149 priv->can.state = CAN_STATE_STOPPED; in bfin_can_set_reset_mode()
201 if (priv->can.state != CAN_STATE_STOPPED) in bfin_can_start()
337 enum can_state state = priv->can.state; in bfin_can_err()
370 if (state != priv->can.state && (state == CAN_STATE_ERROR_WARNING || in bfin_can_err()
378 priv->can.can_stats.error_warning++; in bfin_can_err()
383 priv->can.can_stats.error_passive++; in bfin_can_err()
391 priv->can.can_stats.bus_error++; in bfin_can_err()
[all …]
|
| /linux-3.4.99/drivers/staging/usbip/userspace/ |
| 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-3.4.99/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 …]
|
| /linux-3.4.99/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
|
| /linux-3.4.99/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-3.4.99/security/tomoyo/ |
| D | Kconfig | 35 audit logs that the kernel can hold on memory.
36 You can read the log via /sys/kernel/security/tomoyo/audit.
46 operations which can lead to the hijacking of the boot sequence are
47 needed before loading the policy. For example, you can activate
51 loading the variant part of policy. Since you can start using
52 enforcing mode from the beginning, you can reduce the possibility of
62 activation. You can override this setting via TOMOYO_loader= kernel
72 You can override this setting via TOMOYO_trigger= kernel command line
|
| /linux-3.4.99/drivers/rtc/ |
| D | Kconfig | 91 can be accessed as /dev/rtc, which is a name
113 RTC test driver. It's a software RTC which can be
120 This driver can also be built as a module. If so, the module
135 This driver can also be built as a module. If so, the module
153 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
173 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
193 This driver can also be built as a module. If so, the module
203 This driver can also be built as a module. If so, the module
[all …]
|
| /linux-3.4.99/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 …]
|
| /linux-3.4.99/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 …]
|
| /linux-3.4.99/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
31 5.1 can.ko module params
90 controller can be passed up to the network layer and on to the CAN
93 that any number of transport protocols can be loaded or unloaded
94 dynamically. In fact, the can core module alone does not provide any
96 protocol module. Multiple sockets can be opened at the same time,
97 on different or the same protocol module and they can listen/send
102 selects that protocol when opening the socket, and then can read and
157 For this reason a CAN-ID can be treated best as a kind of source address.
169 CAN-IDs can be done for specific CAN interfaces or for all(!) known
[all …]
|
| /linux-3.4.99/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-3.4.99/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-3.4.99/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:
|