Kconfig (77136836aef2c7ce9745e765c1e51a14e3933931) Kconfig (6586c5d74e8c2883ed1246aae81275efb777c088)
1menu "CAN Device Drivers"
2
3config CAN_VCAN
4 tristate "Virtual Local CAN Interface (vcan)"
5 ---help---
6 Similar to the network loopback devices, vcan offers a
7 virtual local CAN interface.
8

--- 22 unchanged lines hidden (view full) ---

31config CAN_DEV
32 tristate "Platform CAN drivers with Netlink support"
33 default y
34 ---help---
35 Enables the common framework for platform CAN drivers with Netlink
36 support. This is the standard library for CAN drivers.
37 If unsure, say Y.
38
1menu "CAN Device Drivers"
2
3config CAN_VCAN
4 tristate "Virtual Local CAN Interface (vcan)"
5 ---help---
6 Similar to the network loopback devices, vcan offers a
7 virtual local CAN interface.
8

--- 22 unchanged lines hidden (view full) ---

31config CAN_DEV
32 tristate "Platform CAN drivers with Netlink support"
33 default y
34 ---help---
35 Enables the common framework for platform CAN drivers with Netlink
36 support. This is the standard library for CAN drivers.
37 If unsure, say Y.
38
39if CAN_DEV
40
39config CAN_CALC_BITTIMING
40 bool "CAN bit-timing calculation"
41config CAN_CALC_BITTIMING
42 bool "CAN bit-timing calculation"
41 depends on CAN_DEV
42 default y
43 ---help---
44 If enabled, CAN bit-timing parameters will be calculated for the
45 bit-rate specified via Netlink argument "bitrate" when the device
46 get started. This works fine for the most common CAN controllers
47 with standard bit-rates but may fail for exotic bit-rates or CAN
48 source clock frequencies. Disabling saves some space, but then the
49 bit-timing parameters must be specified directly using the Netlink
50 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
51 If unsure, say Y.
52
53config CAN_AT91
54 tristate "Atmel AT91 onchip CAN controller"
43 default y
44 ---help---
45 If enabled, CAN bit-timing parameters will be calculated for the
46 bit-rate specified via Netlink argument "bitrate" when the device
47 get started. This works fine for the most common CAN controllers
48 with standard bit-rates but may fail for exotic bit-rates or CAN
49 source clock frequencies. Disabling saves some space, but then the
50 bit-timing parameters must be specified directly using the Netlink
51 arguments "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
52 If unsure, say Y.
53
54config CAN_AT91
55 tristate "Atmel AT91 onchip CAN controller"
55 depends on CAN_DEV && (ARCH_AT91SAM9263 || ARCH_AT91SAM9X5)
56 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9X5
56 ---help---
57 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
58 and AT91SAM9X5 processors.
59
60config CAN_TI_HECC
57 ---help---
58 This is a driver for the SoC CAN controller in Atmel's AT91SAM9263
59 and AT91SAM9X5 processors.
60
61config CAN_TI_HECC
61 depends on CAN_DEV && ARCH_OMAP3
62 depends on ARCH_OMAP3
62 tristate "TI High End CAN Controller"
63 ---help---
64 Driver for TI HECC (High End CAN Controller) module found on many
65 TI devices. The device specifications are available from www.ti.com
66
67config CAN_MCP251X
68 tristate "Microchip MCP251x SPI CAN controllers"
63 tristate "TI High End CAN Controller"
64 ---help---
65 Driver for TI HECC (High End CAN Controller) module found on many
66 TI devices. The device specifications are available from www.ti.com
67
68config CAN_MCP251X
69 tristate "Microchip MCP251x SPI CAN controllers"
69 depends on CAN_DEV && SPI && HAS_DMA
70 depends on SPI && HAS_DMA
70 ---help---
71 Driver for the Microchip MCP251x SPI CAN controllers.
72
73config CAN_BFIN
71 ---help---
72 Driver for the Microchip MCP251x SPI CAN controllers.
73
74config CAN_BFIN
74 depends on CAN_DEV && (BF534 || BF536 || BF537 || BF538 || BF539 || BF54x)
75 depends on BF534 || BF536 || BF537 || BF538 || BF539 || BF54x
75 tristate "Analog Devices Blackfin on-chip CAN"
76 ---help---
77 Driver for the Analog Devices Blackfin on-chip CAN controllers
78
79 To compile this driver as a module, choose M here: the
80 module will be called bfin_can.
81
82config CAN_JANZ_ICAN3
83 tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
76 tristate "Analog Devices Blackfin on-chip CAN"
77 ---help---
78 Driver for the Analog Devices Blackfin on-chip CAN controllers
79
80 To compile this driver as a module, choose M here: the
81 module will be called bfin_can.
82
83config CAN_JANZ_ICAN3
84 tristate "Janz VMOD-ICAN3 Intelligent CAN controller"
84 depends on CAN_DEV && MFD_JANZ_CMODIO
85 depends on MFD_JANZ_CMODIO
85 ---help---
86 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
87 connects to a MODULbus carrier board.
88
89 This driver can also be built as a module. If so, the module will be
90 called janz-ican3.ko.
91
92config HAVE_CAN_FLEXCAN
93 bool
94
95config CAN_FLEXCAN
96 tristate "Support for Freescale FLEXCAN based chips"
86 ---help---
87 Driver for Janz VMOD-ICAN3 Intelligent CAN controller module, which
88 connects to a MODULbus carrier board.
89
90 This driver can also be built as a module. If so, the module will be
91 called janz-ican3.ko.
92
93config HAVE_CAN_FLEXCAN
94 bool
95
96config CAN_FLEXCAN
97 tristate "Support for Freescale FLEXCAN based chips"
97 depends on CAN_DEV && HAVE_CAN_FLEXCAN
98 depends on HAVE_CAN_FLEXCAN
98 ---help---
99 Say Y here if you want to support for Freescale FlexCAN.
100
101config PCH_CAN
102 tristate "Intel EG20T PCH CAN controller"
99 ---help---
100 Say Y here if you want to support for Freescale FlexCAN.
101
102config PCH_CAN
103 tristate "Intel EG20T PCH CAN controller"
103 depends on CAN_DEV && PCI
104 depends on PCI
104 ---help---
105 This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which
106 is an IOH for x86 embedded processor (Intel Atom E6xx series).
107 This driver can access CAN bus.
108
109config CAN_GRCAN
110 tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
105 ---help---
106 This driver is for PCH CAN of Topcliff (Intel EG20T PCH) which
107 is an IOH for x86 embedded processor (Intel Atom E6xx series).
108 This driver can access CAN bus.
109
110config CAN_GRCAN
111 tristate "Aeroflex Gaisler GRCAN and GRHCAN CAN devices"
111 depends on CAN_DEV && OF
112 depends on OF
112 ---help---
113 Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
114 Note that the driver supports little endian, even though little
115 endian syntheses of the cores would need some modifications on
116 the hardware level to work.
117
118source "drivers/net/can/mscan/Kconfig"
119
120source "drivers/net/can/sja1000/Kconfig"
121
122source "drivers/net/can/c_can/Kconfig"
123
124source "drivers/net/can/cc770/Kconfig"
125
126source "drivers/net/can/usb/Kconfig"
127
128source "drivers/net/can/softing/Kconfig"
129
113 ---help---
114 Say Y here if you want to use Aeroflex Gaisler GRCAN or GRHCAN.
115 Note that the driver supports little endian, even though little
116 endian syntheses of the cores would need some modifications on
117 the hardware level to work.
118
119source "drivers/net/can/mscan/Kconfig"
120
121source "drivers/net/can/sja1000/Kconfig"
122
123source "drivers/net/can/c_can/Kconfig"
124
125source "drivers/net/can/cc770/Kconfig"
126
127source "drivers/net/can/usb/Kconfig"
128
129source "drivers/net/can/softing/Kconfig"
130
131endif
132
130config CAN_DEBUG_DEVICES
131 bool "CAN devices debugging messages"
132 ---help---
133 Say Y here if you want the CAN device drivers to produce a bunch of
134 debug messages to the system log. Select this if you are having
135 a problem with CAN support and want to see more of what is going
136 on.
137
138endmenu
133config CAN_DEBUG_DEVICES
134 bool "CAN devices debugging messages"
135 ---help---
136 Say Y here if you want the CAN device drivers to produce a bunch of
137 debug messages to the system log. Select this if you are having
138 a problem with CAN support and want to see more of what is going
139 on.
140
141endmenu