Searched refs:CAN (Results 1 – 25 of 97) sorted by relevance
1234
| /Linux-v5.4/net/can/ |
| D | Kconfig | 3 # Controller Area Network (CAN) network layer core configuration
6 menuconfig CAN config
8 tristate "CAN bus subsystem support"
10 Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
11 communications protocol. Development of the CAN bus started in
13 released in 1986. The CAN bus was originally mainly for automotive,
15 applications. More information on the CAN network protocol family
18 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-v5.4/Documentation/networking/ |
| D | can.rst | 8 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 …]
|
| D | can_ucan_protocol.rst | 5 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 …]
|
| /Linux-v5.4/drivers/net/can/ |
| D | Kconfig | 2 menu "CAN Device Drivers"
5 tristate "Virtual Local CAN Interface (vcan)"
8 virtual local CAN interface.
14 tristate "Virtual CAN Tunnel (vxcan)"
17 local CAN traffic tunnel between two virtual CAN network devices.
22 In opposite to vcan loopback devices the vxcan only forwards CAN
24 CAN frames. To disable a potential echo in af_can.c the vxcan driver
26 in each namespace the CAN GW hop counter is set to zero.
32 tristate "Serial / USB serial CAN Adaptors (slcan)"
35 CAN driver for several 'low cost' CAN interfaces that are attached
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/can/ |
| D | rcar_can.txt | 1 Renesas R-Car CAN controller Device Tree Bindings
5 - compatible: "renesas,can-r8a7743" if CAN controller is a part of R8A7743 SoC.
6 "renesas,can-r8a7744" if CAN controller is a part of R8A7744 SoC.
7 "renesas,can-r8a7745" if CAN controller is a part of R8A7745 SoC.
8 "renesas,can-r8a77470" if CAN controller is a part of R8A77470 SoC.
9 "renesas,can-r8a774a1" if CAN controller is a part of R8A774A1 SoC.
10 "renesas,can-r8a774c0" if CAN controller is a part of R8A774C0 SoC.
11 "renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC.
12 "renesas,can-r8a7779" if CAN controller is a part of R8A7779 SoC.
13 "renesas,can-r8a7790" if CAN controller is a part of R8A7790 SoC.
[all …]
|
| D | xilinx_can.txt | 1 Xilinx Axi CAN/Zynq CANPS controller Device Tree Bindings
6 - "xlnx,zynq-can-1.0" for Zynq CAN controllers
7 - "xlnx,axi-can-1.00.a" for Axi CAN controllers
8 - "xlnx,canfd-1.0" for CAN FD controllers
9 - "xlnx,canfd-2.0" for CAN FD 2.0 controllers
16 - "can_clk", "s_axi_aclk" (For AXI CAN and CAN FD).
19 - tx-fifo-depth : Can Tx fifo depth (Zynq, Axi CAN).
20 - rx-fifo-depth : Can Rx fifo depth (Zynq, Axi CAN, CAN FD in
22 - tx-mailbox-count : Can Tx mailbox buffer count (CAN FD).
23 - rx-mailbox-count : Can Rx mailbox buffer count (CAN FD in mailbox Rx
[all …]
|
| D | can-transceiver.txt | 1 Generic CAN transceiver Device Tree binding
4 CAN transceiver typically limits the max speed in standard CAN and CAN FD
11 speed that CAN/CAN-FD can run. Any other value
16 Based on Texas Instrument's TCAN1042HGV CAN Transceiver
|
| D | holt_hi311x.txt | 1 * 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.
|
| D | fsl-flexcan.txt | 1 Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
19 - xceiver-supply: Regulator that powers the CAN transceiver
30 req_gpr is the gpr register offset of CAN stop request.
31 req_bit is the bit offset of CAN stop request.
32 ack_gpr is the gpr register offset of CAN stop acknowledge.
33 ack_bit is the bit offset of CAN stop acknowledge.
35 - fsl,clk-source: Select the clock source to the CAN Protocol Engine (PE).
42 - wakeup-source: enable CAN remote wakeup
|
| D | microchip,mcp251x.txt | 1 * Microchip MCP251X stand-alone CAN controller device tree bindings
9 - 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.
|
| D | atmel-can.txt | 1 * AT91 CAN *
5 - reg: Should contain CAN controller registers location and length
6 - interrupts: Should contain IRQ line for the CAN controller
|
| D | rcar_canfd.txt | 1 Renesas R-Car CAN FD controller Device Tree Bindings
21 - reg: physical base address and size of the R-Car CAN FD register map.
36 In the denoted SoCs, canfd clock is a div6 clock and can be used by both CAN
37 and CAN FD controller at the same time. It needs to be scaled to maximum
45 The controller can operate in either CAN FD only mode (default) or
46 Classical CAN only mode. The mode is global to both the channels. In order to
48 - renesas,no-can-fd: puts the controller in Classical CAN only mode.
81 E.g. below enables Channel 1 alone in the board in Classical CAN only mode.
|
| D | ifi_canfd.txt | 6 - reg: Should contain CAN controller registers location and length
7 - interrupts: Should contain IRQ line for the CAN controller
|
| D | sun4i_can.txt | 1 Allwinner A10/A20 CAN controller Device Tree Bindings
6 - reg: physical base address and size of the Allwinner A10/A20 CAN register map.
|
| D | ti_hecc.txt | 1 Texas Instruments High End CAN Controller (HECC)
19 - xceiver-supply: regulator that powers the CAN transceiver
|
| D | grcan.txt | 1 Aeroflex Gaisler GRCAN and GRHCAN CAN controllers.
3 The GRCAN and CRHCAN CAN controllers are available in the GRLIB VHDL IP core
|
| D | m_can.txt | 14 and CAN clock.
48 that can be used for CAN/CAN-FD modes. See
|
| /Linux-v5.4/drivers/net/can/usb/ |
| D | Kconfig | 2 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 USB/2 CAN/USB interface"
20 This driver supports the CAN-USB/2 interface
27 candleLight USB CAN interfaces USB/CAN devices
33 tristate "Kvaser CAN/USB interface"
35 This driver adds support for Kvaser CAN/USB devices like Kvaser
84 tristate "Microchip CAN BUS Analyzer interface"
86 This driver supports the CAN BUS Analyzer interface
[all …]
|
| /Linux-v5.4/Documentation/media/uapi/rc/ |
| D | lirc-get-features.rst | 48 .. _LIRC-CAN-REC-RAW:
54 .. _LIRC-CAN-REC-PULSE:
61 .. _LIRC-CAN-REC-MODE2:
71 .. _LIRC-CAN-REC-LIRCCODE:
77 .. _LIRC-CAN-REC-SCANCODE:
84 .. _LIRC-CAN-SET-SEND-CARRIER:
91 .. _LIRC-CAN-SET-SEND-DUTY-CYCLE:
98 .. _LIRC-CAN-SET-TRANSMITTER-MASK:
105 .. _LIRC-CAN-SET-REC-CARRIER:
112 .. _LIRC-CAN-SET-REC-DUTY-CYCLE-RANGE:
[all …]
|
| /Linux-v5.4/drivers/net/can/peak_canfd/ |
| D | Kconfig | 7 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-v5.4/drivers/net/can/spi/ |
| D | Kconfig | 2 menu "CAN SPI interfaces"
6 tristate "Holt HI311x SPI CAN controllers"
9 Driver for the Holt HI311x SPI CAN controllers.
12 tristate "Microchip MCP251x and MCP25625 SPI CAN controllers"
15 Driver for the Microchip MCP251x and MCP25625 SPI CAN
|
| /Linux-v5.4/drivers/net/can/rcar/ |
| D | Kconfig | 3 tristate "Renesas R-Car 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-v5.4/drivers/net/can/softing/ |
| D | Kconfig | 3 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 busses.
20 tristate "Softing Gmbh CAN pcmcia cards"
30 In order to use the card as CAN device, you need the Softing generic
|
| /Linux-v5.4/drivers/net/can/sja1000/ |
| D | Kconfig | 25 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-v5.4/drivers/net/can/mscan/ |
| D | Kconfig | 8 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
|
1234
