| /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 | kvaser_pciefd.c | 9 #include <linux/can/dev.h>
22 MODULE_DESCRIPTION("CAN driver for Kvaser CAN/PCIe devices");
63 /* Kvaser KCAN CAN controller registers */
150 /* FDF bit when controller is in classic CAN mode */
166 /* Controller got CAN FD capability */
185 /* Classic CAN mode */
191 /* CAN FD non-ISO */
408 struct can_priv can; member
424 struct kvaser_pciefd_can *can[KVASER_PCIEFD_MAX_CAN_CHANNELS]; member
510 static inline void kvaser_pciefd_send_kcan_cmd(struct kvaser_pciefd_can *can, u32 cmd) in kvaser_pciefd_send_kcan_cmd() argument
[all …]
|
| H A D | sun4i_can.c | 2 * sun4i_can.c - CAN bus controller driver for Allwinner SUN4I&SUN7I based SoCs
51 #include <linux/can.h>
52 #include <linux/can/dev.h>
53 #include <linux/can/error.h>
68 #define SUN4I_REG_MSEL_ADDR 0x0000 /* CAN Mode Select */
69 #define SUN4I_REG_CMD_ADDR 0x0004 /* CAN Command */
70 #define SUN4I_REG_STA_ADDR 0x0008 /* CAN Status */
71 #define SUN4I_REG_INT_ADDR 0x000c /* CAN Interrupt Flag */
72 #define SUN4I_REG_INTEN_ADDR 0x0010 /* CAN Interrupt Enable */
73 #define SUN4I_REG_BTIME_ADDR 0x0014 /* CAN Bus Timing 0 */
[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"
9 Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
10 communications protocol. Development of the CAN bus started in
12 released in 1986. The CAN bus was originally mainly for automotive,
14 applications. More information on the CAN network protocol family
15 PF_CAN is contained in <Documentation/networking/can.rst>.
17 If you want CAN support you should say Y here and also to the
21 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 = from_timer(net, t, can.stattimer); in can_stat_update()
118 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stat_update()
176 mod_timer(&net->can.stattimer, round_jiffies(jiffies + HZ)); in can_stat_update()
213 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stats_proc_show()
[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)
66 - $ref: can-controller.yaml#
72 - 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 …]
|
| H A D | mii.h | 63 #define BMSR_100HALF2 0x0200 /* Can do 100BASE-T2 HDX */
64 #define BMSR_100FULL2 0x0400 /* Can do 100BASE-T2 FDX */
65 #define BMSR_10HALF 0x0800 /* Can do 10mbps, half-duplex */
66 #define BMSR_10FULL 0x1000 /* Can do 10mbps, full-duplex */
67 #define BMSR_100HALF 0x2000 /* Can do 100mbps, half-duplex */
68 #define BMSR_100FULL 0x4000 /* Can do 100mbps, full-duplex */
69 #define BMSR_100BASE4 0x8000 /* Can do 100mbps, 4k packets */
86 #define ADVERTISE_RFAULT 0x2000 /* Say we can detect faults */
97 #define LPA_10HALF 0x0020 /* Can do 10mbps half-duplex */
98 #define LPA_1000XFULL 0x0020 /* Can do 1000BASE-X full-duplex */
[all …]
|
| /linux/drivers/net/can/usb/ |
| H A 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 electronics gmbh CAN/USB interfaces"
20 This driver adds support for several 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"
43 tristate "Fintek F81604 USB to 2CAN interface"
[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 …]
|
| H A D | netlink.h | 3 * linux/can/netlink.h
5 * Definitions for the CAN netlink interface
9 * This program is free software; you can redistribute it and/or modify
25 * CAN bit-timing parameters
28 * REQUIREMENTS" of the "Bosch CAN Specification version 2.0"
43 * CAN hardware-dependent bit-timing constant
48 char name[16]; /* Name of the CAN controller hardware */
60 * CAN clock parameters
63 __u32 freq; /* CAN system clock frequency in Hz */
67 * CAN operational and error states
[all …]
|
| /linux/drivers/hwmon/ |
| H A D | Kconfig | 13 can include temperature sensors, voltage sensors, fan speed
23 This support can also be built as a module. If so, the module
48 chip can be found on Abit uGuru featuring motherboards (most modern
53 This driver can also be built as a module. If so, the module
63 uGuru chip can be found on recent Abit motherboards (since end
67 This driver can also be built as a module. If so, the module
85 This driver can also be built as a module. If so, the module
95 This driver can also be built as a module. If so, the module
105 This driver can also be built as a module. If so, the module
116 This driver can also be built as a module. If so, the module
[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/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/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/drivers/i2c/busses/ |
| H A D | Kconfig | 28 This driver can also be built as a module. If so, the module
40 This driver can also be built as a module. If so, the module
50 This driver can also be built as a module. If so, the module
62 This driver can also be built as a module. If so, the module
72 This driver can also be built as a module. If so, the module
82 This driver can also be built as modules. If so, the modules will
109 This driver can also be built as a module. If so, the module
169 This driver can also be built as a module. If so, the module
188 This driver can also be built as a module. If so, the module
198 This driver can also be built as a module. If so, the module will be
[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/power/regulator/ |
| H A D | consumer.rst | 12 A consumer driver can get access to its supply regulator by calling ::
25 Consumers can be supplied by more than one regulator e.g. codec consumer with
39 A consumer can enable its power supply by calling::
48 A consumer can determine if a regulator is enabled by calling::
55 A consumer can disable its supply when no longer needed by calling::
63 Finally, a regulator can be forcefully disabled in the case of an emergency::
76 voltage to match system operating points. e.g. CPUfreq drivers can scale
80 Consumers can control their supply voltage by calling::
87 NOTE: this can be called when the regulator is enabled or disabled. If called
92 The regulators configured voltage output can be found by calling::
[all …]
|
| /linux/net/netfilter/ipset/ |
| H A D | Kconfig | 9 ipset(8). You can use the sets in netfilter via the "set" match
22 You can define here default value of the maximum number
25 The value can be overridden by the 'max_sets' module
33 can store IPv4 addresses (or network addresses) from a range.
42 can store IPv4 address and (source) MAC address pairs from a range.
51 can store TCP/UDP port numbers from a range.
60 can store arbitrary IPv4 or IPv6 addresses (or network addresses)
70 can store IPv4/IPv6 address and mark pairs.
79 can store IPv4/IPv6 address and protocol/port pairs.
88 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
[all …]
|