From: <Arun.Ramadoss@microchip.com>
To: <andrew@lunn.ch>, <olteanv@gmail.com>, <davem@davemloft.net>,
<Woojung.Huh@microchip.com>, <pabeni@redhat.com>,
<o.rempel@pengutronix.de>, <edumazet@google.com>,
<f.fainelli@gmail.com>, <kuba@kernel.org>
Cc: <kernel@pengutronix.de>, <dsahern@kernel.org>, <san@skov.dk>,
<willemb@google.com>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <horms@kernel.org>,
<UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH net-next v3 7/9] net: dsa: microchip: enable ETS support for KSZ989X variants
Date: Mon, 8 Apr 2024 03:52:57 +0000 [thread overview]
Message-ID: <2d4afde2479cb7830c8add15a7df3d58db0dbb3c.camel@microchip.com> (raw)
In-Reply-To: <20240405095216.353829-8-o.rempel@pengutronix.de>
Hi Oleksij,
On Fri, 2024-04-05 at 11:52 +0200, Oleksij Rempel wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> I tested ETS support on KSZ9893, so it should work other KSZ989X
> variants too.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
nitpick: For the source code I infer ets support is support for all
switches except ksz8x family(KSZ8795/4, KSZ8765 and KSZ8830).
Instead of .tc_ets_supported, can we add in the ksz_tc_setup_qdisc_ets(
)
like
if( ksz8_family())
return -EOPNOTSUPP;
Otherwise
Acked-by: Arun Ramadoss <arun.ramadoss@microchip.com>
> ---
> drivers/net/dsa/microchip/ksz_common.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/dsa/microchip/ksz_common.c
> b/drivers/net/dsa/microchip/ksz_common.c
> index 840b17b8507e1..dc96931e62da8 100644
> --- a/drivers/net/dsa/microchip/ksz_common.c
> +++ b/drivers/net/dsa/microchip/ksz_common.c
> @@ -1378,6 +1378,7 @@ const struct ksz_chip_data ksz_switch_chips[] =
> {
> .port_nirqs = 2,
> .num_tx_queues = 4,
> .num_ipvs = 8,
> + .tc_ets_supported = true,
> .ops = &ksz9477_dev_ops,
> .mib_names = ksz9477_mib_names,
> .mib_cnt = ARRAY_SIZE(ksz9477_mib_names),
> @@ -1411,6 +1412,7 @@ const struct ksz_chip_data ksz_switch_chips[] =
> {
> .port_nirqs = 2,
> .num_tx_queues = 4,
> .num_ipvs = 8,
> + .tc_ets_supported = true,
> .ops = &ksz9477_dev_ops,
> .mib_names = ksz9477_mib_names,
> .mib_cnt = ARRAY_SIZE(ksz9477_mib_names),
> @@ -1442,6 +1444,7 @@ const struct ksz_chip_data ksz_switch_chips[] =
> {
> .port_nirqs = 2,
> .num_tx_queues = 4,
> .num_ipvs = 8,
> + .tc_ets_supported = true,
> .ops = &ksz9477_dev_ops,
> .mib_names = ksz9477_mib_names,
> .mib_cnt = ARRAY_SIZE(ksz9477_mib_names),
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-04-08 3:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 9:52 [PATCH net-next v3 0/9] Enhanced DCB and DSCP Support for KSZ Switches Oleksij Rempel
2024-04-05 9:52 ` [PATCH net-next v3 1/9] net: dsa: add support for DCB get/set apptrust configuration Oleksij Rempel
2024-04-05 9:52 ` [PATCH net-next v3 2/9] net: dsa: microchip: add IPV information support Oleksij Rempel
2024-04-05 9:52 ` [PATCH net-next v3 3/9] net: add IEEE 802.1q specific helpers Oleksij Rempel
2024-04-05 9:52 ` [PATCH net-next v3 4/9] net: dsa: microchip: add multi queue support for KSZ88X3 variants Oleksij Rempel
2024-04-05 9:52 ` [PATCH net-next v3 5/9] net: dsa: microchip: add support for different DCB app configurations Oleksij Rempel
2024-04-05 9:52 ` [PATCH net-next v3 6/9] net: dsa: microchip: dcb: add special handling for KSZ88X3 family Oleksij Rempel
2024-04-05 9:52 ` [PATCH net-next v3 7/9] net: dsa: microchip: enable ETS support for KSZ989X variants Oleksij Rempel
2024-04-08 3:52 ` Arun.Ramadoss [this message]
2024-04-05 9:52 ` [PATCH net-next v3 8/9] net: dsa: microchip: init predictable IPV to queue mapping for all non KSZ8xxx variants Oleksij Rempel
2024-04-08 3:41 ` Arun.Ramadoss
2024-04-08 5:00 ` Oleksij Rempel
2024-04-05 9:52 ` [PATCH net-next v3 9/9] net: dsa: microchip: let DCB code do PCP and DSCP policy configuration Oleksij Rempel
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=2d4afde2479cb7830c8add15a7df3d58db0dbb3c.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=san@skov.dk \
--cc=willemb@google.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