[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190708121023.GB17624@t480s.localdomain>
Date: Mon, 8 Jul 2019 12:10:23 -0400
From: Vivien Didelot <vivien.didelot@...il.com>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Vinicius Costa Gomes <vinicius.gomes@...el.com>,
vedang.patel@...el.com, Richard Cochran <richardcochran@...il.com>,
weifeng.voon@...el.com, jiri@...lanox.com, m-karicheri2@...com,
Jose.Abreu@...opsys.com, ilias.apalodimas@...aro.org,
netdev <netdev@...r.kernel.org>
Subject: Re: [RFC PATCH net-next 0/6] tc-taprio offload for SJA1105 DSA
On Sun, 7 Jul 2019 23:28:24 +0300, Vladimir Oltean <olteanv@...il.com> wrote:
> I thought the dsa_port_notify functions are just to be
> called from switchdev. I'm still not sure I fully understand, but I'll
> try to switch to that in v2 and see what happens.
dsa_port_notify is used to forward an event occuring on a given port, to
all switch chips of a fabric. For example when programming a VLAN on a port,
all ports interconnecting switches together must to programmed too. Even
though mainly switchdev objects or attributes are notified at the moment,
a DSA notification is not specific to switchdev.
Thanks,
Vivien
Powered by blists - more mailing lists