public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
	"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
	"andrew@lunn.ch" <andrew@lunn.ch>
Subject: Re: [PATCH net-next v3 5/6] net: lan966x: Add vlan support
Date: Thu, 9 Dec 2021 13:59:28 +0000	[thread overview]
Message-ID: <20211209135928.25myffd3xzcnmndl@skbuf> (raw)
In-Reply-To: <20211209094615.329379-6-horatiu.vultur@microchip.com>

On Thu, Dec 09, 2021 at 10:46:14AM +0100, Horatiu Vultur wrote:
> +int lan966x_vlan_port_set_vid(struct lan966x_port *port, u16 vid,
> +			      bool pvid, bool untagged)
> +{
> +	struct lan966x *lan966x = port->lan966x;
> +
> +	/* Egress vlan classification */
> +	if (untagged && port->vid != vid) {
> +		if (port->vid) {
> +			dev_err(lan966x->dev,
> +				"Port already has a native VLAN: %d\n",
> +				port->vid);
> +			return -EBUSY;

Are you interested in supporting the use case from 0da1a1c48911 ("net:
mscc: ocelot: allow a config where all bridge VLANs are egress-untagged")?
Because it would be good if the driver was structured that way from the
get-go instead of patching it later.

> +		}
> +		port->vid = vid;
> +	}
> +
> +	/* Default ingress vlan classification */
> +	if (pvid)
> +		port->pvid = vid;
> +
> +	return 0;
> +}

  reply	other threads:[~2021-12-09 13:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09  9:46 [PATCH net-next v3 0/6] net: lan966x: Add switchdev and vlan support Horatiu Vultur
2021-12-09  9:46 ` [PATCH net-next v3 1/6] net: lan966x: Add registers that are used for switch and vlan functionality Horatiu Vultur
2021-12-09  9:46 ` [PATCH net-next v3 2/6] dt-bindings: net: lan966x: Extend with the analyzer interrupt Horatiu Vultur
2021-12-09 10:58   ` Vladimir Oltean
2021-12-09 15:42     ` Horatiu Vultur
2021-12-09 20:23       ` Vladimir Oltean
2021-12-09  9:46 ` [PATCH net-next v3 3/6] net: lan966x: add support for interrupts from analyzer Horatiu Vultur
2021-12-09 11:47   ` Vladimir Oltean
2021-12-09 15:38     ` Horatiu Vultur
2021-12-09  9:46 ` [PATCH net-next v3 4/6] net: lan966x: More MAC table functionality Horatiu Vultur
2021-12-09  9:46 ` [PATCH net-next v3 5/6] net: lan966x: Add vlan support Horatiu Vultur
2021-12-09 13:59   ` Vladimir Oltean [this message]
2021-12-09 15:47     ` Horatiu Vultur
2021-12-09  9:46 ` [PATCH net-next v3 6/6] net: lan966x: Add switchdev support Horatiu Vultur
2021-12-09 13:36   ` Vladimir Oltean
2021-12-09 16:43     ` Horatiu Vultur
2021-12-13 10:25       ` Horatiu Vultur
2021-12-13 13:43         ` Vladimir Oltean
2021-12-13 14:26           ` Horatiu Vultur
2021-12-13 14:29             ` Vladimir Oltean
2021-12-13 15:28               ` Horatiu Vultur
2021-12-13 16:25                 ` Vladimir Oltean
2021-12-13 21:24                   ` Horatiu Vultur
2021-12-14  0:01                     ` Vladimir Oltean
2021-12-14 14:31                       ` Horatiu Vultur
2021-12-15  9:27                         ` Vladimir Oltean
2021-12-13 11:46       ` Vladimir Oltean
2021-12-13 13:37         ` Horatiu Vultur

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=20211209135928.25myffd3xzcnmndl@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vivien.didelot@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox