From: Geert Uytterhoeven Date: Wed, 23 Nov 2016 13:44:46 +0000 (+0100) Subject: can: rcar_canfd: Correct order of interrupt specifiers X-Git-Tag: v4.10-rc1~202^2~112^2~1 X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=commitdiff_plain;h=08469bba2852da651ce7a047495685c10164c63b;p=linux.git can: rcar_canfd: Correct order of interrupt specifiers According to both DTS (example and actual files), and Linux driver code, the first interrupt specifier should be the Channel interrupt, while the second interrupt specifier should be the Global interrupt. Signed-off-by: Geert Uytterhoeven Acked-by: Ramesh Shanmugasundaram Acked-by: Rob Herring Signed-off-by: Marc Kleine-Budde --- diff --git a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt index 788f2737a997..93c3a6ae32f9 100644 --- a/Documentation/devicetree/bindings/net/can/rcar_canfd.txt +++ b/Documentation/devicetree/bindings/net/can/rcar_canfd.txt @@ -12,7 +12,7 @@ Required properties: family-specific and/or generic versions. - reg: physical base address and size of the R-Car CAN FD register map. -- interrupts: interrupt specifier for the Global & Channel interrupts +- interrupts: interrupt specifiers for the Channel & Global interrupts - clocks: phandles and clock specifiers for 3 clock inputs. - clock-names: 3 clock input name strings: "fck", "canfd", "can_clk". - pinctrl-0: pin control group to be used for this controller.