From: Grygorii Strashko <email@example.com> To: Jakub Kicinski <firstname.lastname@example.org> Cc: "David S. Miller" <email@example.com>, <firstname.lastname@example.org>, Vignesh Raghavendra <email@example.com>, Sekhar Nori <firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>, Murali Karicheri <email@example.com> Subject: Re: [PATCH net-next 0/8] net: ethernet: ti: am65-cpsw: add multi port support in mac-only mode Date: Mon, 5 Oct 2020 13:16:34 +0300 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 03/10/2020 02:07, Jakub Kicinski wrote: > On Fri, 2 Oct 2020 16:04:21 -0700 Jakub Kicinski wrote: >> On Fri, 2 Oct 2020 12:56:43 +0300 Grygorii Strashko wrote: >>> On 02/10/2020 02:08, Jakub Kicinski wrote: >>>> On Thu, 1 Oct 2020 13:52:50 +0300 Grygorii Strashko wrote: >>>>> This series adds multi-port support in mac-only mode (multi MAC mode) to TI >>>>> AM65x CPSW driver in preparation for enabling support for multi-port devices, >>>>> like Main CPSW0 on K3 J721E SoC or future CPSW3g on K3 AM64x SoC. >>>>> >>>>> The multi MAC mode is implemented by configuring every enabled port in "mac-only" >>>>> mode (all ingress packets are sent only to the Host port and egress packets >>>>> directed to target Ext. Port) and creating separate net_device for >>>>> every enabled Ext. port. >>>> >>>> Do I get it right that you select the mode based on platform? Can the >>>> other mode still be supported on these platforms? >>>> >>>> Is this a transition to normal DSA mode where ports always have netdevs? >>> >>> The idea here is to start in multi mac mode by default, as we still >>> have pretty high demand for this. Then, and we are working on it, the >>> switchdev mode is going to be introduces (not DSA). The switch >>> between modes will happen by using devlink option - the approach is >>> similar to what was used for Sitara CPSW cpsw_new.c driver . >> >> What's unclear from the patches is whether the default configuration >> for already supported platforms will change? >> >> All the patches sound like they are "in preparation for support of K3 >> J721E" etc. So this is just code restructuring with no user-visible >> changes? > > Another way of putting the question perhaps would be - is num_ports > always 1 for existing platforms? > Yes. Sorry for confusion - all now supported K3 CPSW instances have 1 external port and these changes should not have affect on them. -- Best regards, grygorii
prev parent reply other threads:[~2020-10-05 10:16 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-01 10:52 Grygorii Strashko 2020-10-01 10:52 ` [PATCH net-next 1/8] net: ethernet: ti: am65-cpsw: move ale selection in pdata Grygorii Strashko 2020-10-01 10:52 ` [PATCH net-next 2/8] net: ethernet: ti: am65-cpsw: move free desc queue mode " Grygorii Strashko 2020-10-01 10:52 ` [PATCH net-next 3/8] net: ethernet: ti: am65-cpsw: use cppi5_desc_is_tdcm() Grygorii Strashko 2020-10-01 10:52 ` [PATCH net-next 4/8] net: ethernet: ti: cpsw_ale: add cpsw_ale_vlan_del_modify() Grygorii Strashko 2020-10-01 10:52 ` [PATCH net-next 5/8] net: ethernet: ti: am65-cpsw: fix vlan offload for multi mac mode Grygorii Strashko 2020-10-01 10:52 ` [PATCH net-next 6/8] net: ethernet: ti: am65-cpsw: keep active if cpts enabled Grygorii Strashko 2020-10-01 10:52 ` [PATCH net-next 7/8] net: ethernet: ti: am65-cpsw: prepare xmit/rx path for multi-port devices in mac-only mode Grygorii Strashko 2020-10-03 2:09 ` David Miller 2020-10-05 10:28 ` Grygorii Strashko 2020-10-01 10:52 ` [PATCH net-next 8/8] net: ethernet: ti: am65-cpsw: add multi port support " Grygorii Strashko 2020-10-01 23:08 ` [PATCH net-next 0/8] " Jakub Kicinski 2020-10-02 9:56 ` Grygorii Strashko 2020-10-02 23:04 ` Jakub Kicinski 2020-10-02 23:07 ` Jakub Kicinski 2020-10-05 10:16 ` Grygorii Strashko [this message]
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH net-next 0/8] net: ethernet: ti: am65-cpsw: add multi port support in mac-only mode' \ /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
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).