Home
last modified time | relevance | path

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

12345678910>>...24

/linux/net/can/
A DKconfig6 menuconfig CAN config
7 tristate "CAN bus subsystem support"
20 if CAN
23 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
26 The raw CAN protocol option offers access to the CAN bus via
48 The CAN Gateway/Router is used to route (and modify) CAN frames.
51 CAN frames can be routed between CAN network interfaces (one hop).
58 tristate "ISO 15765-2:2016 CAN transport protocol"
61 communication between CAN nodes via two defined CAN Identifiers.
63 (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
[all …]
/linux/Documentation/networking/
A Dcan.rst126 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
625 and CAN FD frames. OTOH the application has to handle CAN and CAN FD frames
946 Up to 257 CAN frames (multiplex filter bit mask CAN frame plus 256 CAN
1078 frames received by CAN interfaces and to send CAN frames::
1155 CAN interface. A full qualified address on CAN consists of
1157 - a unique CAN Identifier (CAN ID)
[all …]
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
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 …]
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.
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
171 On CAN, you first need to open a socket for communicating over a CAN network.
181 packets to the other end (using several CAN packets). ``SOCK_STREAM`` is not
[all …]
/linux/drivers/net/can/
A DKconfig2 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.
35 CAN driver for several 'low cost' CAN interfaces that are attached
62 bool "CAN bit-timing calculation"
150 tristate "TI High End CAN Controller"
156 tristate "Xilinx CAN"
160 Xilinx CAN driver. This driver supports both soft AXI CAN IP and
[all …]
/linux/drivers/net/can/usb/
A DKconfig2 menu "CAN USB interfaces"
12 tristate "EMS CPC-USB/ARM7 CAN/USB interface"
18 tristate "ESD USB/2 CAN/USB interface"
24 tristate "ETAS ES58X CAN/USB interfaces"
37 candleLight USB CAN interfaces USB/CAN devices
43 tristate "Kvaser CAN/USB interface"
79 - Kvaser Hybrid CAN/LIN
81 - Kvaser Hybrid Pro CAN/LIN
108 tristate "PEAK PCAN-USB/USB Pro interfaces for CAN 2.0b/CAN-FD"
111 access to the CAN bus, with respect to the CAN 2.0b and/or CAN-FD
[all …]
/linux/Documentation/devicetree/bindings/net/can/
A Dxilinx_can.txt1 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).
40 For Axi CAN Dts file:
[all …]
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.
A Dmicrochip,mcp251x.txt1 * 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.
A Dfsl,flexcan.yaml8 Flexcan CAN controller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
66 description: Regulator that powers the CAN transceiver.
83 req_gpr is the gpr register offset of CAN stop request.
84 req_bit is the bit offset of CAN stop request.
89 - description: The 'req_gpr' is the gpr register offset of CAN stop request.
91 - description: The 'req_bit' is the bit offset of CAN stop request.
96 Select the clock source to the CAN Protocol Engine (PE). It's SoC
110 Enable CAN remote wakeup.
114 The scu index of CAN instance.
116 property can help indicate a resource. It supports up to 3 CAN instances
A Dcan-transceiver.yaml7 title: CAN transceiver Bindings
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.
A Drenesas,rcar-canfd.yaml7 title: Renesas R-Car CAN FD Controller
60 The controller can operate in either CAN FD only mode (default) or
61 Classical CAN only mode. The mode is global to both the channels.
62 Specify this property to put the controller in Classical CAN only mode.
67 used by both CAN (if present) and CAN FD controllers at the same time.
105 - description: CAN global error interrupt
106 - description: CAN receive FIFO interrupt
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
A Dcan-controller.yaml7 title: CAN Controller Generic Binding
17 description: GPIO pin to enable CAN bus termination.
21 description: The resistance value of the CAN bus termination resistor.
A Dbosch,c_can.yaml9 description: Bosch C_CAN/D_CAN controller for CAN bus
46 CAN functional clock phandle.
55 register offset to the RAMINIT register and the CAN instance number (0
62 - description: The CAN instance number.
A Dmicrochip,mcp251xfd.yaml8 Microchip MCP2517FD and MCP2518FD stand-alone CAN controller device tree
34 description: Regulator that powers the CAN controller.
37 description: Regulator that powers the CAN transceiver.
A Difi_canfd.txt6 - reg: Should contain CAN controller registers location and length
7 - interrupts: Should contain IRQ line for the CAN controller
/linux/Documentation/userspace-api/media/rc/
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:
132 .. _LIRC-CAN-SET-REC-FILTER:
152 .. _LIRC-CAN-NOTIFY-DECODE:
158 .. _LIRC-CAN-SEND-RAW:
164 .. _LIRC-CAN-SEND-PULSE:
174 .. _LIRC-CAN-SEND-MODE2:
[all …]
/linux/drivers/net/can/peak_canfd/
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/
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/
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/drivers/net/can/sja1000/
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/drivers/net/can/softing/
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/arch/arm/boot/dts/
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/mscan/
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

Completed in 36 milliseconds

12345678910>>...24