c_can.txt 1.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. Bosch C_CAN/D_CAN controller Device Tree Bindings
  2. -------------------------------------------------
  3. Required properties:
  4. - compatible : Should be "bosch,c_can" for C_CAN controllers and
  5. "bosch,d_can" for D_CAN controllers.
  6. Can be "ti,dra7-d_can", "ti,am3352-d_can" or
  7. "ti,am4372-d_can".
  8. - reg : physical base address and size of the C_CAN/D_CAN
  9. registers map
  10. - interrupts : property with a value describing the interrupt
  11. number
  12. Optional properties:
  13. - ti,hwmods : Must be "d_can<n>" or "c_can<n>", n being the
  14. instance number
  15. - syscon-raminit : Handle to system control region that contains the
  16. RAMINIT register, register offset to the RAMINIT
  17. register and the CAN instance number (0 offset).
  18. Note: "ti,hwmods" field is used to fetch the base address and irq
  19. resources from TI, omap hwmod data base during device registration.
  20. Future plan is to migrate hwmod data base contents into device tree
  21. blob so that, all the required data will be used from device tree dts
  22. file.
  23. Example:
  24. Step1: SoC common .dtsi file
  25. dcan1: d_can@481d0000 {
  26. compatible = "bosch,d_can";
  27. reg = <0x481d0000 0x2000>;
  28. interrupts = <55>;
  29. interrupt-parent = <&intc>;
  30. status = "disabled";
  31. };
  32. (or)
  33. dcan1: d_can@481d0000 {
  34. compatible = "bosch,d_can";
  35. ti,hwmods = "d_can1";
  36. reg = <0x481d0000 0x2000>;
  37. interrupts = <55>;
  38. interrupt-parent = <&intc>;
  39. status = "disabled";
  40. };
  41. Step 2: board specific .dts file
  42. &dcan1 {
  43. status = "okay";
  44. };