From: Vladimir Oltean <olteanv@gmail.com>
To: Prasanna Vengateshan <prasanna.vengateshan@microchip.com>
Cc: andrew@lunn.ch, netdev@vger.kernel.org, robh+dt@kernel.org,
UNGLinuxDriver@microchip.com, woojung.huh@microchip.com,
hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
devicetree@vger.kernel.org, pabeni@redhat.com
Subject: Re: [RFC PATCH v11 net-next 05/10] net: dsa: microchip: add DSA support for microchip lan937x
Date: Sat, 9 Apr 2022 02:25:57 +0300 [thread overview]
Message-ID: <20220408232557.b62l3lksotq5vuvm@skbuf> (raw)
In-Reply-To: <20220325165341.791013-6-prasanna.vengateshan@microchip.com>
On Fri, Mar 25, 2022 at 10:23:36PM +0530, Prasanna Vengateshan wrote:
> +static void lan937x_r_mib_stats64(struct ksz_device *dev, int port)
> +{
> + struct ksz_port_mib *mib = &dev->ports[port].mib;
> + struct rtnl_link_stats64 *s;
> + u64 *ctr = mib->counters;
> +
> + s = &mib->stats64;
> + spin_lock(&mib->stats64_lock);
I haven't looked at further patches yet to see if the situation improves
or not, but right now, this spin lock is useless, as you do not
implement .get_stats64.
> +
> + s->rx_packets = ctr[lan937x_mib_rx_mcast] +
> + ctr[lan937x_mib_rx_bcast] +
> + ctr[lan937x_mib_rx_ucast] +
> + ctr[lan937x_mib_rx_pause];
> +
> + s->tx_packets = ctr[lan937x_mib_tx_mcast] +
> + ctr[lan937x_mib_tx_bcast] +
> + ctr[lan937x_mib_tx_ucast] +
> + ctr[lan937x_mib_tx_pause];
> +
> + s->rx_bytes = ctr[lan937x_mib_rx_total];
> + s->tx_bytes = ctr[lan937x_mib_tx_total];
> +
> + s->rx_errors = ctr[lan937x_mib_rx_fragments] +
> + ctr[lan937x_mib_rx_jabbers] +
> + ctr[lan937x_mib_rx_sym_err] +
> + ctr[lan937x_mib_rx_align_err] +
> + ctr[lan937x_mib_rx_crc_err];
> +
> + s->tx_errors = ctr[lan937x_mib_tx_exc_col] +
> + ctr[lan937x_mib_tx_late_col];
> +
> + s->rx_dropped = ctr[lan937x_mib_rx_discard];
> + s->tx_dropped = ctr[lan937x_mib_tx_discard];
> + s->multicast = ctr[lan937x_mib_rx_mcast];
> +
> + s->collisions = ctr[lan937x_mib_tx_late_col] +
> + ctr[lan937x_mib_tx_single_col] +
> + ctr[lan937x_mib_tx_mult_col];
> +
> + s->rx_length_errors = ctr[lan937x_mib_rx_fragments] +
> + ctr[lan937x_mib_rx_jabbers];
> +
> + s->rx_crc_errors = ctr[lan937x_mib_rx_crc_err];
> + s->rx_frame_errors = ctr[lan937x_mib_rx_align_err];
> + s->tx_aborted_errors = ctr[lan937x_mib_tx_exc_col];
> + s->tx_window_errors = ctr[lan937x_mib_tx_late_col];
> +
> + spin_unlock(&mib->stats64_lock);
> +}
> +static int lan937x_init(struct ksz_device *dev)
> +{
> + int ret;
> +
> + ret = lan937x_switch_init(dev);
> + if (ret < 0) {
> + dev_err(dev->dev, "failed to initialize the switch");
> + return ret;
> + }
> +
> + /* enable Indirect Access from SPI to the VPHY registers */
> + ret = lan937x_enable_spi_indirect_access(dev);
Do you need to call this both from lan937x_init() and from lan937x_setup()?
> + if (ret < 0) {
> + dev_err(dev->dev, "failed to enable spi indirect access");
> + return ret;
> + }
> +
> + ret = lan937x_mdio_register(dev);
> + if (ret < 0) {
> + dev_err(dev->dev, "failed to register the mdio");
> + return ret;
> + }
> +
> + return 0;
> +}
> +static void lan937x_port_stp_state_set(struct dsa_switch *ds, int port,
> + u8 state)
> +{
> + struct ksz_device *dev = ds->priv;
> + struct ksz_port *p;
> + u8 data;
> +
> + lan937x_pread8(dev, port, P_STP_CTRL, &data);
This is a copy-paste of ksz8_port_stp_state_set() except for the use of
lan937x_pread8() instead of ksz_pread8(). But ksz_pread8() should work
too, since it calls dev->dev_ops->get_port_addr(port, offset) which you
translate into PORT_CTRL_ADDR(port, offset) which is exactly what
lan937x_pread8() does.
> + data &= ~(PORT_TX_ENABLE | PORT_RX_ENABLE | PORT_LEARN_DISABLE);
> +
> + switch (state) {
> + case BR_STATE_DISABLED:
> + data |= PORT_LEARN_DISABLE;
> + break;
> + case BR_STATE_LISTENING:
> + data |= (PORT_RX_ENABLE | PORT_LEARN_DISABLE);
> + break;
> + case BR_STATE_LEARNING:
> + data |= PORT_RX_ENABLE;
> + break;
> + case BR_STATE_FORWARDING:
> + data |= (PORT_TX_ENABLE | PORT_RX_ENABLE);
> + break;
> + case BR_STATE_BLOCKING:
> + data |= PORT_LEARN_DISABLE;
> + break;
> + default:
> + dev_err(ds->dev, "invalid STP state: %d\n", state);
> + return;
> + }
> +
> + lan937x_pwrite8(dev, port, P_STP_CTRL, data);
> +
> + p = &dev->ports[port];
> + p->stp_state = state;
> +
> + ksz_update_port_member(dev, port);
> +}
next prev parent reply other threads:[~2022-04-08 23:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 16:53 [RFC PATCH v11 net-next 00/10] net: dsa: microchip: DSA driver support for LAN937x switch Prasanna Vengateshan
2022-03-25 16:53 ` [RFC PATCH v11 net-next 01/10] dt-bindings: net: make internal-delay-ps based on phy-mode Prasanna Vengateshan
2022-03-29 20:41 ` Rob Herring
2022-03-25 16:53 ` [RFC PATCH v11 net-next 02/10] dt-bindings: net: dsa: dt bindings for microchip lan937x Prasanna Vengateshan
2022-04-08 22:40 ` Vladimir Oltean
2022-03-25 16:53 ` [RFC PATCH v11 net-next 03/10] net: dsa: move mib->cnt_ptr reset code to ksz_common.c Prasanna Vengateshan
2022-03-25 16:53 ` [RFC PATCH v11 net-next 04/10] net: dsa: tag_ksz: add tag handling for Microchip LAN937x Prasanna Vengateshan
2022-03-25 16:53 ` [RFC PATCH v11 net-next 05/10] net: dsa: microchip: add DSA support for microchip lan937x Prasanna Vengateshan
2022-04-08 23:25 ` Vladimir Oltean [this message]
2022-03-25 16:53 ` [RFC PATCH v11 net-next 06/10] net: dsa: microchip: add support for phylink management Prasanna Vengateshan
2022-04-08 23:41 ` Vladimir Oltean
2022-04-29 15:58 ` Russell King (Oracle)
2022-03-25 16:53 ` [RFC PATCH v11 net-next 07/10] net: dsa: microchip: add support for ethtool port counters Prasanna Vengateshan
2022-03-25 16:53 ` [RFC PATCH v11 net-next 08/10] net: dsa: microchip: add support for port mirror operations Prasanna Vengateshan
2022-03-25 16:53 ` [RFC PATCH v11 net-next 09/10] net: dsa: microchip: add support for fdb and mdb management Prasanna Vengateshan
2022-03-25 16:53 ` [RFC PATCH v11 net-next 10/10] net: dsa: microchip: add support for vlan operations Prasanna Vengateshan
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=20220408232557.b62l3lksotq5vuvm@skbuf \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prasanna.vengateshan@microchip.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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