aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/net/can/rcar_can.txt
diff options
context:
space:
mode:
authorMarek Vasut <marex@denx.de>2016-03-03 20:45:58 +0100
committerMarc Kleine-Budde <mkl@pengutronix.de>2016-03-10 10:19:09 +0100
commit6cc6426605b7edabde41c72add723979d1d509e7 (patch)
treeeee67e46f22111dad939b2ea5d40d8b3312e2fc9 /Documentation/devicetree/bindings/net/can/rcar_can.txt
parentcan: ifi: Fix RX and TX ID mask (diff)
downloadlinux-dev-6cc6426605b7edabde41c72add723979d1d509e7.tar.xz
linux-dev-6cc6426605b7edabde41c72add723979d1d509e7.zip
can: ifi: Add obscure bit swap for EFF frame IDs
In case of CAN2.0 EFF frame, the controller handles frame IDs in a rather bizzare way. The ID is split into an extended part, IDX[28:11] and standard part, ID[10:0]. In the TX path, the core first sends the top 11 bits of the IDX, followed by ID and finally the rest of IDX. In the RX path, the core stores the ID the LSbit part of IDX field, followed by the LSbit parts of real IDX. The MSbit parts of IDX are stored in ID field of the register. This patch implements the necessary bit shuffling to mitigate this obscure behavior. In case two of these controllers are connected together, the RX and TX bit swapping nullifies itself and the issue does not manifest. The issue only manifests when talking to another different CAN controller. Signed-off-by: Marek Vasut <marex@denx.de> Cc: Marc Kleine-Budde <mkl@pengutronix.de> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Oliver Hartkopp <socketcan@hartkopp.net> Cc: Wolfgang Grandegger <wg@grandegger.com> Reviewed-by: Oliver Hartkopp <socketcan@hartkopp.net> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'Documentation/devicetree/bindings/net/can/rcar_can.txt')
0 files changed, 0 insertions, 0 deletions