| /linux-3.3/arch/blackfin/mach-bf548/include/mach/ |
| D | defBF548.h | 16 /* CAN Controller 1 Config 1 Registers */
18 #define CAN1_MC1 0xffc03200 /* CAN Controller 1 Mailbox Configuration Re…
19 #define CAN1_MD1 0xffc03204 /* CAN Controller 1 Mailbox Direction Regist…
20 #define CAN1_TRS1 0xffc03208 /* CAN Controller 1 Transmit Request Set Reg…
21 #define CAN1_TRR1 0xffc0320c /* CAN Controller 1 Transmit Request Reset R…
22 #define CAN1_TA1 0xffc03210 /* CAN Controller 1 Transmit Acknowledge Reg…
23 #define CAN1_AA1 0xffc03214 /* CAN Controller 1 Abort Acknowledge Regist…
24 #define CAN1_RMP1 0xffc03218 /* CAN Controller 1 Receive Message Pending …
25 #define CAN1_RML1 0xffc0321c /* CAN Controller 1 Receive Message Lost Reg…
26 #define CAN1_MBTIF1 0xffc03220 /* CAN Controller 1 Mailbox Transmit Interru…
[all …]
|
| D | defBF544.h | 73 /* CAN Controller 1 Config 1 Registers */
75 #define CAN1_MC1 0xffc03200 /* CAN Controller 1 Mailbox Configuration Re…
76 #define CAN1_MD1 0xffc03204 /* CAN Controller 1 Mailbox Direction Regist…
77 #define CAN1_TRS1 0xffc03208 /* CAN Controller 1 Transmit Request Set Reg…
78 #define CAN1_TRR1 0xffc0320c /* CAN Controller 1 Transmit Request Reset R…
79 #define CAN1_TA1 0xffc03210 /* CAN Controller 1 Transmit Acknowledge Reg…
80 #define CAN1_AA1 0xffc03214 /* CAN Controller 1 Abort Acknowledge Regist…
81 #define CAN1_RMP1 0xffc03218 /* CAN Controller 1 Receive Message Pending …
82 #define CAN1_RML1 0xffc0321c /* CAN Controller 1 Receive Message Lost Reg…
83 #define CAN1_MBTIF1 0xffc03220 /* CAN Controller 1 Mailbox Transmit Interru…
[all …]
|
| D | defBF54x_base.h | 1040 /* CAN Controller 0 Config 1 Registers */
1042 #define CAN0_MC1 0xffc02a00 /* CAN Controller 0 Mailbox Configuration Re…
1043 #define CAN0_MD1 0xffc02a04 /* CAN Controller 0 Mailbox Direction Regist…
1044 #define CAN0_TRS1 0xffc02a08 /* CAN Controller 0 Transmit Request Set Reg…
1045 #define CAN0_TRR1 0xffc02a0c /* CAN Controller 0 Transmit Request Reset R…
1046 #define CAN0_TA1 0xffc02a10 /* CAN Controller 0 Transmit Acknowledge Reg…
1047 #define CAN0_AA1 0xffc02a14 /* CAN Controller 0 Abort Acknowledge Regist…
1048 #define CAN0_RMP1 0xffc02a18 /* CAN Controller 0 Receive Message Pending …
1049 #define CAN0_RML1 0xffc02a1c /* CAN Controller 0 Receive Message Lost Reg…
1050 #define CAN0_MBTIF1 0xffc02a20 /* CAN Controller 0 Mailbox Transmit Interru…
[all …]
|
| /linux-3.3/Documentation/networking/ |
| D | can.txt | 3 can.txt
5 Readme file for the Controller Area Network Protocol Family (aka Socket CAN)
9 1 Overview / What is Socket CAN
13 3 Socket CAN concept
19 4 How to use Socket CAN
30 5 Socket CAN core module
31 5.1 can.ko module params
33 5.3 writing own CAN protocol modules
35 6 CAN network drivers
38 6.3 CAN controller hardware filters
[all …]
|
| /linux-3.3/drivers/net/can/ |
| D | Kconfig | 1 menu "CAN Device Drivers"
2 depends on CAN
5 tristate "Virtual Local CAN Interface (vcan)"
6 depends on CAN
9 virtual local CAN interface.
11 This driver can also be built as a module. If so, the module
15 tristate "Serial / USB serial CAN Adaptors (slcan)"
16 depends on CAN
18 CAN driver for several 'low cost' CAN interfaces that are attached
22 As only the sending and receiving of CAN frames is implemented, this
[all …]
|
| /linux-3.3/net/can/ |
| D | Kconfig | 2 # Controller Area Network (CAN) network layer core configuration
5 menuconfig CAN config
7 tristate "CAN bus subsystem support"
9 Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
13 More information on the CAN network protocol family PF_CAN
14 is contained in <Documentation/networking/can.txt>.
16 If you want CAN support you should say Y here and also to the
20 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
21 depends on CAN
24 The raw CAN protocol option offers access to the CAN bus via
[all …]
|
| 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.3/include/linux/can/ |
| D | gw.h | 2 * linux/can/gw.h
4 * Definitions for CAN frame Gateway/Router/Bridge
16 #include <linux/can.h>
24 /* CAN gateway types */
27 CGW_TYPE_CAN_CAN, /* CAN->CAN routing */
33 /* CAN rtnetlink attribute definitions */
36 CGW_MOD_AND, /* CAN frame modification binary AND */
37 CGW_MOD_OR, /* CAN frame modification binary OR */
38 CGW_MOD_XOR, /* CAN frame modification binary XOR */
39 CGW_MOD_SET, /* CAN frame modification set alternate values */
[all …]
|
| D | netlink.h | 2 * linux/can/netlink.h
4 * Definitions for the CAN netlink interface
16 * CAN bit-timing parameters
19 * REQUIREMENTS" of the "Bosch CAN Specification version 2.0"
34 * CAN harware-dependent bit-timing constant
39 char name[16]; /* Name of the CAN controller hardware */
51 * CAN clock parameters
54 __u32 freq; /* CAN system clock frequency in Hz */
58 * CAN operational and error states
71 * CAN bus error counters
[all …]
|
| /linux-3.3/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.3/include/linux/ |
| D | can.h | 2 * linux/can.h
4 * Definitions for CAN network layer (socket addr / CAN frame / CAN filter)
19 /* controller area network (CAN) kernel definitions */
26 /* valid bits in CAN ID for frame formats */
34 * bit 0-28 : CAN identifier (11/29 bit)
44 * bit 0-28 : error class mask (see include/linux/can/error.h)
50 * struct can_frame - basic CAN frame structure
51 * @can_id: the CAN ID of the frame and CAN_*_FLAG flags, see above.
52 * @can_dlc: the data length field of the CAN frame
53 * @data: the CAN frame payload.
[all …]
|
| D | gpio.h | 66 /* GPIO can never have been requested */ in gpio_free()
74 /* GPIO can never have been requested */ in gpio_free_array()
95 /* GPIO can never have been requested or set as {in,out}put */ in gpio_get_value()
102 /* GPIO can never have been requested or set as output */ in gpio_set_value()
108 /* GPIO can never have been requested or set as {in,out}put */ in gpio_cansleep()
115 /* GPIO can never have been requested or set as {in,out}put */ in gpio_get_value_cansleep()
122 /* GPIO can never have been requested or set as output */ in gpio_set_value_cansleep()
128 /* GPIO can never have been requested or set as {in,out}put */ in gpio_export()
136 /* GPIO can never have been exported */ in gpio_export_link()
143 /* GPIO can never have been requested */ in gpio_sysfs_set_active_low()
[all …]
|
| /linux-3.3/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.3/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.3/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.3/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.3/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.3/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 …]
|
| /linux-3.3/drivers/net/can/usb/ |
| D | ems_usb.c | 2 * CAN driver for EMS Dr. Thomas Wuensche CPC-USB/ARM7
6 * This program is free software; you can redistribute it and/or modify it
26 #include <linux/can.h>
27 #include <linux/can/dev.h>
28 #include <linux/can/error.h>
31 MODULE_DESCRIPTION("CAN driver for EMS Dr. Thomas Wuensche CAN/USB interfaces");
45 #define CPC_MSG_TYPE_CAN_FRAME 1 /* CAN data frame */
46 #define CPC_MSG_TYPE_RTR_FRAME 8 /* CAN remote frame */
47 #define CPC_MSG_TYPE_CAN_PARAMS 12 /* Actual CAN parameters */
48 #define CPC_MSG_TYPE_CAN_STATE 14 /* CAN state message */
[all …]
|
| /linux-3.3/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.3/Documentation/ |
| 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 …]
|
| /linux-3.3/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.3/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.3/drivers/i2c/busses/ |
| D | Kconfig | 19 This driver can also be built as a module. If so, the module
31 This driver can also be built as a module. If so, the module
41 This driver can also be built as a module. If so, the module
53 This driver can also be built as a module. If so, the module
66 This driver can also be built as a module. If so, the module
76 This driver can also be built as a module. If so, the module
107 This driver can also be built as a module. If so, the module
118 This driver can also be built as a module. If so, the module
145 This driver can also be built as a module. If so, the module
155 This driver can also be built as a module. If so, the module
[all …]
|