c_can.txt 1.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  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. - reg : physical base address and size of the C_CAN/D_CAN
  7. registers map
  8. - interrupts : property with a value describing the interrupt
  9. number
  10. Optional properties:
  11. - ti,hwmods : Must be "d_can<n>" or "c_can<n>", n being the
  12. instance number
  13. Note: "ti,hwmods" field is used to fetch the base address and irq
  14. resources from TI, omap hwmod data base during device registration.
  15. Future plan is to migrate hwmod data base contents into device tree
  16. blob so that, all the required data will be used from device tree dts
  17. file.
  18. Example:
  19. Step1: SoC common .dtsi file
  20. dcan1: d_can@481d0000 {
  21. compatible = "bosch,d_can";
  22. reg = <0x481d0000 0x2000>;
  23. interrupts = <55>;
  24. interrupt-parent = <&intc>;
  25. status = "disabled";
  26. };
  27. (or)
  28. dcan1: d_can@481d0000 {
  29. compatible = "bosch,d_can";
  30. ti,hwmods = "d_can1";
  31. reg = <0x481d0000 0x2000>;
  32. interrupts = <55>;
  33. interrupt-parent = <&intc>;
  34. status = "disabled";
  35. };
  36. Step 2: board specific .dts file
  37. &dcan1 {
  38. status = "okay";
  39. };