c_can.txt

Version: - FREEBSD - FREEBSD-13-STABLE - FREEBSD-13-0 - FREEBSD-12-STABLE - FREEBSD-12-0 - FREEBSD-11-STABLE - FREEBSD-11-0 - FREEBSD-10-STABLE - FREEBSD-10-0 - FREEBSD-9-STABLE - FREEBSD-9-0 - FREEBSD-8-STABLE - FREEBSD-8-0 - FREEBSD-7-STABLE - FREEBSD-7-0 - FREEBSD-6-STABLE - FREEBSD-6-0 - FREEBSD-5-STABLE - FREEBSD-5-0 - FREEBSD-4-STABLE - FREEBSD-3-STABLE - FREEBSD22 - l41 - OPENBSD - linux-2.6 - MK84 - PLAN9 - xnu-8792
SearchContext: - none - 3 - 10

    1 Bosch C_CAN/D_CAN controller Device Tree Bindings
    2 -------------------------------------------------
    3 
    4 Required properties:
    5 - compatible            : Should be "bosch,c_can" for C_CAN controllers and
    6                           "bosch,d_can" for D_CAN controllers.
    7                           Can be "ti,dra7-d_can", "ti,am3352-d_can" or
    8                           "ti,am4372-d_can".
    9 - reg                   : physical base address and size of the C_CAN/D_CAN
   10                           registers map
   11 - interrupts            : property with a value describing the interrupt
   12                           number
   13 
   14 The following are mandatory properties for DRA7x, AM33xx and AM43xx SoCs only:
   15 - ti,hwmods             : Must be "d_can<n>" or "c_can<n>", n being the
   16                           instance number
   17 
   18 The following are mandatory properties for Keystone 2 66AK2G SoCs only:
   19 - power-domains         : Should contain a phandle to a PM domain provider node
   20                           and an args specifier containing the DCAN device id
   21                           value. This property is as per the binding,
   22                           Documentation/devicetree/bindings/soc/ti/sci-pm-domain.yaml
   23 - clocks                : CAN functional clock phandle. This property is as per the
   24                           binding,
   25                           Documentation/devicetree/bindings/clock/ti,sci-clk.yaml
   26 
   27 Optional properties:
   28 - syscon-raminit        : Handle to system control region that contains the
   29                           RAMINIT register, register offset to the RAMINIT
   30                           register and the CAN instance number (0 offset).
   31 
   32 Note: "ti,hwmods" field is used to fetch the base address and irq
   33 resources from TI, omap hwmod data base during device registration.
   34 Future plan is to migrate hwmod data base contents into device tree
   35 blob so that, all the required data will be used from device tree dts
   36 file.
   37 
   38 Example:
   39 
   40 Step1: SoC common .dtsi file
   41 
   42         dcan1: d_can@481d0000 {
   43                 compatible = "bosch,d_can";
   44                 reg = <0x481d0000 0x2000>;
   45                 interrupts = <55>;
   46                 interrupt-parent = <&intc>;
   47                 status = "disabled";
   48         };
   49 
   50 (or)
   51 
   52         dcan1: d_can@481d0000 {
   53                 compatible = "bosch,d_can";
   54                 ti,hwmods = "d_can1";
   55                 reg = <0x481d0000 0x2000>;
   56                 interrupts = <55>;
   57                 interrupt-parent = <&intc>;
   58                 status = "disabled";
   59         };
   60 
   61 Step 2: board specific .dts file
   62 
   63         &dcan1 {
   64                 status = "okay";
   65         };

Cache object: 530d391483b10a84be349dc80a31b819

[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]

This page is part of the FreeBSD/Linux Linux Kernel Cross-Reference, and was automatically generated using a modified version of the LXR engine.

FreeBSD/Linux Kernel Cross Reference sys/contrib/device-tree/Bindings/net/can/c_can.txt

FreeBSD/Linux Kernel Cross Reference
sys/contrib/device-tree/Bindings/net/can/c_can.txt