| /linux-6.15/net/can/ |
| H A D | Kconfig | 6 menuconfig CAN config
7 tristate "CAN bus subsystem support"
21 if CAN
24 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
27 The raw CAN protocol option offers access to the CAN bus via
49 The CAN Gateway/Router is used to route (and modify) CAN frames.
52 CAN frames can be routed between CAN network interfaces (one hop).
59 tristate "ISO 15765-2 CAN transport protocol"
62 communication between CAN nodes via two defined CAN Identifiers.
64 (aka Classical CAN, CAN 2.0B) and CAN FD frame types which were
[all …]
|
| /linux-6.15/Documentation/networking/ |
| H A D | can.rst | 126 CAN-IDs from the same CAN network interface. The SocketCAN core
165 arbitration on the CAN bus the transmission of a low prio CAN-ID
231 The Classical CAN frame structure (aka CAN 2.0B), the CAN FD frame structure
263 the CAN payload. There is no given byteorder on the CAN bus by
354 When the CAN interface is bound to 'any' existing CAN interface
643 and CAN FD frames. OTOH the application has to handle CAN and CAN FD frames
948 Up to 257 CAN frames (multiplex filter bit mask CAN frame plus 256 CAN
1080 frames received by CAN interfaces and to send CAN frames::
1190 CAN interface. A full qualified address on CAN consists of
1192 - a unique CAN Identifier (CAN ID)
[all …]
|
| H A D | iso15765-2.rst | 11 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
40 * "normal" : each address is represented simply by a CAN ID.
43 the CAN payload; both the CAN ID and the byte inside the payload shall be
47 the CAN payload; the CAN ID is different between two addresses, but the
71 Linux network subsystem for the CAN bus, aka. Linux-CAN or SocketCAN, and
87 bind the socket to the desired CAN interface; to do so:
103 of the data payload exceeds the MTU of the underlying CAN bus).
125 * ``can_addr.tp.tx_id`` specifies the transmit (TX) CAN ID
276 for classical CAN frames or ``CANFD_MTU`` for CAN FD frames.
[all …]
|
| H A 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
82 Bring the CAN interface up.
96 Stop the CAN interface
106 Reset the CAN controller (including error counters)
226 Data received from the CAN bus (ID + payload).
234 The CAN device has sent a message to the CAN bus. It answers with a
288 Transmit a CAN frame. (parameters: ``id``, ``data``)
[all …]
|
| /linux-6.15/drivers/net/can/ |
| H A D | Kconfig | 4 tristate "CAN Device Drivers"
6 depends on CAN
11 (CAN-FD). The CAN bus was originally mainly for automotive, but is now
29 virtual local CAN interface.
35 tristate "Virtual CAN Tunnel (vxcan)"
38 local CAN traffic tunnel between two virtual CAN network devices.
70 bool "CAN bit-timing calculation"
104 extended CAN Controller (bxCAN).
178 CAN driver for several 'low cost' CAN interfaces that are attached
212 tristate "Xilinx CAN"
[all …]
|
| /linux-6.15/drivers/net/can/usb/ |
| H A D | Kconfig | 2 menu "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"
68 tristate "Kvaser CAN/USB interface"
106 - Kvaser Hybrid CAN/LIN
108 - Kvaser Hybrid Pro CAN/LIN
137 tristate "PEAK PCAN-USB/USB Pro interfaces for CAN 2.0b/CAN-FD"
140 access to the CAN bus, with respect to the CAN 2.0b and/or CAN-FD
[all …]
|
| /linux-6.15/Documentation/userspace-api/media/rc/ |
| H A D | lirc-get-features.rst | 41 .. _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:
98 .. _LIRC-CAN-SET-REC-CARRIER:
140 .. _LIRC-CAN-SEND-RAW:
146 .. _LIRC-CAN-SEND-PULSE:
156 .. _LIRC-CAN-SEND-MODE2:
[all …]
|
| /linux-6.15/drivers/net/can/peak_canfd/ |
| H A 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-6.15/drivers/net/can/spi/ |
| H A D | Kconfig | 2 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-6.15/Documentation/devicetree/bindings/net/can/ |
| H A D | xilinx,can.yaml | 8 Xilinx CAN and CANFD controller
39 description: CAN Tx fifo depth (Zynq, Axi CAN).
43 description: CAN Rx fifo depth (Zynq, Axi CAN, CAN FD in sequential Rx mode)
47 description: CAN Tx mailbox buffer count (CAN FD)
54 description: CAN TX_OL, TX_TL and RX FIFOs have ECC support(AXI CAN)
|
| H A 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.
|
| H A D | st,stm32-bxcan.yaml | 9 description: STMicroelectronics BxCAN controller for CAN bus
25 two CAN peripherals in dual CAN configuration. In that case they share
27 Not to be used if the peripheral is in single CAN configuration.
35 has two CAN peripherals in dual CAN configuration. In that case they
37 Not to be used if the peripheral is in single CAN configuration.
70 secondary) in dual CAN peripheral configuration.
|
| H A D | can-transceiver.yaml | 7 title: CAN transceiver
9 description: CAN transceiver generic properties bindings
17 description: a positive non 0 value that determines the max speed that CAN/CAN-FD can run.
|
| H A D | fsl,flexcan.yaml | 8 Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
82 description: Regulator that powers the CAN transceiver.
106 req_gpr is the gpr register offset of CAN stop request.
107 req_bit is the bit offset of CAN stop request.
112 - description: The 'req_gpr' is the gpr register offset of CAN stop request.
114 - description: The 'req_bit' is the bit offset of CAN stop request.
119 Select the clock source to the CAN Protocol Engine (PE). It's SoC
133 Enable CAN remote wakeup.
137 The scu index of CAN instance.
139 property can help indicate a resource. It supports up to 3 CAN instances
|
| H A D | renesas,rcar-canfd.yaml | 7 title: Renesas R-Car CAN FD Controller
67 The controller can operate in either CAN FD only mode (default) or
68 Classical CAN only mode. The mode is global to all channels.
69 Specify this property to put the controller in Classical CAN only mode.
74 used by both CAN (if present) and CAN FD controllers at the same time.
121 - description: CAN global error interrupt
122 - description: CAN receive FIFO interrupt
|
| H A D | can-controller.yaml | 7 title: CAN Controller Common Properties
17 description: GPIO pin to enable CAN bus termination.
21 description: The resistance value of the CAN bus termination resistor.
|
| /linux-6.15/drivers/net/can/rcar/ |
| H A D | Kconfig | 3 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-6.15/drivers/net/can/ctucanfd/ |
| H A D | Kconfig | 2 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-6.15/Documentation/networking/device_drivers/can/ |
| H A D | can327.rst | 17 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,
165 with (11 bit) CAN ID ``0x123``.
174 of CAN ID, DLC, and data::
207 "``AT CSM``" (CAN Silent Monitoring, i.e. don't send CAN ACKs) is
243 command, and the "listen-only" CAN option will take effect.
288 - No use of hardware CAN ID filtering
[all …]
|
| /linux-6.15/drivers/net/can/softing/ |
| H A 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 buses.
20 tristate "Softing Gmbh CAN pcmcia cards"
30 In order to use the card as CAN device, you need the Softing generic
|
| /linux-6.15/drivers/net/can/sja1000/ |
| H A 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-6.15/Documentation/networking/device_drivers/can/ctu/ |
| H A D | ctucanfd-driver.rst | 3 CTU CAN FD Driver
9 About CTU CAN FD IP Core
32 for CAN FD buses, host connection and CTU CAN FD core emulation. The development
260 CTU CAN FD Driver design
265 CAN FD core driver in particular.
340 An incoming frame may be either a CAN 2.0 frame or a CAN FD frame. The
357 the smaller CAN 2.0 frame.
471 whether this functionality will be practical for CAN.
520 CTU CAN FD Driver Sources Reference
549 …* uses project in their CAN/CAN FD diagnostics framework for `Skoda Auto <https://www.skoda-auto.c…
[all …]
|
| /linux-6.15/Documentation/networking/device_drivers/can/freescale/ |
| H A D | flexcan.rst | 4 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-6.15/drivers/net/can/mscan/ |
| H A 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
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | sysfs-class-net-peak_usb | 7 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
|