From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: andrew@lunn.ch, vivien.didelot@savoirfairelinux.com,
john@phrozen.org, davem@davemloft.net,
Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH net-next v2 0/5] net: dsa: Multi-CPU ground work (v2)
Date: Tue, 6 Jun 2017 17:03:12 -0700 [thread overview]
Message-ID: <20170607000317.14729-1-f.fainelli@gmail.com> (raw)
Hi all,
This patch series prepares the ground for adding mutliple CPU port support to
DSA, and starts by removing redundant pieces of information such as
master_netdev which is cpu_dp->ethernet. Finally drivers are moved away from
directly accessing ds->dst->cpu_dp and use appropriate helper functions.
Note that if you have Device Tree blobs/platform configurations that are
currently listing multiple CPU ports, the proposed behavior in
dsa_ds_get_cpu_dp() will be to return the last bit set in ds->cpu_port_mask.
Future plans include:
- making dst->cpu_dp a flexible data structure (array, list, you name it)
- having the ability for drivers to return a default/preferred CPU port (if
necessary)
Changes in v2:
- added Reviewed-by tags
- assign port->cpu_dp earlier before ops->setup() has run
Florian Fainelli (5):
net: dsa: Remove master_netdev and use dst->cpu_dp->netdev
net: dsa: Relocate master ethtool operations
net: dsa: Associate slave network device with CPU port
net: dsa: Introduce dsa_dst_get_cpu_dp()
net: dsa: Stop accessing ds->dst->cpu_dp in drivers
drivers/net/dsa/b53/b53_common.c | 4 +--
drivers/net/dsa/bcm_sf2.c | 10 +++++---
drivers/net/dsa/mt7530.c | 6 +++--
drivers/net/dsa/mv88e6060.c | 2 +-
drivers/net/dsa/qca8k.c | 2 +-
include/net/dsa.h | 29 +++++++++-------------
net/dsa/dsa.c | 19 ++++----------
net/dsa/dsa2.c | 27 ++++++++++++--------
net/dsa/dsa_priv.h | 10 ++++++++
net/dsa/legacy.c | 23 ++++++++++-------
net/dsa/slave.c | 53 ++++++++++++++++++++--------------------
net/dsa/tag_brcm.c | 5 ++--
net/dsa/tag_ksz.c | 5 ++--
net/dsa/tag_qca.c | 3 ++-
net/dsa/tag_trailer.c | 5 ++--
15 files changed, 107 insertions(+), 96 deletions(-)
--
2.9.3
next reply other threads:[~2017-06-07 0:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 0:03 Florian Fainelli [this message]
2017-06-07 0:03 ` [PATCH net-next v2 1/5] net: dsa: Remove master_netdev and use dst->cpu_dp->netdev Florian Fainelli
2017-06-07 2:15 ` Vivien Didelot
2017-06-07 0:03 ` [PATCH net-next v2 2/5] net: dsa: Relocate master ethtool operations Florian Fainelli
2017-06-07 0:03 ` [PATCH net-next v2 3/5] net: dsa: Associate slave network device with CPU port Florian Fainelli
2017-06-07 0:03 ` [PATCH net-next v2 4/5] net: dsa: Introduce dsa_dst_get_cpu_dp() Florian Fainelli
2017-06-07 0:03 ` [PATCH net-next v2 5/5] net: dsa: Stop accessing ds->dst->cpu_dp in drivers Florian Fainelli
2017-06-07 2:11 ` Vivien Didelot
2017-06-07 2:38 ` Florian Fainelli
2017-06-07 17:15 ` Vivien Didelot
2017-06-07 19:21 ` Florian Fainelli
2017-06-07 19:27 ` Vivien Didelot
2017-06-07 23:24 ` Vivien Didelot
2017-06-08 0:27 ` Florian Fainelli
2017-06-08 1:03 ` Vivien Didelot
2017-06-07 0:05 ` [PATCH net-next v2 0/5] net: dsa: Multi-CPU ground work (v2) Florian Fainelli
2017-06-07 2:13 ` Vivien Didelot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170607000317.14729-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=john@phrozen.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).