diff options
| author | Vivien Didelot | 2017-05-01 20:05:17 +0200 |
|---|---|---|
| committer | David S. Miller | 2017-05-01 21:03:10 +0200 |
| commit | f169e5ee5f29f81c1c8d647fa6fb5387ee793131 (patch) | |
| tree | 9f7efbcd86248fd6d044ccac52cfb4c76efe3655 /drivers/net/dsa/bcm_sf2.h | |
| parent | net: dsa: mv88e6xxx: move VTU VID accessors (diff) | |
| download | kernel-qcow2-linux-f169e5ee5f29f81c1c8d647fa6fb5387ee793131.tar.gz kernel-qcow2-linux-f169e5ee5f29f81c1c8d647fa6fb5387ee793131.tar.xz kernel-qcow2-linux-f169e5ee5f29f81c1c8d647fa6fb5387ee793131.zip | |
net: dsa: mv88e6xxx: move generic VTU GetNext
Even though every switch model has a different way to access the VTU
Data bits, the base implementation of the VTU GetNext operation remains
the same: wait, write the first VID to iterate from, start the
operation, and read the next VID.
Move this generic implementation into global1_vtu.c and abstract the
handling of the start VID (similarly to the ATU GetNext implementation),
before introducing a new chip operation for specific chips.
Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/dsa/bcm_sf2.h')
0 files changed, 0 insertions, 0 deletions