Home
last modified time | relevance | path

Searched full:can (Results 1 – 25 of 7083) sorted by relevance

12345678910>>...284

/Linux-v5.4/Documentation/devicetree/bindings/net/can/
Drcar_can.txt1 Renesas R-Car CAN controller Device Tree Bindings
5 - compatible: "renesas,can-r8a7743" if CAN controller is a part of R8A7743 SoC.
6 "renesas,can-r8a7744" if CAN controller is a part of R8A7744 SoC.
7 "renesas,can-r8a7745" if CAN controller is a part of R8A7745 SoC.
8 "renesas,can-r8a77470" if CAN controller is a part of R8A77470 SoC.
9 "renesas,can-r8a774a1" if CAN controller is a part of R8A774A1 SoC.
10 "renesas,can-r8a774c0" if CAN controller is a part of R8A774C0 SoC.
11 "renesas,can-r8a7778" if CAN controller is a part of R8A7778 SoC.
12 "renesas,can-r8a7779" if CAN controller is a part of R8A7779 SoC.
13 "renesas,can-r8a7790" if CAN controller is a part of R8A7790 SoC.
[all …]
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).
23 - rx-mailbox-count : Can Rx mailbox buffer count (CAN FD in mailbox Rx
[all …]
Dcan-transceiver.txt1 Generic CAN transceiver Device Tree binding
4 CAN transceiver typically limits the max speed in standard CAN and CAN FD
7 the "can-transceiver" node can be used.
11 speed that CAN/CAN-FD can run. Any other value
16 Based on Texas Instrument's TCAN1042HGV CAN Transceiver
20 can-transceiver {
/Linux-v5.4/drivers/net/can/
Dkvaser_pciefd.c13 #include <linux/can/dev.h>
21 MODULE_DESCRIPTION("CAN driver for Kvaser CAN/PCIe devices");
47 /* Kvaser KCAN CAN controller registers */
178 /* Controller got CAN FD capability */
190 /* CAN FD non-ISO */
196 /* Classic CAN mode */
253 struct can_priv can; member
269 struct kvaser_pciefd_can *can[KVASER_PCIEFD_MAX_CAN_CHANNELS]; member
484 static void kvaser_pciefd_request_status(struct kvaser_pciefd_can *can) in kvaser_pciefd_request_status() argument
489 cmd |= ++can->cmd_seq << KVASER_PCIEFD_KCAN_CMD_SEQ_SHIFT; in kvaser_pciefd_request_status()
[all …]
DKconfig2 menu "CAN Device Drivers"
5 tristate "Virtual Local CAN Interface (vcan)"
8 virtual local CAN interface.
10 This driver can also be built as a module. If so, the module
14 tristate "Virtual CAN Tunnel (vxcan)"
17 local CAN traffic tunnel between two virtual CAN network devices.
20 versa. The vxcan can be used for cross namespace communication.
22 In opposite to vcan loopback devices the vxcan only forwards CAN
24 CAN frames. To disable a potential echo in af_can.c the vxcan driver
26 in each namespace the CAN GW hop counter is set to zero.
[all …]
Dsun4i_can.c2 * 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>
54 #include <linux/can/led.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 */
[all …]
/Linux-v5.4/Documentation/networking/
Dcan.rst8 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 …]
/Linux-v5.4/net/can/
DKconfig3 # Controller Area Network (CAN) network layer core configuration
6 menuconfig CAN config
8 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
21 if CAN
[all …]
Dproc.c3 * proc.c - procfs support for Protocol family CAN core module
48 #include <linux/can/can-ml.h>
49 #include <linux/can/core.h>
82 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_init_stats()
83 struct can_rcv_lists_stats *rcv_lists_stats = net->can.rcv_lists_stats; in can_init_stats()
110 printk(KERN_ERR "can: calc_rate: count exceeded! %ld\n", in calc_rate()
122 struct net *net = from_timer(net, t, can.stattimer); in can_stat_update()
123 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()
216 struct can_pkg_stats *pkg_stats = net->can.pkg_stats; in can_stats_proc_show()
[all …]
Daf_can.c2 /* 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()
184 * can_send - transmit a CAN frame (optional with local loopback)
[all …]
/Linux-v5.4/include/uapi/linux/can/
Dgw.h3 * 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 …]
Dnetlink.h3 * 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-v5.4/drivers/net/can/usb/
DKconfig2 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 USB/2 CAN/USB interface"
20 This driver supports the CAN-USB/2 interface
27 candleLight USB CAN interfaces USB/CAN devices
33 tristate "Kvaser CAN/USB interface"
35 This driver adds support for Kvaser CAN/USB devices like Kvaser
84 tristate "Microchip CAN BUS Analyzer interface"
86 This driver supports the CAN BUS Analyzer interface
[all …]
/Linux-v5.4/drivers/hwmon/
DKconfig13 can include temperature sensors, voltage sensors, fan speed
23 This support 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
60 chip can be found on Abit uGuru featuring motherboards (most modern
65 This driver can also be built as a module. If so, the module
75 uGuru chip can be found on recent Abit motherboards (since end
79 This driver can also be built as a module. If so, the module
89 This driver can also be built as a module. If so, the module
99 This driver can also be built as a module. If so, the module
109 This driver can also be built as a module. If so, the module
[all …]
/Linux-v5.4/include/uapi/linux/
Dcan.h3 * linux/can.h
5 * Definitions for CAN network layer (socket addr / CAN frame / CAN filter)
52 /* controller area network (CAN) kernel definitions */
59 /* valid bits in CAN ID for frame formats */
67 * bit 0-28 : CAN identifier (11/29 bit)
80 * bit 0-28 : error class mask (see include/uapi/linux/can/error.h)
85 /* CAN payload length and DLC definitions according to ISO 11898-1 */
89 /* CAN FD payload length and DLC definitions according to ISO 11898-7 */
94 * struct can_frame - basic CAN frame structure
95 * @can_id: CAN ID of the frame and CAN_*_FLAG flags, see canid_t definition
[all …]
Dmii.h63 #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-v5.4/Documentation/media/uapi/rc/
Dlirc-get-features.rst48 .. _LIRC-CAN-REC-RAW:
54 .. _LIRC-CAN-REC-PULSE:
59 :ref:`LIRC_MODE_PULSE <lirc-mode-pulse>` can only be used for transmitting.
61 .. _LIRC-CAN-REC-MODE2:
71 .. _LIRC-CAN-REC-LIRCCODE:
77 .. _LIRC-CAN-REC-SCANCODE:
84 .. _LIRC-CAN-SET-SEND-CARRIER:
91 .. _LIRC-CAN-SET-SEND-DUTY-CYCLE:
98 .. _LIRC-CAN-SET-TRANSMITTER-MASK:
105 .. _LIRC-CAN-SET-REC-CARRIER:
[all …]
/Linux-v5.4/drivers/rtc/
DKconfig72 one can sleep when setting time, because it runs in the workqueue
123 can be accessed as /dev/rtc, which is a name
145 RTC test driver. It's a software RTC which can be
152 This driver can also be built as a module. If so, the module
166 This driver can also be built as a module. If so, the module
176 This driver can also be built as a module. If so, the module
186 This driver can also be built as a module. If so, the module
196 This driver can also be built as a module. If so, the module
207 This driver can also be built as a module. If so, the module
217 This driver can also be built as a module. If so, the module
[all …]
/Linux-v5.4/drivers/staging/speakup/
DKconfig10 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
49 synthesizer. You can say y to build it into the kernel,
58 synthesizer. You can say y to build it into the kernel,
66 synthesizer. You can say y to build it into the kernel,
[all …]
/Linux-v5.4/drivers/hwmon/pmbus/
DKconfig12 This driver can also be built as a module. If so, the module will
26 This driver can also be built as a module. If so, the module will
36 This driver can also be built as a module. If so, the module will
46 This driver can also be built as a module. If so, the module will
55 This driver can also be built as a module. If so, the module will
64 This driver can also be built as a module. If so, the module will
73 This driver can also be built as a module. If so, the module will
82 This driver can also be built as a module. If so, the module will
91 This driver can also be built as a module. If so, the module will
100 This driver can also be built as a module. If so, the module will
[all …]
/Linux-v5.4/fs/nls/
DKconfig43 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-v5.4/net/netfilter/ipset/
DKconfig9 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 addresse) 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 …]
/Linux-v5.4/Documentation/power/regulator/
Dconsumer.rst12 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-v5.4/drivers/i2c/busses/
DKconfig21 This driver can also be built as a module. If so, the module
33 This driver can also be built as a module. If so, the module
43 This driver can also be built as a module. If so, the module
55 This driver can also be built as a module. If so, the module
68 This driver can also be built as a module. If so, the module
78 This driver can also be built as a module. If so, the module
88 This driver can also be built as modules. If so, the modules will
98 This driver can also be built as a module. If so, the module
149 This driver can also be built as a module. If so, the module
160 This driver can also be built as a module. If so, the module
[all …]
/Linux-v5.4/drivers/block/paride/
DTransition-notes2 If ps_tq is scheduled, ps_tq_active is 1. ps_tq_int() can be called
5 under ps_spinlock. There are three places where that can happen:
7 Consider the sequnce of these events. A can not be preceded by
9 ps_spinlock. C is always preceded by B, since we can't reach it
11 IOW, the sequence is A?(BA|BC|B)*. OTOH, number of B can not exceed
16 since at any time number of B can not exceed the number of these
17 moments which, in turn, can not exceed the number of A and C.
49 1) at any time at most one thread of execution can be in that area or
60 (1) can become not true if some thread enters that area while another is there.
61 a) do_pd_request1() can be called from next_request() or do_pd_request()
[all …]

12345678910>>...284