Lines Matching refs:can
3 can.txt
38 5.1 can.ko module params
98 controller can be passed up to the network layer and on to the CAN
101 that any number of transport protocols can be loaded or unloaded
102 dynamically. In fact, the can core module alone does not provide any
104 protocol module. Multiple sockets can be opened at the same time,
105 on different or the same protocol module and they can listen/send
110 selects that protocol when opening the socket, and then can read and
165 For this reason a CAN-ID can be treated best as a kind of source address.
177 CAN-IDs can be done for specific CAN interfaces or for all(!) known
202 The Linux network devices (by default) just can handle the
209 some reason the SocketCAN core can do this task as a fallback solution.
229 reason the CAN interface driver can generate so called Error Message
230 Frames that can optionally be passed to the user application in the
233 creates an appropriate error message frame. Error messages frames can
238 described in the Linux header file "include/uapi/linux/can/error.h".
260 the socket, you can read(2) and write(2) from/to the socket or use
266 in include/linux/can.h:
328 perror("can raw socket read");
340 Writing CAN frames can be done similarly, with the write(2) system call:
384 The struct canfd_frame is defined in include/linux/can.h:
399 all structure elements can be used as-is - only the data[] becomes extended.
412 definitions are specified for CAN specific MTUs in include/linux/can.h :
431 sockets, include <linux/can/raw.h>.
435 The reception of CAN frames using CAN_RAW sockets can be controlled
438 The CAN filter structure is defined in include/linux/can.h:
450 The filter can be inverted in this semantic, when the CAN_INV_FILTER
494 both SFF frames with CAN ID 0x123 and EFF frames with 0xXXXXX123 can pass.
510 As described in chapter 3.4 the CAN interface driver can generate so
511 called Error Message Frames that can optionally be passed to the user
515 error condition CAN_ERR_MASK can be used as value for the error mask.
516 The values for the error mask are defined in linux/can/error.h .
528 functionality can be disabled (separately for each socket):
551 CAN FD support in CAN_RAW sockets can be enabled with a new socket option
556 Once CAN_RAW_FD_FRAMES is enabled the application can send both CAN frames
581 /* the content can be handled independently from the received MTU size */
599 or CAN FD frames and can process them the same way.
603 The CAN device MTU can be retrieved e.g. with a SIOCGIFMTU ioctl() syscall.
607 The CAN_RAW socket can set multiple CAN identifier specific filters that
627 This flag can be interpreted as a 'transmission confirmation' when the
636 Receive filters can be used to down sample frequent messages; detect events
640 Periodic transmission tasks of CAN frames or a sequence of CAN frames can be
642 possible transmit intervals can be altered.
648 defined in the linux/can/bcm.h include. The BCM message consists of a
663 at the beginning of section 4 and in the include/linux/can.h include. All
774 The timer values can be altered at runtime when only SET_TIMER is set.
778 Up to 256 CAN frames can be transmitted in a sequence in the case of a cyclic
815 than one CAN frames can be passed in a RX_SETUP configuration message. The
821 filters) can be added as array to the TX_SETUP BCM configuration message.
855 5.1 can.ko module params
859 invoked at can.ko module start time by default. This timer can be
868 receive lists, their filters and the count of filter matches can be
872 foo@bar:~$ cat /proc/net/can/rcvlist_all
891 Additional procfs files in /proc/net/can
900 protocol has to be defined in include/linux/can.h .
901 The prototypes and definitions to use the SocketCAN core can be
902 accessed by including include/linux/can/core.h .
911 For details see the kerneldoc documentation in net/can/af_can.c or
912 the source code of net/can/raw.c or net/can/bcm.c .
983 removal of vcan network devices can be managed with the ip(8) tool:
997 to setup, configure and monitor CAN network devices. The user can then
1004 understand how to use them. The name of the module is can-dev.ko.
1010 "include/linux/can/netlink.h". CAN link support for the program "ip"
1011 of the IPROUTE2 utility suite is available and it can be used as shown
1016 $ ip link set can0 type can help
1017 Usage: ip link set DEVICE type can
1042 link/can
1043 can <TRIPLE-SAMPLING> state ERROR-ACTIVE restart-ms 100
1075 bit-timing can be defined by setting the "bitrate" argument.
1076 Optionally the "sample-point" can be specified. By default it's
1103 The CAN bit-timing parameters can always be defined in a hardware
1108 $ ip link set canX type can tq 125 prop-seg 6 \
1115 $ ip link set canX type can bitrate 125000
1122 constants can be used for that purpose. They are listed by the
1134 before you can start it to avoid error-prone default settings:
1136 $ ip link set canX up type can bitrate 125000
1140 bus-off recovery can be enabled by setting the "restart-ms" to a
1143 $ ip link set canX type can restart-ms 100
1149 $ ip link set canX type can restart
1169 The CAN netdevice driver capabilities can be distinguished by the network
1175 The CAN device MTU can be retrieved e.g. with a SIOCGIFMTU ioctl() syscall.
1176 N.B. CAN FD capable devices can also handle and send legacy CAN frames.
1182 Please check the "Kconfig" file in "drivers/net/can" to get an actual