From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCHv2 net-next 3/4] net: dsa: mv88e6xxx: Move the tagging protocol into info
Date: Fri, 02 Dec 2016 14:41:08 -0500 [thread overview]
Message-ID: <87k2bice5n.fsf@ketchup.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <1480701779-30633-4-git-send-email-andrew@lunn.ch>
Hi Andrew,
Andrew Lunn <andrew@lunn.ch> writes:
> @@ -3749,6 +3756,7 @@ static const struct mv88e6xxx_info mv88e6xxx_table[] = {
> .global1_addr = 0x1b,
> .age_time_coeff = 15000,
> .g1_irqs = 9,
> + .tag_protocol = DSA_TAG_PROTO_EDSA,
> .flags = MV88E6XXX_FLAGS_FAMILY_6352,
> .ops = &mv88e6172_ops,
> },
Since some chips support several protocols, we will have to turn
tag_protocol into a bitmask and introduce something like:
enum mv88e6xxx_tag {
MV88E6XXX_TAG_TRAILER = BIT(DSA_TAG_PROTO_TRAILER),
MV88E6XXX_TAG_DSA = BIT(DSA_TAG_PROTO_DSA),
MV88E6XXX_TAG_EDSA = BIT(DSA_TAG_PROTO_EDSA),
};
But I guess it is OK to force a single one at the moment.
Reviewed-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Thanks,
Vivien
next prev parent reply other threads:[~2016-12-02 19:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 18:02 [PATCHv2 net-next 0/4] MV88E6390 batch two Andrew Lunn
2016-12-02 18:02 ` [PATCHv2 net-next 1/4] net: dsa: mv88e6xxx: Implement mv88e6390 tag remap Andrew Lunn
2016-12-02 19:15 ` Vivien Didelot
2016-12-02 18:02 ` [PATCHv2 net-next 2/4] net: dsa: mv88e6xxx: Monitor and Management tables Andrew Lunn
2016-12-02 19:32 ` Vivien Didelot
2016-12-02 20:56 ` Andrew Lunn
2016-12-02 21:53 ` Vivien Didelot
2016-12-02 18:02 ` [PATCHv2 net-next 3/4] net: dsa: mv88e6xxx: Move the tagging protocol into info Andrew Lunn
2016-12-02 19:41 ` Vivien Didelot [this message]
2016-12-02 21:02 ` Andrew Lunn
2016-12-02 18:02 ` [PATCHv2 net-next 4/4] net: dsa: mv88e6xxx: Refactor CPU and DSA port setup Andrew Lunn
2016-12-02 21:02 ` Vivien Didelot
2016-12-02 21:18 ` Andrew Lunn
2016-12-02 22:03 ` 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=87k2bice5n.fsf@ketchup.i-did-not-set--mail-host-address--so-tickle-me \
--to=vivien.didelot@savoirfairelinux.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.