aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/net
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2016-06-27 10:33:42 -0400
committerDavid S. Miller <davem@davemloft.net>2016-06-27 10:33:42 -0400
commit5db15872c5370d9ae7b1d1c972a48b598b23b824 (patch)
treedb81d20ce48b13b5e781785bed40f493c9b2409c /Documentation/devicetree/bindings/net
parent810bf11033637a2069952afb9c37f3afd3bbfe41 (diff)
parentb63f69d0fc1fa1e25842a2266633862d523c380f (diff)
Merge tag 'linux-can-next-for-4.8-20160623' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next
Marc Kleine-Budde says: ==================== pull-request: can-next 2016-06-17 this is a pull request of 4 patches for net-next/master. Arnd Bergmann's patch fixes a regresseion in af_can introduced in linux-can-next-for-4.8-20160617. There are two patches by Ramesh Shanmugasundaram, which add CAN-2.0 support to the rcar_canfd driver. And a patch by Ed Spiridonov that adds better error diagnoses messages to the Ed Spiridonov driver. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/devicetree/bindings/net')
-rw-r--r--Documentation/devicetree/bindings/net/can/rcar_canfd.txt21
1 files changed, 14 insertions, 7 deletions
diff --git a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
index d45182bd21dd..22a6f10bab05 100644
--- a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
+++ b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt
@@ -32,6 +32,12 @@ below properties.
32- assigned-clocks: phandle of canfd clock. 32- assigned-clocks: phandle of canfd clock.
33- assigned-clock-rates: maximum frequency of this clock. 33- assigned-clock-rates: maximum frequency of this clock.
34 34
35Optional property:
36The controller can operate in either CAN FD only mode (default) or
37Classical CAN only mode. The mode is global to both the channels. In order to
38enable the later, define the following optional property.
39 - renesas,no-can-fd: puts the controller in Classical CAN only mode.
40
35Example 41Example
36------- 42-------
37 43
@@ -63,12 +69,13 @@ SoC common .dtsi file:
63 69
64Board specific .dts file: 70Board specific .dts file:
65 71
66E.g. below enables Channel 1 alone in the board. 72E.g. below enables Channel 1 alone in the board in Classical CAN only mode.
67 73
68&canfd { 74&canfd {
69 pinctrl-0 = <&canfd1_pins>; 75 pinctrl-0 = <&canfd1_pins>;
70 pinctrl-names = "default"; 76 pinctrl-names = "default";
71 status = "okay"; 77 renesas,no-can-fd;
78 status = "okay";
72 79
73 channel1 { 80 channel1 {
74 status = "okay"; 81 status = "okay";
@@ -79,9 +86,9 @@ E.g. below enables Channel 0 alone in the board using External clock
79as fCAN clock. 86as fCAN clock.
80 87
81&canfd { 88&canfd {
82 pinctrl-0 = <&canfd0_pins &can_clk_pins>; 89 pinctrl-0 = <&canfd0_pins &can_clk_pins>;
83 pinctrl-names = "default"; 90 pinctrl-names = "default";
84 status = "okay"; 91 status = "okay";
85 92
86 channel0 { 93 channel0 {
87 status = "okay"; 94 status = "okay";