97efe9aef1
If our CAN device's device tree node has a clock-frequency property, then use that value for the can devices clock frequency. If not, fall back to asking the platform/mach code for the clock frequency associated with the flexcan device. Signed-off-by: Robin Holt <holt@sgi.com> Acked-by: Wolfgang Grandegger <wg@grandegger.com>, Cc: Kumar Gala <galak@kernel.crashing.org> Cc: Marc Kleine-Budde <mkl@pengutronix.de>, Cc: U Bhaskar-B22300 <B22300@freescale.com> Cc: Scott Wood <scottwood@freescale.com> Cc: Grant Likely <grant.likely@secretlab.ca> Cc: socketcan-core@lists.berlios.de, Cc: netdev@vger.kernel.org, Cc: PPC list <linuxppc-dev@lists.ozlabs.org> Cc: devicetree-discuss@lists.ozlabs.org Signed-off-by: David S. Miller <davem@davemloft.net>
24 lines
679 B
Text
24 lines
679 B
Text
Flexcan CAN contoller on Freescale's ARM and PowerPC system-on-a-chip (SOC).
|
|
|
|
Required properties:
|
|
|
|
- compatible : Should be "fsl,<processor>-flexcan"
|
|
|
|
An implementation should also claim any of the following compatibles
|
|
that it is fully backwards compatible with:
|
|
|
|
- fsl,p1010-flexcan
|
|
|
|
- reg : Offset and length of the register set for this device
|
|
- interrupts : Interrupt tuple for this device
|
|
- clock-frequency : The oscillator frequency driving the flexcan device
|
|
|
|
Example:
|
|
|
|
can@1c000 {
|
|
compatible = "fsl,p1010-flexcan";
|
|
reg = <0x1c000 0x1000>;
|
|
interrupts = <48 0x2>;
|
|
interrupt-parent = <&mpic>;
|
|
clock-frequency = <200000000>; // filled in by bootloader
|
|
};
|