Home
last modified time | relevance | path

Searched full:m_can (Results 1 – 15 of 15) sorted by relevance

/kernel/linux/linux-5.10/drivers/net/can/m_can/
DKconfig3 tristate "Bosch M_CAN support"
5 Say Y here if you want support for Bosch M_CAN controller framework.
6 This is common support for devices that embed the Bosch M_CAN IP.
9 tristate "Bosch M_CAN support for io-mapped devices"
13 Say Y here if you want support for IO Mapped Bosch M_CAN controller.
14 This support is for devices that have the Bosch M_CAN controller
21 tristate "TCAN4X5X M_CAN device"
24 M_CAN controller. This device is a peripheral device that uses the
Dm_can_platform.c2 // IOMapped CAN bus driver for Bosch M_CAN controller
10 #include "m_can.h"
81 res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "m_can"); in m_can_plat_probe()
184 { .compatible = "bosch,m_can", .data = NULL },
204 MODULE_DESCRIPTION("M_CAN driver for IO Mapped Bosch controllers");
DMakefile3 # Makefile for the Bosch M_CAN controller driver.
6 obj-$(CONFIG_CAN_M_CAN) += m_can.o
Dm_can.c2 // CAN bus driver for Bosch M_CAN controller
7 /* Bosch M_CAN user manual can be obtained from:
8 * http://www.bosch-semiconductors.de/media/pdf_1/ipmodules_1/m_can/
25 #include "m_can.h"
383 /* enable m_can configuration */ in m_can_config_endisable()
1082 /* Equation based on Bosch's M_CAN User Manual's in m_can_set_bittiming()
1111 /* Configure M_CAN chip:
1240 /* basic m_can configuration */ in m_can_start()
1263 /* Checks core release number of M_CAN
1283 /* M_CAN v3.x.y: create return value */ in m_can_check_core_release()
[all …]
Dm_can.h2 /* CAN bus driver for Bosch M_CAN controller
31 /* m_can lec values */
Dtcan4x5x.c11 #include "m_can.h"
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/can/
Dbosch,m_can.yaml4 $id: http://devicetree.org/schemas/net/can/bosch,m_can.yaml#
16 const: bosch,m_can
20 - description: M_CAN registers map
25 - const: m_can
55 Multiple M_CAN instances can share the same Message RAM
59 used by this M_CAN controller.
68 M_CAN includes the following elements according to user manual:
78 M_CAN user manual for details.
128 compatible = "bosch,m_can";
130 reg-names = "m_can", "message_ram";
Dtcan4x5x.txt17 See Documentation/devicetree/bindings/net/can/bosch,m_can.yaml for additional
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dstm32mp153.dtsi27 compatible = "bosch,m_can";
29 reg-names = "m_can", "message_ram";
40 compatible = "bosch,m_can";
42 reg-names = "m_can", "message_ram";
Ddra76x.dtsi28 compatible = "bosch,m_can";
30 reg-names = "m_can", "message_ram";
Dsama5d2.dtsi727 compatible = "bosch,m_can";
729 reg-names = "m_can", "message_ram";
1133 compatible = "bosch,m_can";
1135 reg-names = "m_can", "message_ram";
/kernel/linux/linux-5.10/drivers/net/can/
DMakefile25 obj-$(CONFIG_CAN_M_CAN) += m_can/
DKconfig173 source "drivers/net/can/m_can/Kconfig"
/kernel/linux/linux-5.10/Documentation/networking/
Dcan.rst1366 2. non-ISO compliant (fixed, like the M_CAN IP core v3.0.1 in m_can.c)
/kernel/linux/linux-5.10/
DMAINTAINERS10717 F: Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
10718 F: drivers/net/can/m_can/m_can.c
10719 F: drivers/net/can/m_can/m_can.h
10720 F: drivers/net/can/m_can/m_can_platform.c
17565 F: drivers/net/can/m_can/tcan4x5x.c