net: mvpp2: Handle eth device naming in multi-CP case correctly
authorStefan Roese <sr@denx.de>
Fri, 24 Feb 2017 09:12:41 +0000 (10:12 +0100)
committerStefan Roese <sr@denx.de>
Wed, 29 Mar 2017 05:42:33 +0000 (07:42 +0200)
commitc9607c932585e6757ad1c378751030c2a4234227
treef04773c2ca73219bb834641e87b6c73625464fe5
parentdef844299cfbe65a625ace8d724e92063f3fce9f
net: mvpp2: Handle eth device naming in multi-CP case correctly

Currently, the naming of the ethernet ports is not handled correctly in
the multi-CP (Communication Processor) case. On Armada 8k, the slave-CP
also instantiates an ethernet controller with the same device ID's.
This patch now takes this into account and adds the required base-id
so that the slave-CP ethernet devices will be named "mvpp2-3 ...".

This patch also updates my Copyright notice to include 2017 as well.

Signed-off-by: Stefan Roese <sr@denx.de>
Cc: Stefan Chulski <stefanc@marvell.com>
Cc: Kostya Porotchkin <kostap@marvell.com>
Cc: Nadav Haklai <nadavh@marvell.com>
Acked-by: Joe Hershberger <joe.hershberger@ni.com>
drivers/net/mvpp2.c