Home
last modified time | relevance | path

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

/linux/drivers/net/can/m_can/
H A DKconfig3 tristate "Bosch M_CAN support"
6 Say Y here if you want support for Bosch M_CAN controller framework.
7 This is common support for devices that embed the Bosch M_CAN IP.
12 tristate "Generic PCI Bus based M_CAN driver"
15 Say Y here if you want to support Bosch M_CAN controller connected
19 tristate "Bosch M_CAN support for io-mapped devices"
22 Say Y here if you want support for IO Mapped Bosch M_CAN controller.
23 This support is for devices that have the Bosch M_CAN controller
29 tristate "TCAN4X5X M_CAN device"
32 M_CAN controller. This device is a peripheral device that uses the
H A Dm_can_platform.c2 // IOMapped CAN bus driver for Bosch M_CAN controller
12 #include "m_can.h"
99 addr = devm_platform_ioremap_resource_byname(pdev, "m_can"); in m_can_plat_probe()
222 { .compatible = "bosch,m_can", .data = NULL },
242 MODULE_DESCRIPTION("M_CAN driver for IO Mapped Bosch controllers");
H A DMakefile3 # Makefile for the Bosch M_CAN controller driver.
6 obj-$(CONFIG_CAN_M_CAN) += m_can.o
H A Dm_can_pci.c3 * PCI Specific M_CAN Glue
17 #include "m_can.h"
208 MODULE_DESCRIPTION("CAN bus driver for Bosch M_CAN controller on PCI bus");
H A Dm_can.c2 // CAN bus driver for Bosch M_CAN controller
7 /* Bosch M_CAN user manual can be obtained from:
8 * https://github.com/linux-can/can-doc/tree/master/m_can
27 #include "m_can.h"
315 /* The ID and DLC registers are adjacent in M_CAN FIFO memory,
1240 /* The m_can controller signals its interrupt status as a level, but in m_can_interrupt_handler()
1419 /* Equation based on Bosch's M_CAN User Manual's in m_can_set_bittiming()
1448 /* Configure M_CAN chip:
1612 /* basic m_can configuration */ in m_can_start()
1650 /* Checks core release number of M_CAN
[all …]
H A Dm_can.h2 /* CAN bus driver for Bosch M_CAN controller
32 /* m_can lec values */
H A Dtcan4x5x-regmap.c100 /* M_CAN */
121 regmap_reg_range(0x1000, 0x10fc), /* M_CAN */
H A Dtcan4x5x-core.c525 dev_err(&spi->dev, "Failed registering m_can device %pe\n", in tcan4x5x_can_probe()
/linux/arch/arm64/boot/dts/ti/
H A Dk3-am62-mcu.dtsi155 compatible = "bosch,m_can";
158 reg-names = "m_can", "message_ram";
167 compatible = "bosch,m_can";
170 reg-names = "m_can", "message_ram";
/linux/arch/arm/boot/dts/microchip/
H A Dsama7g5.dtsi379 compatible = "bosch,m_can";
381 reg-names = "m_can", "message_ram";
395 compatible = "bosch,m_can";
397 reg-names = "m_can", "message_ram";
411 compatible = "bosch,m_can";
413 reg-names = "m_can", "message_ram";
427 compatible = "bosch,m_can";
429 reg-names = "m_can", "message_ram";
443 compatible = "bosch,m_can";
445 reg-names = "m_can", "message_ram";
[all …]
H A Dlan966x.dtsi478 compatible = "bosch,m_can";
480 reg-names = "m_can", "message_ram";
493 compatible = "bosch,m_can";
495 reg-names = "m_can", "message_ram";
H A Dsama5d2.dtsi743 compatible = "bosch,m_can";
745 reg-names = "m_can", "message_ram";
1143 compatible = "bosch,m_can";
1145 reg-names = "m_can", "message_ram";
/linux/arch/arm/boot/dts/ti/omap/
H A Ddra76x.dtsi28 compatible = "bosch,m_can";
30 reg-names = "m_can", "message_ram";
/linux/drivers/net/can/
H A DMakefile30 obj-$(CONFIG_CAN_M_CAN) += m_can/
H A DKconfig225 source "drivers/net/can/m_can/Kconfig"
/linux/Documentation/networking/
H A Dcan.rst1435 2. non-ISO compliant (fixed, like the M_CAN IP core v3.0.1 in m_can.c)
/linux/
H A DMAINTAINERS15417 F: Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
15418 F: drivers/net/can/m_can/m_can.c
15419 F: drivers/net/can/m_can/m_can.h
15420 F: drivers/net/can/m_can/m_can_platform.c