1Bosch C_CAN/D_CAN controller Device Tree Bindings 2------------------------------------------------- 3 4Required 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 14Optional properties: 15- ti,hwmods : Must be "d_can<n>" or "c_can<n>", n being the 16 instance number 17- syscon-raminit : Handle to system control region that contains the 18 RAMINIT register, register offset to the RAMINIT 19 register and the CAN instance number (0 offset). 20 21Note: "ti,hwmods" field is used to fetch the base address and irq 22resources from TI, omap hwmod data base during device registration. 23Future plan is to migrate hwmod data base contents into device tree 24blob so that, all the required data will be used from device tree dts 25file. 26 27Example: 28 29Step1: SoC common .dtsi file 30 31 dcan1: d_can@481d0000 { 32 compatible = "bosch,d_can"; 33 reg = <0x481d0000 0x2000>; 34 interrupts = <55>; 35 interrupt-parent = <&intc>; 36 status = "disabled"; 37 }; 38 39(or) 40 41 dcan1: d_can@481d0000 { 42 compatible = "bosch,d_can"; 43 ti,hwmods = "d_can1"; 44 reg = <0x481d0000 0x2000>; 45 interrupts = <55>; 46 interrupt-parent = <&intc>; 47 status = "disabled"; 48 }; 49 50Step 2: board specific .dts file 51 52 &dcan1 { 53 status = "okay"; 54 }; 55