[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191119151221.14ff2d28@cakuba.netronome.com>
Date: Tue, 19 Nov 2019 15:12:21 -0800
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: <netdev@...r.kernel.org>,
Ilias Apalodimas <ilias.apalodimas@...aro.org>,
Andrew Lunn <andrew@...n.ch>,
"David S . Miller" <davem@...emloft.net>,
Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>,
Jiri Pirko <jiri@...nulli.us>,
Florian Fainelli <f.fainelli@...il.com>,
Sekhar Nori <nsekhar@...com>, <linux-kernel@...r.kernel.org>,
<linux-omap@...r.kernel.org>,
Murali Karicheri <m-karicheri2@...com>,
Ivan Vecera <ivecera@...hat.com>,
Rob Herring <robh+dt@...nel.org>, <devicetree@...r.kernel.org>
Subject: Re: [PATCH v7 net-next 07/13] net: ethernet: ti: introduce cpsw
switchdev based driver part 1 - dual-emac
On Wed, 20 Nov 2019 00:19:19 +0200, Grygorii Strashko wrote:
> From: Ilias Apalodimas <ilias.apalodimas@...aro.org>
>
> Part 1:
> Introduce basic CPSW dual_mac driver (cpsw_new.c) which is operating in
> dual-emac mode by default, thus working as 2 individual network interfaces.
> Main differences from legacy CPSW driver are:
>
> - optimized promiscuous mode: The P0_UNI_FLOOD (both ports) is enabled in
> addition to ALLMULTI (current port) instead of ALE_BYPASS. So, Ports in
> promiscuous mode will keep possibility of mcast and vlan filtering, which
> is provides significant benefits when ports are joined to the same bridge,
> but without enabling "switch" mode, or to different bridges.
> - learning disabled on ports as it make not too much sense for
> segregated ports - no forwarding in HW.
> - enabled basic support for devlink.
>
> devlink dev show
> platform/48484000.switch
>
> devlink dev param show
> platform/48484000.switch:
> name ale_bypass type driver-specific
> values:
> cmode runtime value false
>
> - "ale_bypass" devlink driver parameter allows to enable
> ALE_CONTROL(4).BYPASS mode for debug purposes.
> - updated DT bindings.
Could you please add documentation for the devlink parameter under
Documentation/networking/devlink-params-* ?
Powered by blists - more mailing lists