Home
last modified time | relevance | path

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

12345

/linux/net/can/
H A DKconfig3 # Controller Area Network (CAN) network layer core configuration
6 menuconfig CAN config
7 tristate "CAN bus subsystem support"
9 Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
10 communications protocol. Development of the CAN bus started in
12 released in 1986. The CAN bus was originally mainly for automotive,
14 applications. More information on the CAN network protocol family
17 If you want CAN support you should say Y here and also to the
21 if CAN
24 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
[all …]
/linux/Documentation/networking/
H A Dcan.rst8 The socketcan package is an implementation of CAN protocols
9 (Controller Area Network) for Linux. CAN is a networking technology
11 automotive fields. While there have been other CAN implementations
13 socket API, the Linux network stack and implements the CAN device
14 drivers as network interfaces. The CAN socket API has been designed
16 familiar with network programming, to easily learn how to use CAN
25 There have been CAN implementations for Linux before SocketCAN so the
27 implementations come as a device driver for some CAN hardware, they
31 receive raw CAN frames, directly to/from the controller hardware.
36 the CAN controller requires employment of another device driver and
[all …]
H A Diso15765-2.rst11 for diagnostic communication on CAN. It is widely used in the automotive
15 ISO-TP can be used both on CAN CC (aka Classical CAN) and CAN FD (CAN with
17 CAN network using SAE J1939 as data link layer (however, this is not a
40 * "normal" : each address is represented simply by a CAN ID.
42 * "extended": each address is represented by a CAN ID plus the first byte of
43 the CAN payload; both the CAN ID and the byte inside the payload shall be
46 * "mixed": each address is represented by a CAN ID plus the first byte of
47 the CAN payload; the CAN ID is different between two addresses, but the
54 inside one single CAN message or not, also considering the overhead the protocol
60 data block (``blocksize``) and the minimum time between the single CAN messages
[all …]
H A Dcan_ucan_protocol.rst5 UCAN is the protocol used by the microcontroller-based USB-CAN
10 It is modeled closely after how Linux represents CAN devices
25 The device sends CAN data frames and CAN error frames
28 The driver sends CAN data frames on the out endpoint
36 To support multiple CAN interfaces in a single USB device all
82 Bring the CAN interface up.
96 Stop the CAN interface
106 Reset the CAN controller (including error counters)
166 Setup hardware CAN filters. Not yet supported by the driver.
226 Data received from the CAN bus (ID + payload).
[all …]
H A Dj1939.rst10 SAE J1939 defines a higher layer protocol on CAN. It implements a more
59 The J1939 sockets operate on CAN network devices (see SocketCAN). Any J1939
60 user space library operating on CAN raw sockets will still operate properly.
72 The J1939 protocol uses the 29-bit CAN identifier with the following structure:
75 29 bit CAN-ID
77 Bit positions within the CAN-ID
90 Bit positions within the CAN-ID
105 Bit positions within the CAN-ID
115 Bit positions within the CAN-ID
128 Regarding PGN mapping to 29-bit CAN identifier, the Destination Address shall
[all …]
/linux/drivers/net/can/
H A DKconfig4 tristate "CAN Device Drivers"
6 depends on CAN
8 Controller Area Network (CAN) is serial communications protocol up to
9 1Mbit/s for its original release (now known as Classical CAN) and up
10 to 8Mbit/s for the more recent CAN with Flexible Data-Rate
11 (CAN-FD). The CAN bus was originally mainly for automotive, but is now
13 applications. More information on the CAN network protocol family
16 This section contains all the CAN(-FD) device drivers including the
17 virtual ones. If you own such devices or plan to use the virtual CAN
26 tristate "Virtual Local CAN Interface (vcan)"
[all …]
/linux/drivers/net/can/usb/
H A DKconfig2 menu "CAN USB interfaces"
12 tristate "EMS CPC-USB/ARM7 CAN/USB interface"
14 This driver is for the one channel CPC-USB/ARM7 CAN/USB interface
18 tristate "esd electronics gmbh CAN/USB interfaces"
20 This driver adds support for several CAN/USB interfaces
24 - esd CAN-USB/2
25 - esd CAN-USB/3-FD
26 - esd CAN-USB/Micro
32 tristate "ETAS ES58X CAN/USB interfaces"
43 tristate "Fintek F81604 USB to 2CAN interface"
[all …]
/linux/Documentation/userspace-api/media/rc/
H A Dlirc-get-features.rst41 .. _LIRC-CAN-REC-RAW:
47 .. _LIRC-CAN-REC-PULSE:
54 .. _LIRC-CAN-REC-MODE2:
64 .. _LIRC-CAN-REC-LIRCCODE:
70 .. _LIRC-CAN-REC-SCANCODE:
77 .. _LIRC-CAN-SET-SEND-CARRIER:
84 .. _LIRC-CAN-SET-SEND-DUTY-CYCLE:
91 .. _LIRC-CAN-SET-TRANSMITTER-MASK:
98 .. _LIRC-CAN-SET-REC-CARRIER:
105 .. _LIRC-CAN-SET-REC-CARRIER-RANGE:
[all …]
/linux/drivers/net/can/peak_canfd/
H A DKconfig7 CAN-FD cards family.
8 These 1x or 2x CAN-FD channels cards offer CAN 2.0 a/b as well as
9 CAN-FD access to the CAN bus. Besides the nominal bitrate of up to
10 1 Mbit/s, the data bytes of CAN-FD frames can be transmitted with
11 up to 12 Mbit/s. A galvanic isolation of the CAN ports protects the
/linux/drivers/net/can/rcar/
H A DKconfig3 tristate "Renesas R-Car and RZ/G CAN controller"
6 Say Y here if you want to use CAN controller found on Renesas R-Car
13 tristate "Renesas R-Car CAN FD controller"
16 Say Y here if you want to use CAN FD controller found on
17 Renesas R-Car SoCs. The driver puts the controller in CAN FD only
19 dedicated CAN 2.0 mode.
/linux/drivers/net/can/spi/
H A DKconfig2 menu "CAN SPI interfaces"
6 tristate "Holt HI311x SPI CAN controllers"
8 Driver for the Holt HI311x SPI CAN controllers.
11 tristate "Microchip MCP251x and MCP25625 SPI CAN controllers"
13 Driver for the Microchip MCP251x and MCP25625 SPI CAN
/linux/Documentation/devicetree/bindings/net/can/
H A Dholt_hi311x.txt1 * Holt HI-311X stand-alone CAN controller device tree bindings
7 - clocks: The clock feeding the CAN controller.
8 - interrupts: Should contain IRQ line for the CAN controller.
11 - vdd-supply: Regulator that powers the CAN controller.
12 - xceiver-supply: Regulator that powers the CAN transceiver.
H A Datmel-can.txt1 * AT91 CAN *
6 - reg: Should contain CAN controller registers location and length
7 - interrupts: Should contain IRQ line for the CAN controller
H A Difi_canfd.txt6 - reg: Should contain CAN controller registers location and length
7 - interrupts: Should contain IRQ line for the CAN controller
/linux/drivers/net/can/ctucanfd/
H A DKconfig2 tristate "CTU CAN-FD IP core" if COMPILE_TEST
4 This driver adds support for the CTU CAN FD open-source IP core.
12 Guidepost CTU FEE CAN bus projects page https://canbus.pages.fel.cvut.cz/ .
15 tristate "CTU CAN-FD IP core PCI/PCIe driver"
19 This driver adds PCI/PCIe support for CTU CAN-FD IP core.
25 tristate "CTU CAN-FD IP core platform (FPGA, SoC) driver"
30 modified to be CAN FD frames tolerant on MicroZed Zynq based
/linux/Documentation/networking/device_drivers/can/
H A Dcan327.rst17 working with CAN buses.
19 CAN adapters are expensive, few, and far between.
21 Let's use ELM327s as CAN adapters.
29 into full fledged (as far as possible) CAN interfaces.
31 Since the ELM327 was never meant to be a stand alone CAN controller,
80 Once the ldisc is attached, the CAN interface starts out unconfigured.
154 When a CAN frame is to be sent, the target address is configured, after
165 with (11 bit) CAN ID ``0x123``.
173 the ELM327 will send one line for each received CAN frame, consisting
174 of CAN ID, DLC, and data::
[all …]
H A Dindex.rst3 Controller Area Network (CAN) Device Drivers
6 Device drivers for CAN devices.
/linux/drivers/net/can/sja1000/
H A DKconfig25 tristate "Fintek F81601 PCIE to 2 CAN Controller"
28 This driver adds support for Fintek F81601 PCIE to 2 CAN
74 This driver is for CAN interface cards based on
79 - esd CAN-PCI/CPCI/PCI104/200 (http://www.esd.eu/)
80 - esd CAN-PCI/PMC/266
81 - esd CAN-PCIe/2000
82 - Marathon CAN-bus-PCI card (http://www.marathon.ru/)
86 - ASEM CAN raw - 2 isolated CAN channels (www.asem.it)
/linux/Documentation/networking/device_drivers/can/ctu/
H A Dctucanfd-driver.rst3 CTU CAN FD Driver
9 About CTU CAN FD IP Core
12 `CTU CAN FD <https://gitlab.fel.cvut.cz/canbus/ctucanfd_ip_core>`_
30 The basic functional model of the CTU CAN FD peripheral has been
31 accepted into QEMU mainline. See QEMU `CAN emulation support <https://www.qemu.org/docs/master/syst…
32 for CAN FD buses, host connection and CTU CAN FD core emulation. The development
40 SocketCAN is a standard common interface for CAN devices in the Linux
45 natural way to implement and work with higher layer protocols over CAN,
51 Before going into detail about the structure of a CAN bus device driver,
101 discovery and set up, and platform-independent CAN network device
[all …]
/linux/drivers/net/can/softing/
H A DKconfig3 tristate "Softing Gmbh CAN generic support"
6 Support for CAN cards from Softing Gmbh & some cards
8 Softing Gmbh CAN cards come with 1 or 2 physical buses.
20 tristate "Softing Gmbh CAN pcmcia cards"
30 In order to use the card as CAN device, you need the Softing generic
/linux/Documentation/networking/device_drivers/can/freescale/
H A Dflexcan.rst4 Flexcan CAN Controller driver
22 The RX FIFO mode uses a hardware FIFO with a depth of 6 CAN frames,
24 CAN frames. With the help of the bigger buffer, the mailbox mode
27 As reception of RTR frames is part of the CAN standard, all flexcan
37 The CAN controller can and will receive RTR frames.
/linux/drivers/net/can/mscan/
H A DKconfig8 implementation of the Motorola Scalable CAN concept targeted for
14 tristate "Freescale MPC5xxx onboard CAN controller"
18 onboard CAN controller. Currently, the MPC5200, MPC5200B and
/linux/Documentation/ABI/testing/
H A Dsysfs-class-net-peak_usb7 PEAK PCAN-USB devices support user-configurable CAN channel
9 are writable and can be set per CAN interface. This means that
10 if a USB device exports multiple CAN interfaces, each of them
/linux/arch/arm/boot/dts/ti/omap/
H A Dam335x-netcan-plus-1xx.dts42 AM33XX_PADCONF(AM335X_PIN_UART1_RXD, PIN_OUTPUT_PULLDOWN, MUX_MODE7) /* CAN Data LED */
43 AM33XX_PADCONF(AM335X_PIN_UART1_TXD, PIN_OUTPUT_PULLDOWN, MUX_MODE7) /* CAN Error LED */
49 AM33XX_PADCONF(AM335X_PIN_UART0_CTSN, PIN_OUTPUT, MUX_MODE2) /* CAN TX */
50 AM33XX_PADCONF(AM335X_PIN_UART0_RTSN, PIN_INPUT, MUX_MODE2) /* CAN RX */
/linux/drivers/net/can/rockchip/
H A DKconfig4 tristate "Rockchip CAN-FD controller"
8 Say Y here if you want to use CAN-FD controller found on

12345