From: Vignesh Raghavendra <vigneshr@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Jonathan Corbet <corbet@lwn.net>, Jiri Pirko <jiri@nvidia.com>,
<netdev@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] net: ti: am65-cpsw-nuss: Add devlink support
Date: Thu, 3 Dec 2020 14:10:48 +0530 [thread overview]
Message-ID: <cc7fe740-1002-f1b9-8136-e1ba60cf2541@ti.com> (raw)
In-Reply-To: <20201130155044.GE2073444@lunn.ch>
Hi Andrew,
On 11/30/20 9:20 PM, Andrew Lunn wrote:
> On Mon, Nov 30, 2020 at 01:50:43PM +0530, Vignesh Raghavendra wrote:
>> AM65 NUSS ethernet switch on K3 devices can be configured to work either
>> in independent mac mode where each port acts as independent network
>> interface (multi mac) or switch mode.
>>
>> Add devlink hooks to provide a way to switch b/w these modes.
>
> Hi Vignesh
>
> What is not clear is why you need this? Ports are independent anyway
> until you add them to a bridge when using switchdev.
>
Default use case is to support multiple independent ports with no
switching. Users can either use software bridge with multi-mac
configuration or HW bridge for switch functionality. devlink hook
enables users to select Hw supported switch functionality. We don't want
to enable HW based switch support unless explicitly asked by user.
This also matches previous generation of devices (DRA7xx and AM57xx)
supported under drivers/net/ethernet/ti/cpsw_new.c
In general, devlink will also be used to configure few more parameters
(in addition to switch mode) such as host port in ALE_BYPASS mode (to
allow all packets to be routed to host) etc.
Regards
Vignesh
WARNING: multiple messages have this Message-ID (diff)
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Jonathan Corbet <corbet@lwn.net>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Jiri Pirko <jiri@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] net: ti: am65-cpsw-nuss: Add devlink support
Date: Thu, 3 Dec 2020 14:10:48 +0530 [thread overview]
Message-ID: <cc7fe740-1002-f1b9-8136-e1ba60cf2541@ti.com> (raw)
In-Reply-To: <20201130155044.GE2073444@lunn.ch>
Hi Andrew,
On 11/30/20 9:20 PM, Andrew Lunn wrote:
> On Mon, Nov 30, 2020 at 01:50:43PM +0530, Vignesh Raghavendra wrote:
>> AM65 NUSS ethernet switch on K3 devices can be configured to work either
>> in independent mac mode where each port acts as independent network
>> interface (multi mac) or switch mode.
>>
>> Add devlink hooks to provide a way to switch b/w these modes.
>
> Hi Vignesh
>
> What is not clear is why you need this? Ports are independent anyway
> until you add them to a bridge when using switchdev.
>
Default use case is to support multiple independent ports with no
switching. Users can either use software bridge with multi-mac
configuration or HW bridge for switch functionality. devlink hook
enables users to select Hw supported switch functionality. We don't want
to enable HW based switch support unless explicitly asked by user.
This also matches previous generation of devices (DRA7xx and AM57xx)
supported under drivers/net/ethernet/ti/cpsw_new.c
In general, devlink will also be used to configure few more parameters
(in addition to switch mode) such as host port in ALE_BYPASS mode (to
allow all packets to be routed to host) etc.
Regards
Vignesh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-03 8:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 8:20 [PATCH 0/4] net: ti: am65-cpsw-nuss: Add switchdev driver Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
2020-11-30 8:20 ` [PATCH 1/4] net: ti: am65-cpsw-nuss: Add devlink support Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
2020-11-30 15:50 ` Andrew Lunn
2020-11-30 15:50 ` Andrew Lunn
2020-12-03 8:40 ` Vignesh Raghavendra [this message]
2020-12-03 8:40 ` Vignesh Raghavendra
2020-12-03 14:18 ` Andrew Lunn
2020-12-03 14:18 ` Andrew Lunn
2020-12-03 16:22 ` Grygorii Strashko
2020-12-03 16:22 ` Grygorii Strashko
2020-11-30 8:20 ` [PATCH 2/4] net: ti: am65-cpsw-nuss: Add netdevice notifiers Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
2020-11-30 8:20 ` [PATCH 3/4] net: ti: am65-cpsw-nuss: Add switchdev support Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
2020-11-30 17:20 ` Andrew Lunn
2020-11-30 17:20 ` Andrew Lunn
2020-12-03 13:49 ` Vignesh Raghavendra
2020-12-03 13:49 ` Vignesh Raghavendra
2020-11-30 8:20 ` [PATCH 4/4] docs: networking: ti: Add driver doc for AM65 NUSS switch driver Vignesh Raghavendra
2020-11-30 8:20 ` Vignesh Raghavendra
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=cc7fe740-1002-f1b9-8136-e1ba60cf2541@ti.com \
--to=vigneshr@ti.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.