Home
last modified time | relevance | path

Searched refs:CAN (Results 1 – 65 of 65) sorted by relevance

/linux-4.4.14/net/can/
DKconfig2 # 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
16 If you want CAN support you should say Y here and also to the
19 if CAN
22 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
25 The raw CAN protocol option offers access to the CAN bus via
29 To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
[all …]
/linux-4.4.14/Documentation/networking/
Dcan.txt40 5.3 writing own CAN protocol modules
42 6 CAN network drivers
45 6.3 CAN controller hardware filters
46 6.4 The virtual CAN driver (vcan)
47 6.5 The CAN network device driver interface
49 6.5.2 Setting the CAN bit-timing
50 6.5.3 Starting and stopping the CAN network device
51 6.6 CAN FD (flexible data rate) driver support
52 6.7 supported CAN hardware
63 The socketcan package is an implementation of CAN protocols
[all …]
D00-INDEX44 - documentation on CAN protocol family.
/linux-4.4.14/drivers/net/can/
DKconfig1 menu "CAN Device Drivers"
4 tristate "Virtual Local CAN Interface (vcan)"
7 virtual local CAN interface.
13 tristate "Serial / USB serial CAN Adaptors (slcan)"
16 CAN driver for several 'low cost' CAN interfaces that are attached
20 As only the sending and receiving of CAN frames is implemented, this
21 driver should work with the (serial/USB) CAN hardware from:
28 The slcan driver supports up to 10 CAN netdevices by default which
33 tristate "Platform CAN drivers with Netlink support"
36 Enables the common framework for platform CAN drivers with Netlink
[all …]
/linux-4.4.14/drivers/net/can/usb/
DKconfig1 menu "CAN USB interfaces"
5 tristate "EMS CPC-USB/ARM7 CAN/USB interface"
7 This driver is for the one channel CPC-USB/ARM7 CAN/USB interface
11 tristate "ESD USB/2 CAN/USB interface"
13 This driver supports the CAN-USB/2 interface
19 This driver supports the Geschwister Schneider USB/CAN devices.
25 tristate "Kvaser CAN/USB interface"
27 This driver adds support for Kvaser CAN/USB devices like Kvaser
62 tristate "PEAK PCAN-USB/USB Pro interfaces for CAN 2.0b/CAN-FD"
65 access to the CAN bus, with repect to the CAN 2.0b and/or CAN-FD
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/net/can/
Drcar_can.txt1 Renesas R-Car CAN controller Device Tree Bindings
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.
9 - reg: physical base address and size of the R-Car CAN register map.
11 - clocks: phandles and clock specifiers for 3 CAN clock inputs.
17 - renesas,can-clock-select: R-Car CAN Clock Source Select. Valid values are:
Dmicrochip,mcp251x.txt1 * Microchip MCP251X stand-alone CAN controller device tree bindings
8 - clocks: The clock feeding the CAN controller.
10 - interrupts: Should contain IRQ line for the CAN controller.
13 - vdd-supply: Regulator that powers the CAN controller.
14 - xceiver-supply: Regulator that powers the CAN transceiver.
Dxilinx_can.txt1 Xilinx Axi CAN/Zynq CANPS controller Device Tree Bindings
5 - compatible : Should be "xlnx,zynq-can-1.0" for Zynq CAN
6 controllers and "xlnx,axi-can-1.00.a" for Axi CAN
8 - reg : Physical base address and size of the Axi CAN/Zynq
14 (For CANPS), "can_clk" , "s_axi_aclk"(For AXI CAN)
34 For Axi CAN Dts file:
Datmel-can.txt1 * AT91 CAN *
5 - reg: Should contain CAN controller registers location and length
6 - interrupts: Should contain IRQ line for the CAN controller
Dsun4i_can.txt1 Allwinner A10/A20 CAN controller Device Tree Bindings
6 - reg: physical base address and size of the Allwinner A10/A20 CAN register map.
Dfsl-flexcan.txt1 Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
19 - xceiver-supply: Regulator that powers the CAN transceiver
Dgrcan.txt1 Aeroflex Gaisler GRCAN and GRHCAN CAN controllers.
3 The GRCAN and CRHCAN CAN controllers are available in the GRLIB VHDL IP core
Dmpc5xxx-mscan.txt1 CAN Device Tree Bindings
27 If this property is not present, an optimal CAN
Dcc770.txt1 Memory mapped Bosch CC770 and Intel AN82527 CAN controller
3 Note: The CC770 is a CAN controller from Bosch, which is 100%
Dsja1000.txt1 Memory mapped SJA1000 CAN controller from NXP (formerly Philips)
44 - nxp,no-comparator-bypass : Allows to disable the CAN input comparator.
Dc_can.txt19 register and the CAN instance number (0 offset).
Dm_can.txt14 and CAN clock.
/linux-4.4.14/drivers/net/can/spi/
DKconfig1 menu "CAN SPI interfaces"
5 tristate "Microchip MCP251x SPI CAN controllers"
8 Driver for the Microchip MCP251x SPI CAN controllers.
/linux-4.4.14/drivers/net/can/softing/
DKconfig2 tristate "Softing Gmbh CAN generic support"
5 Support for CAN cards from Softing Gmbh & some cards
7 Softing Gmbh CAN cards come with 1 or 2 physical busses.
19 tristate "Softing Gmbh CAN pcmcia cards"
29 In order to use the card as CAN device, you need the Softing generic
/linux-4.4.14/drivers/net/can/mscan/
DKconfig7 implementation of the Motorola Scalable CAN concept targeted for
13 tristate "Freescale MPC5xxx onboard CAN controller"
17 onboard CAN controller. Currently, the MPC5200, MPC5200B and
/linux-4.4.14/drivers/net/can/sja1000/
DKconfig79 This driver is for CAN interface cards based on
84 - esd CAN-PCI/CPCI/PCI104/200 (http://www.esd.eu/)
85 - esd CAN-PCI/PMC/266
86 - esd CAN-PCIe/2000
87 - Marathon CAN-bus-PCI card (http://www.marathon.ru/)
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-pci-drivers-janz-cmodio6 Value representing the HEX switch S2 of the janz carrier board CMOD-IO or CAN-PCI2
/linux-4.4.14/Documentation/arm/stm32/
Dstm32f429-overview.txt11 - I2C, SPI, SAI, CAN, USB OTG, Ethernet controllers
/linux-4.4.14/arch/sh/kernel/cpu/sh4a/
Dsetup-sh7770.c355 DU, VIDEO_IN, REMOTE, YUV, USB, ATAPI, CAN, GPS, GFX2D, enumerator
389 INTC_VECT(CAN, 0x880), INTC_VECT(GPS, 0x8a0),
436 GPS, CAN, ATAPI, USB, YUV, REMOTE, VIDEO_IN, DU, SRC, I2S,
445 { 0xffe00010, 0, 32, 8, /* INT2PRI4 */ { ATAPI, CAN, GPS, GFX2D } },
/linux-4.4.14/arch/arm/boot/dts/
Dsama5d3_can.dtsi3 * CAN support
Dam335x-wega.dtsi27 /* CAN Busses */
Dimx27-phytec-phycore-rdk.dts213 MX27_PAD_SD1_D1__GPIO5_19 0x0 /* CAN IRQ */
Dimx53-tx53.dtsi93 regulator-name = "CAN XCVR";
Dimx6qdl-tx6.dtsi107 regulator-name = "CAN XCVR";
Dimx6qdl-sabrelite.dtsi90 regulator-name = "CAN XCVR";
Dimx6qdl-nitrogen6x.dtsi91 regulator-name = "CAN XCVR";
Dimx28-tx28.dts94 regulator-name = "CAN XCVR";
Dimx6qdl-nitrogen6_max.dtsi123 regulator-name = "CAN XCVR";
Dr8a7791.dtsi1025 /* External CAN clock */
Dr8a7790.dtsi993 /* External CAN clock */
/linux-4.4.14/arch/blackfin/mach-bf537/
DKconfig17 int "IRQ_ERROR: PPI CAN MAC SPORT0 SPORT1 SPI UART0 UART1"
/linux-4.4.14/arch/powerpc/boot/dts/
Dtqm8560.dts318 2 0x0 0xe3000000 0x00008000 // CAN (2 x i82527)
356 /* Note: CAN support needs be enabled in U-Boot */
Dtqm8548-bigflash.dts350 2 0x0 0xa3000000 0x00008000 // CAN (2 x CC770)
390 /* Note: CAN support needs be enabled in U-Boot */
Dtqm8548.dts350 2 0x0 0xe3000000 0x00008000 // CAN (2 x CC770)
390 /* Note: CAN support needs be enabled in U-Boot */
Dtqm8xx.dts72 /* Note: CAN support needs be enabled in U-Boot */
Dmpc5125twr.dts129 can@1300 { // CAN rev.2
/linux-4.4.14/arch/powerpc/platforms/512x/
Dclock-commonclk.c1058 NODE_CHK("ipg", clks[MPC512x_CLK_BDLC], 0, CAN); in mpc5121_clk_provide_backwards_compat()
1059 NODE_CHK("mclk", clks[MPC512x_CLK_MSCAN0_MCLK + idx], 0, CAN); in mpc5121_clk_provide_backwards_compat()
/linux-4.4.14/net/sched/
DKconfig570 tristate "CAN Identifier"
571 depends on NET_EMATCH && (CAN=y || CAN=m)
573 Say Y here if you want to be able to classify CAN frames based
574 on CAN Identifier.
/linux-4.4.14/Documentation/arm/nwfpe/
DREADME68 PERSONS AND ORGANIZATIONS WHO CAN AND WILL TAKE FULL RESPONSIBILITY FOR ANY
/linux-4.4.14/arch/blackfin/kernel/
Ddebug-mmrs.c120 char buf[32], *_buf = REGS_STR_PFX(buf, CAN, num); in bfin_debug_mmrs_can()
202 #define CAN(num) bfin_debug_mmrs_can(parent, CAN##num##_MC1, num) macro
784 CAN(0); in bfin_debug_mmrs_init()
787 CAN(1); in bfin_debug_mmrs_init()
/linux-4.4.14/arch/m68k/q40/
DREADME92 - 50 or 200 Hz - level 2, !!THIS CAN'T BE DISABLED!!
/linux-4.4.14/Documentation/ioctl/
Dioctl-number.txt282 'z' 00-3F CAN bus card conflict!
284 'z' 40-7F CAN bus card conflict!
/linux-4.4.14/arch/m68k/ifpsp060/
Diskeleton.S189 | SO THAT THE 060SP CAN CREATE A PROPER ACCESS ERROR FRAME.
/linux-4.4.14/arch/m68k/fpsp040/
Dslogn.S347 |--LOG(1+U) CAN BE VERY EFFICIENT.
/linux-4.4.14/arch/arm/nwfpe/
Dsoftfloat-specialize21 PERSONS AND ORGANIZATIONS WHO CAN AND WILL TAKE FULL RESPONSIBILITY FOR ANY
Dsoftfloat-macros21 PERSONS AND ORGANIZATIONS WHO CAN AND WILL TAKE FULL RESPONSIBILITY FOR ANY
/linux-4.4.14/Documentation/serial/
Drocket.txt128 CAN NOT set the second, third or fourth board for address 0x140 since
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmpc5200.txt88 mscan@<addr> fsl,mpc5200-mscan CAN bus controller
/linux-4.4.14/Documentation/ide/
Dide.txt13 *** IMPORTANT NOTICES: BUGGY IDE CHIPSETS CAN CORRUPT DATA!!
/linux-4.4.14/Documentation/scsi/
Daic7xxx.txt190 INCORRECTLY CAN RENDER YOUR SYSTEM INOPERABLE.
Daic79xx.txt215 INCORRECTLY CAN RENDER YOUR SYSTEM INOPERABLE.
/linux-4.4.14/Documentation/development-process/
D6.Followthrough180 6.3: OTHER THINGS THAT CAN HAPPEN
/linux-4.4.14/arch/m68k/ifpsp060/src/
Dilsp.S579 # 'N' CAN be set if the operation is unsigned if bit 63 is set.
Dfplsp.S6265 #--FETCH F AND SAVING OF REGISTERS CAN BE ALL HIDED UNDER THE
6412 #--THIS CAN BE RE-WRITTEN AS
8244 #--LOG(1+U) CAN BE VERY EFFICIENT.
8486 #--TAKEN BECAUSE 1+Z CAN HAVE 67 BITS OF INFORMATION AND WE MUST
Dfpsp.S5183 #--R' = SGN*R, S=R*R. THIS CAN BE REWRITTEN AS
5236 #--S=R*R AND S'=SGN*S. THIS CAN BE REWRITTEN AS
/linux-4.4.14/Documentation/sound/oss/
DREADME.OSS255 THE BIGGEST MISTAKES YOU CAN MAKE
268 IF YOU REALLY ARE 150% SURE YOU HAVE A SOUND BLASTER YOU CAN SKIP THE REST OF
707 * VERSIONS CAN BE INSTALLED FROM A SEPARATELY DISTRIBUTED PACKAGE *
/linux-4.4.14/Documentation/isdn/
DREADME569 CAN be used, however it's possible to use single tty's/interfaces with
/linux-4.4.14/Documentation/
Ddevices.txt1651 91 char CAN-Bus devices
1652 0 = /dev/can0 First CAN-Bus controller
1653 1 = /dev/can1 Second CAN-Bus controller
/linux-4.4.14/drivers/mfd/
DKconfig406 CAN and GPIO controllers.
/linux-4.4.14/
DMAINTAINERS2593 CAN NETWORK LAYER
2609 CAN NETWORK DRIVERS