linux-toradex.git/Documentation/devicetree/bindings/net/can, branch v4.10

can: rcar_canfd: Correct order of interrupt specifiers

2016-12-01T13:27:02+00:00

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

can: rcar_canfd: Add r8a7796 support

2016-12-01T13:27:01+00:00

Signed-off-by: Chris Paterson 
Reviewed-by: Geert Uytterhoeven 
Acked-by: Marc Kleine-Budde 
Acked-by: Rob Herring 
Signed-off-by: Marc Kleine-Budde

can: rcar_can: Add r8a7796 support

2016-12-01T13:26:57+00:00

Signed-off-by: Chris Paterson 
Reviewed-by: Geert Uytterhoeven 
Acked-by: Marc Kleine-Budde 
Acked-by: Rob Herring 
Signed-off-by: Marc Kleine-Budde

can: rcar_canfd: Add Classical CAN only mode support

2016-06-23T09:23:49+00:00

The controller can operate in one of the two global modes
 - CAN FD only mode (default)
 - Classical CAN (CAN2.0) only mode

This patch adds support for Classical CAN only mode. It can be enabled
by defining the optional device tree property "renesas,no-can-fd" of this
node.

Note: R-Car Gen3 h/w manual v0.51E shows bit6 of RSCFDnCFDGCFG as
reserved, which is incorrect. This bit is same as RSCFDnGCFG.

Signed-off-by: Ramesh Shanmugasundaram 
Signed-off-by: Marc Kleine-Budde

can: rcar_canfd: Add Renesas R-Car CAN FD driver

2016-06-17T13:39:47+00:00

This patch adds support for the CAN FD controller found in Renesas R-Car
SoCs. The controller operates in CAN FD only mode by default.

CAN FD mode supports both Classical CAN & CAN FD frame formats. The
controller supports ISO 11898-1:2015 CAN FD format only.

This controller supports two channels and the driver can enable either
or both of the channels.

Driver uses Rx FIFOs (one per channel) for reception & Common FIFOs (one
per channel) for transmission. Rx filter rules are configured to the
minimum (one per channel) and it accepts Standard, Extended, Data &
Remote Frame combinations.

Note: There are few documentation errors in R-Car Gen3 Hardware User
Manual v0.5E with respect to CAN FD controller. They are listed below:

1. CAN FD interrupt numbers 29 & 30 are listed as per channel
interrupts. However, they are common to both channels (i.e.) they are
global and channel interrupts respectively.

2. CANFD clock is derived from PLL1. This is not documented.

3. CANFD clock is further divided by (1/2) within the CAN FD controller.
This is not documented.

4. The minimum value of NTSEG1 in RSCFDnCFDCmNCFG register is 2 Tq. It
is specified 4 Tq in the manual.

5. The maximum number of message RAM area the controller can use is 3584
bytes. It is specified 10752 bytes in the manual.

Signed-off-by: Ramesh Shanmugasundaram 
Acked-by: Rob Herring 
Reviewed-by: Ulrich Hecht 
Signed-off-by: Marc Kleine-Budde

can: rcar_can: Add r8a7795 support

2016-03-10T09:30:21+00:00

Added r8a7795 SoC support.

Signed-off-by: Ramesh Shanmugasundaram 
Acked-by: Rob Herring 
Signed-off-by: Marc Kleine-Budde

can: rcar: add device tree support for r8a779[234]

2016-02-26T07:43:34+00:00

Simply document new compatibility string.
As a previous patch adds a generic R-Car Gen2 compatibility string
there appears to be no need for a driver updates.

By documenting these compat stings they may be used in DTSs shipped, for
example as part of ROMs. They must be used in conjunction with the Gen2
fallback compat string. At this time there are no known differences between
the r8a779[234] IP blocks and that implemented by the driver for the Gen2
fallback compat string. Thus there is no need to update the driver as the
use of the Gen2 fallback compat string will activate the correct code in
the current driver while leaving the option for r8a779[234]-specific driver
code to be activated in an updated driver should the need arise.

Signed-off-by: Simon Horman 
Acked-by: Geert Uytterhoeven 
Signed-off-by: Marc Kleine-Budde

can: rcar: add gen[12] fallback compatibility strings

2016-02-26T07:43:18+00:00

Add fallback compatibility string for R-Car Gen 1 and Gen2.

In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 1 and Gen 2. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7779 is older than r8a7778 but that doesn't imply that the latter is a
descendant of the former or vice versa.

We can, however, by examining the documentation and behaviour of the
hardware at run-time observe that the current driver implementation appears
to be compatible with the IP blocks on SoCs within a given generation.

For the above reasons and convenience when enabling new SoCs a
per-generation fallback compatibility string scheme being adopted for
drivers for Renesas SoCs.

Signed-off-by: Simon Horman 
Acked-by: Rob Herring 
Acked-by: Geert Uytterhoeven 
Signed-off-by: Marc Kleine-Budde

can: ifi: Add DT bindings for ifi,canfd

2016-02-20T13:56:00+00:00

Add device tree bindings for the I/F/I CANFD controller IP core.

Signed-off-by: Marek Vasut 
Cc: Marc Kleine-Budde 
Cc: Mark Rutland 
Cc: Oliver Hartkopp 
Cc: Wolfgang Grandegger 
Signed-off-by: Marc Kleine-Budde

can: sja1000: add documentation for Technologic Systems version

2016-02-20T13:56:00+00:00

This commit adds documentation for the Technologic Systems version of
SJA1000. The difference with the NXP version is in the way the registers
are accessed.

Signed-off-by: Damien Riegel 
Signed-off-by: Marc Kleine-Budde