| /linux/drivers/net/can/ |
| H A D | Kconfig | 4 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
14 PF_CAN is contained in <Documentation/networking/can.rst>.
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
[all …]
|
| H A D | dummy_can.c | 14 #include <linux/can.h>
15 #include <linux/can/bittiming.h>
16 #include <linux/can/dev.h>
17 #include <linux/can/skb.h>
20 struct can_priv can; member
120 struct can_priv *can_priv = &priv->can; in dummy_can_print_ctrlmode()
142 struct can_priv *can_priv = &priv->can; in dummy_can_print_bittiming_info()
152 netdev_dbg(dev, "Classical CAN nominal bittiming:\n"); in dummy_can_print_bittiming_info()
157 netdev_dbg(dev, "CAN FD databittiming:\n"); in dummy_can_print_bittiming_info()
167 netdev_dbg(dev, "CAN XL databittiming:\n"); in dummy_can_print_bittiming_info()
[all …]
|
| /linux/Documentation/networking/ |
| H A 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 …]
|
| 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
17 CAN network using SAE J1939 as data link layer (however, this is not a
38 Three different addressing formats can be employed:
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
53 When transmitting data using the ISO-TP protocol, the payload can either fit
[all …]
|
| /linux/net/can/ |
| H A D | Kconfig | 3 # Controller Area Network (CAN) network layer core configuration
6 menuconfig CAN config
7 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
16 PF_CAN is contained in <Documentation/networking/can.rst>.
18 If you want CAN support you should say Y here and also to the
22 if CAN
[all …]
|
| H A D | proc.c | 3 * proc.c - procfs support for Protocol family CAN core module
48 #include <linux/can/can-ml.h>
49 #include <linux/can/core.h>
81 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_init_stats()
82 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_init_stats()
107 printk(KERN_ERR "can: calc_rate: count exceeded! %ld\n", in calc_rate()
117 struct net *net = timer_container_of(net, t, can.stattimer); in can_stat_update()
118 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stat_update()
181 mod_timer(&net->can.stattimer, round_jiffies(jiffies + HZ)); in can_stat_update()
219 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stats_proc_show()
[all …]
|
| H A D | af_can.c | 2 /* af_can.c - Protocol family CAN core module
3 * (used by different CAN protocol modules)
58 #include <linux/can.h>
59 #include <linux/can/core.h>
60 #include <linux/can/skb.h>
61 #include <linux/can/can-ml.h>
81 /* table of registered CAN protocols */
132 err = request_module("can-proto-%d", protocol); in can_create()
139 pr_err_ratelimited("can: request_module (can-proto-%d) failed.\n", in can_create()
187 * can_send - transmit a CAN frame (optional with local loopback)
[all …]
|
| H A D | Makefile | 6 obj-$(CONFIG_CAN) += can.o
7 can-y := af_can.o
8 can-$(CONFIG_PROC_FS) += proc.o
10 obj-$(CONFIG_CAN_RAW) += can-raw.o
11 can-raw-y := raw.o
13 obj-$(CONFIG_CAN_BCM) += can-bcm.o
14 can-bcm-y := bcm.o
16 obj-$(CONFIG_CAN_GW) += can-gw.o
17 can-gw-y := gw.o
21 obj-$(CONFIG_CAN_ISOTP) += can-isotp.o
[all …]
|
| /linux/Documentation/devicetree/bindings/net/can/ |
| H A D | renesas,rcar-can.yaml | 4 $id: http://devicetree.org/schemas/net/can/renesas,rcar-can.yaml#
7 title: Renesas R-Car CAN Controller
17 - renesas,can-r8a7778 # R-Car M1-A
18 - renesas,can-r8a7779 # R-Car H1
19 - const: renesas,rcar-gen1-can # R-Car Gen1
23 - renesas,can-r8a7742 # RZ/G1H
24 - renesas,can-r8a7743 # RZ/G1M
25 - renesas,can-r8a7744 # RZ/G1N
26 - renesas,can-r8a7745 # RZ/G1E
27 - renesas,can-r8a77470 # RZ/G1C
[all …]
|
| H A D | xilinx,can.yaml | 4 $id: http://devicetree.org/schemas/net/can/xilinx,can.yaml#
8 Xilinx CAN and CANFD controller
16 - xlnx,zynq-can-1.0
17 - xlnx,axi-can-1.00.a
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)
69 - $ref: can-controller.yaml#
75 - xlnx,zynq-can-1.0
[all …]
|
| H A D | allwinner,sun4i-a10-can.yaml | 4 $id: http://devicetree.org/schemas/net/can/allwinner,sun4i-a10-can.yaml#
7 title: Allwinner A10 CAN Controller
14 - $ref: can-controller.yaml#
20 - const: allwinner,sun7i-a20-can
21 - const: allwinner,sun4i-a10-can
22 - const: allwinner,sun4i-a10-can
23 - const: allwinner,sun8i-r40-can
24 - const: allwinner,sun20i-d1-can
42 - allwinner,sun8i-r40-can
43 - allwinner,sun20i-d1-can
[all …]
|
| /linux/include/uapi/linux/ |
| H A D | can.h | 3 * linux/can.h
5 * Definitions for CAN network layer (socket addr / CAN frame / CAN filter)
53 /* controller area network (CAN) kernel definitions */
60 /* valid bits in CAN ID for frame formats */
69 * bit 0-28 : CAN identifier (11/29 bit)
83 * bit 0-28 : error class mask (see include/uapi/linux/can/error.h)
88 /* CAN payload length and DLC definitions according to ISO 11898-1 */
93 /* CAN FD payload length and DLC definitions according to ISO 11898-7 */
98 * CAN XL payload length and DLC definitions according to ISO 11898-1
99 * CAN XL DLC ranges from 0 .. 2047 => data length from 1 .. 2048 byte
[all …]
|
| /linux/include/uapi/linux/can/ |
| H A D | gw.h | 3 * linux/can/gw.h
5 * Definitions for CAN frame Gateway/Router/Bridge
49 #include <linux/can.h>
57 /* CAN gateway types */
60 CGW_TYPE_CAN_CAN, /* CAN->CAN routing */
66 /* CAN rtnetlink attribute definitions */
69 CGW_MOD_AND, /* CAN frame modification binary AND */
70 CGW_MOD_OR, /* CAN frame modification binary OR */
71 CGW_MOD_XOR, /* CAN frame modification binary XOR */
72 CGW_MOD_SET, /* CAN frame modification set alternate values */
[all …]
|
| /linux/drivers/rtc/ |
| H A D | Kconfig | 69 one can sleep when setting time, because it runs in the workqueue
129 can be accessed as /dev/rtc, which is a name
151 RTC test driver. It's a software RTC which can be
158 This driver can also be built as a module. If so, the module
172 This driver can also be built as a module. If so, the module
182 This driver can also be built as a module. If so, the module
192 This driver can also be built as a module. If so, the module
202 This driver can also be built as a module. If so, the module
212 This driver can also be built as a module. If so, the module
223 This driver can also be built as a module. If so, the module
[all …]
|
| /linux/Documentation/userspace-api/media/rc/ |
| H A D | lirc-get-features.rst | 41 .. _LIRC-CAN-REC-RAW:
47 .. _LIRC-CAN-REC-PULSE:
52 :ref:`LIRC_MODE_PULSE <lirc-mode-pulse>` can only be used for transmitting.
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:
[all …]
|
| /linux/fs/nls/ |
| H A D | Kconfig | 43 The Microsoft FAT file system family can deal with filenames in
48 only, not to the file contents. You can include several codepages;
55 The Microsoft FAT file system family can deal with filenames in
60 only, not to the file contents. You can include several codepages;
67 The Microsoft FAT file system family can deal with filenames in
72 only, not to the file contents. You can include several codepages;
80 The Microsoft FAT file system family can deal with filenames in
85 only, not to the file contents. You can include several codepages;
96 The Microsoft FAT file system family can deal with filenames in
101 only, not to the file contents. You can include several codepages;
[all …]
|
| /linux/drivers/net/can/kvaser_pciefd/ |
| H A D | kvaser_pciefd_devlink.c | 38 int kvaser_pciefd_devlink_port_register(struct kvaser_pciefd_can *can) in kvaser_pciefd_devlink_port_register() argument
43 .phys.port_number = can->can.dev->dev_port, in kvaser_pciefd_devlink_port_register()
45 devlink_port_attrs_set(&can->devlink_port, &attrs); in kvaser_pciefd_devlink_port_register()
47 ret = devlink_port_register(priv_to_devlink(can->kv_pcie), in kvaser_pciefd_devlink_port_register()
48 &can->devlink_port, can->can.dev->dev_port); in kvaser_pciefd_devlink_port_register()
52 SET_NETDEV_DEVLINK_PORT(can->can.dev, &can->devlink_port); in kvaser_pciefd_devlink_port_register()
57 void kvaser_pciefd_devlink_port_unregister(struct kvaser_pciefd_can *can) in kvaser_pciefd_devlink_port_unregister() argument
59 devlink_port_unregister(&can->devlink_port); in kvaser_pciefd_devlink_port_unregister()
|
| /linux/Documentation/core-api/real-time/ |
| H A D | hardware.rst | 9 The way a workload is handled can be influenced by the hardware it runs on.
13 can affect the deterministic handling of workloads in other applications.
21 tasks in a system. One task can dominate the available caches, forcing another
22 task to wait until a cache line is written back to main memory before it can
25 can be buffered before being written back. Conversely, certain write patterns
29 This issue can be partly mitigated if applications do not share the same CPU
32 project (https://www.open-mpi.org/projects/hwloc/) can visualize the hierarchy.
35 is minimized, bottlenecks can still occur when accessing system memory. Memory
39 In some cases, cache and memory bottlenecks can be controlled if the hardware
46 These features can be configured through the Linux Resource Control interface.
[all …]
|
| /linux/drivers/accessibility/speakup/ |
| H A D | Kconfig | 10 kernel, it can speak everything on the text console from
14 can subscribe to.
22 that can be used with a plain text terminal.
24 Speakup can either be built in or compiled as a module
28 the synthesizer drivers below can only be built as
36 The Dectalk pc driver can only be built as a module, and
38 the module can be loaded. See the decpc choice below
55 synthesizer. You can say y to build it into the kernel,
64 synthesizer. You can say y to build it into the kernel,
72 synthesizer. You can say y to build it into the kernel,
[all …]
|
| /linux/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,
52 The official data sheets can be found at ELM electronics' home page:
64 If you have kept this default configuration, the line discipline can
80 Once the ldisc is attached, the CAN interface starts out unconfigured.
85 sudo ip link set can0 type can bitrate 500000
92 After this, you can set out as usual with candump, cansniffer, etc.
[all …]
|
| /linux/Documentation/networking/device_drivers/can/ctu/ |
| H A D | ctucanfd-driver.rst | 3 CTU CAN FD Driver
9 About CTU CAN FD IP Core
12 `CTU CAN FD <https://gitlab.fel.cvut.cz/canbus/ctucanfd_ip_core>`_
19 `Vivado integration <https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top>`_
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
33 version of emulation support can be cloned from ctu-canfd branch of QEMU local
40 SocketCAN is a standard common interface for CAN devices in the Linux
43 described in `Linux SocketCAN <https://www.kernel.org/doc/html/latest/networking/can.html>`_.
[all …]
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | regulator.yaml | 131 hardware performs emergency shutdown. Zero can be passed to disable
133 limit setting can be omitted.
138 Zero can be passed to disable error detection and value '1' indicates
139 that detection should be enabled but limit setting can be omitted.
144 damaged. Recovery actions should be initiated. Zero can be passed to
146 be enabled but limit setting can be omitted.
150 hardware performs emergency shutdown. Zero can be passed to disable
152 limit setting can be omitted. Limit is given as microvolt offset from
158 Zero can be passed to disable error detection and value '1' indicates
159 that detection should be enabled but limit setting can be omitted. Limit
[all …]
|
| /linux/Documentation/sound/cards/ |
| H A D | pcmtest.rst | 6 The Virtual PCM Test Driver emulates a generic PCM device, and can be used for
8 the PCM middle layer. Additionally, it can be used for simulating hard to reproduce
11 What can this driver do?
14 At this moment the driver can do the following things:
23 Also, this driver can check the playback stream for containing the predefined pattern,
47 First of all, you may want to specify the pattern for data generation. You can do it
54 To set the pattern for the channel 0 you can execute the following command:
63 The pattern itself can be up to 4096 bytes long.
69 can be used for time delay/speedup simulations. The parameter has integer type, and
73 negative - faster. You can try it yourself by starting a recording in any
[all …]
|
| /linux/drivers/net/can/usb/etas_es58x/ |
| H A D | es58x_core.h | 3 /* Driver for ETAS GmbH ES58X USB CAN(-FD) Bus Interfaces.
15 #include <linux/can.h>
16 #include <linux/can/dev.h>
55 * @ES58X_DUAL_CHANNEL: Device has two CAN channels. If this flag is
56 * not set, it is implied that the device has only one CAN
58 * @ES58X_FD_FAMILY: Device is CAN-FD capable. If this flag is not
59 * set, the device only supports classical CAN.
73 * @ES58X_PHYSICAL_LAYER_HIGH_SPEED: High-speed CAN (c.f. ISO
76 * Some products of the ETAS portfolio also support low-speed CAN
92 * @ES58X_SYNC_EDGE_SINGLE: ISO CAN specification defines the use of a
[all …]
|
| /linux/Documentation/core-api/ |
| H A D | maple_tree.rst | 17 entry in a cache-efficient manner. The tree can also be put into an RCU-safe
19 synchronize on a lock, which can be the default spinlock, or the user can set
28 The Maple Tree can store values between ``0`` and ``ULONG_MAX``. The Maple
31 entries then the users can convert the entries using xa_mk_value() and convert
33 value, then the user can convert the value when using the
36 The Maple Tree can also be configured to support searching for a gap of a given
57 ``0`` upwards or ``ULONG_MAX`` down. An allocation tree can be used by
60 You can then set entries using mtree_store() or mtree_store_range().
64 given index. You can use mtree_erase() to erase an entire range by only
69 currently ``NULL``, you can use mtree_insert_range() or mtree_insert() which
[all …]
|