-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
can: c_can: Add device tree support to Bosch C_CAN/D_CAN controller
Add device tree support to C_CAN/D_CAN controller and usage details are added to device tree documentation. Driver was tested on AM335x EVM. Signed-off-by: AnilKumar Ch <anilkumar@ti.com> For the of binding doc: Reviewed-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
- Loading branch information
AnilKumar Ch
authored and
Marc Kleine-Budde
committed
Sep 21, 2012
1 parent
f27b1db
commit 2469627
Showing
2 changed files
with
87 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
Bosch C_CAN/D_CAN controller Device Tree Bindings | ||
------------------------------------------------- | ||
|
||
Required properties: | ||
- compatible : Should be "bosch,c_can" for C_CAN controllers and | ||
"bosch,d_can" for D_CAN controllers. | ||
- reg : physical base address and size of the C_CAN/D_CAN | ||
registers map | ||
- interrupts : property with a value describing the interrupt | ||
number | ||
|
||
Optional properties: | ||
- ti,hwmods : Must be "d_can<n>" or "c_can<n>", n being the | ||
instance number | ||
|
||
Note: "ti,hwmods" field is used to fetch the base address and irq | ||
resources from TI, omap hwmod data base during device registration. | ||
Future plan is to migrate hwmod data base contents into device tree | ||
blob so that, all the required data will be used from device tree dts | ||
file. | ||
|
||
Example: | ||
|
||
Step1: SoC common .dtsi file | ||
|
||
dcan1: d_can@481d0000 { | ||
compatible = "bosch,d_can"; | ||
reg = <0x481d0000 0x2000>; | ||
interrupts = <55>; | ||
interrupt-parent = <&intc>; | ||
status = "disabled"; | ||
}; | ||
|
||
(or) | ||
|
||
dcan1: d_can@481d0000 { | ||
compatible = "bosch,d_can"; | ||
ti,hwmods = "d_can1"; | ||
reg = <0x481d0000 0x2000>; | ||
interrupts = <55>; | ||
interrupt-parent = <&intc>; | ||
status = "disabled"; | ||
}; | ||
|
||
Step 2: board specific .dts file | ||
|
||
&dcan1 { | ||
status = "okay"; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters