/openbmc/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"); 56 /* Kvaser KCAN CAN controller registers */ 143 /* FDF bit when controller is in classic CAN mode */ 159 /* Controller got CAN FD capability */ 178 /* Classic CAN mode */ 184 /* CAN FD non-ISO */ 371 struct can_priv can; member 387 struct kvaser_pciefd_can *can[KVASER_PCIEFD_MAX_CAN_CHANNELS]; member 465 static inline void kvaser_pciefd_send_kcan_cmd(struct kvaser_pciefd_can *can, u32 cmd) in kvaser_pciefd_send_kcan_cmd() argument [all …]
|
/openbmc/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 …]
|
/openbmc/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 | 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() 185 * 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 …]
|
/openbmc/qemu/docs/system/devices/ |
H A D | can.rst | 1 CAN Bus Emulation Support 3 The CAN bus emulation provides mechanism to connect multiple 4 emulated CAN controller chips together by one or multiple CAN buses 6 can be connected to host system CAN API (at this time only Linux 9 The concept of buses is generic and different CAN controllers 10 can be implemented. 16 The PCI addon card hardware has been selected as the first CAN 17 interface to implement because such device can be easily connected 20 In 2020, CTU CAN FD controller model has been added as part 28 CAN subsystem for RTEMS. But lack of common environment for code and RTEMS [all …]
|
/openbmc/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 | 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 …]
|
H A D | xilinx,can.yaml | 4 $id: http://devicetree.org/schemas/net/can/xilinx,can.yaml# 8 Xilinx Axi CAN/Zynq CANPS 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) 62 - $ref: can-controller.yaml# 68 - xlnx,zynq-can-1.0 85 - xlnx,axi-can-1.00.a [all …]
|
/openbmc/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 …]
|
/openbmc/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 supports for several CAN/USB interfaces 24 - esd CAN-USB/2 25 - esd CAN-USB/Micro 31 tristate "ETAS ES58X CAN/USB interfaces" 42 tristate "Fintek F81604 USB to 2CAN interface" 44 This driver supports the Fintek F81604 USB to 2CAN interface. [all …]
|
/openbmc/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 …]
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 083.out | 4 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo 8 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo 12 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo 16 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo 20 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo 24 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo 28 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo 32 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo 36 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo 40 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo [all …]
|
/openbmc/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 117 This driver can also be built as a module. If so, the module [all …]
|
/openbmc/linux/drivers/hwmon/pmbus/ |
H A D | Kconfig | 12 This driver can also be built as a module. If so, the module will 27 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 47 This driver can also be built as a module. If so, the module will 57 This driver can also be built as a module. If so, the module will 66 This driver can also be built as a module. If so, the module will 75 This driver can also be built as a module. If so, the module will 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 will 105 This driver can also be built as a module. If so, the module will [all …]
|
/openbmc/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 213 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 …]
|
/openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/ |
H A D | parselogs-ignores-qemuall.txt | 9 # pci 0000:00:00.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size) 10 # pci 0000:00:00.0: [Firmware Bug]: reg 0x14: invalid BAR (can't size) 11 # pci 0000:00:00.0: [Firmware Bug]: reg 0x18: invalid BAR (can't size) 12 # pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size) 13 # pci 0000:00:00.0: [Firmware Bug]: reg 0x20: invalid BAR (can't size) 14 # pci 0000:00:00.0: [Firmware Bug]: reg 0x24: invalid BAR (can't size) 15 invalid BAR (can't size) 17 # pci 0000:00:00.0: [Firmware Bug]: BAR 0: invalid; can't size 18 # pci 0000:00:00.0: [Firmware Bug]: BAR 1: invalid; can't size 19 # pci 0000:00:00.0: [Firmware Bug]: BAR 2: invalid; can't size [all …]
|
/openbmc/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 …]
|
/openbmc/u-boot/drivers/spi/ |
H A D | Kconfig | 31 Enable the Altera SPI driver. This driver can be used to 40 Enable the Aspeed AST2500 FMC/SPI driver. This driver can be 54 Enable the Andestech ATCSPI200 SPI driver. This driver can be 72 many AT91 (ARM) chips. This driver can be used to access 79 Enable the BCM6328 HSSPI driver. This driver can be used to 87 Enable the BCM6348/BCM6358 SPI driver. This driver can be used to 94 Enable the Broadcom set-top box SPI driver. This driver can 101 Enable the Cadence Quad-SPI (QSPI) driver. This driver can be 108 Enable the Designware SPI driver. This driver can be used to 115 Enable the Samsung Exynos SPI driver. This driver can be used to [all …]
|
/openbmc/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 …]
|
/openbmc/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 …]
|