From: "Heiko Stübner" <heiko@sntech.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jose Abreu <joabreu@synopsys.com>,
klaus.goger@theobroma-systems.com,
linux-arm-kernel@lists.infradead.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
philipp.tomsich@theobroma-systems.com,
"Leonidas P. Papadakos" <papadakospan@gmail.com>
Subject: Re: [PATCH 1/2] stmmac: introduce flag to dynamically disable TX offload for rockchip devices
Date: Mon, 01 Apr 2019 21:06:53 +0200 [thread overview]
Message-ID: <2312344.mOsv7YkeBG@diego> (raw)
In-Reply-To: <9d65a22a-2288-dc53-0059-ec4a31424dd8@arm.com>
Am Montag, 1. April 2019, 20:54:45 CEST schrieb Robin Murphy:
> On 01/04/2019 19:18, Leonidas P. Papadakos wrote:
> > From: =?UTF-8?q?Kamil=20Trzci=C5=84ski?= <ayufan@ayufan.eu>
> >
> > Some rockchip boards exhibit an issue where tx checksumming does not work with
> > packets larger than 1498.
>
> Is it really a board-level problem? I'm no networking expert, but the
> nature of the workaround suggests this is more likely to be some
> inherent limitation of the IP block in the SoC, rather than something to
> do with how the external pins get wired up. Does anyone have an RK3328
> or RK3399 board that provably *does* checksum large packets correctly?
I don't have that many rk3399-boards with actual ethernet and even only
the rock64 from rk3328-land, but at least my rk3399-firefly also seems
affected by this.
But so far the rk3399-puma board from Theobroma did not show that ethernet
issue for me, so I've added two Theobroma people who may or may not tell
if they've also seen that issue.
>
> > This is bad for network stability.
> >
> > The previous approach was using force_thresh_dma_mode in the board dts, which
> > does more than we need.
>
> If indeed it is a SoC-level thing (or at least we want to treat it as
> such), then couldn't we just hang it off the existing SoC-specific
> compatibles in dwmac-rk.c and avoid the need for a new DT property at
> all? After all, that's precisely why SoC-specific compatibles are a
> thing in the first place.
>
> Robin.
>
> > Signed-off-by: Leonidas P. Papadakos <papadakospan@gmail.com>
> > ---
> > drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 4 ++++
> > drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c | 2 ++
> > include/linux/stmmac.h | 1 +
> > 3 files changed, 7 insertions(+)
> >
> > diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> > index 6a2e1031a..4552147e9 100644
> > --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> > +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> > @@ -3660,6 +3660,10 @@ static netdev_features_t stmmac_fix_features(struct net_device *dev,
> > if (priv->plat->bugged_jumbo && (dev->mtu > ETH_DATA_LEN))
> > features &= ~NETIF_F_CSUM_MASK;
> >
> > + /* Including very small MTUs of 1498 for Rockchip devices */
> > + if (priv->plat->bugged_tx_coe && (dev->mtu > ETH_DATA_LEN - 2))
> > + features &= ~NETIF_F_CSUM_MASK;
> > +
> > /* Disable tso if asked by ethtool */
> > if ((priv->plat->tso_en) && (priv->dma_cap.tsoen)) {
> > if (features & NETIF_F_TSO)
> > diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
> > index 3031f2bf1..807cf5826 100644
> > --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
> > +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
> > @@ -519,6 +519,8 @@ stmmac_probe_config_dt(struct platform_device *pdev, const char **mac)
> > pr_warn("force_sf_dma_mode is ignored if force_thresh_dma_mode is set.");
> > }
> >
> > + plat->bugged_tx_coe = of_property_read_bool(np, "rockchip,bugged_tx_coe");
> > +
> > of_property_read_u32(np, "snps,ps-speed", &plat->mac_port_sel_speed);
> >
> > plat->axi = stmmac_axi_setup(pdev);
> > diff --git a/include/linux/stmmac.h b/include/linux/stmmac.h
> > index 4335bd771..60c411f43 100644
> > --- a/include/linux/stmmac.h
> > +++ b/include/linux/stmmac.h
> > @@ -162,6 +162,7 @@ struct plat_stmmacenet_data {
> > int pmt;
> > int force_sf_dma_mode;
> > int force_thresh_dma_mode;
> > + int bugged_tx_coe;
> > int riwt_off;
> > int max_speed;
> > int maxmtu;
> >
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Leonidas P. Papadakos" <papadakospan@gmail.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
netdev@vger.kernel.org, Jose Abreu <joabreu@synopsys.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
klaus.goger@theobroma-systems.com,
philipp.tomsich@theobroma-systems.com
Subject: Re: [PATCH 1/2] stmmac: introduce flag to dynamically disable TX offload for rockchip devices
Date: Mon, 01 Apr 2019 21:06:53 +0200 [thread overview]
Message-ID: <2312344.mOsv7YkeBG@diego> (raw)
In-Reply-To: <9d65a22a-2288-dc53-0059-ec4a31424dd8@arm.com>
Am Montag, 1. April 2019, 20:54:45 CEST schrieb Robin Murphy:
> On 01/04/2019 19:18, Leonidas P. Papadakos wrote:
> > From: =?UTF-8?q?Kamil=20Trzci=C5=84ski?= <ayufan@ayufan.eu>
> >
> > Some rockchip boards exhibit an issue where tx checksumming does not work with
> > packets larger than 1498.
>
> Is it really a board-level problem? I'm no networking expert, but the
> nature of the workaround suggests this is more likely to be some
> inherent limitation of the IP block in the SoC, rather than something to
> do with how the external pins get wired up. Does anyone have an RK3328
> or RK3399 board that provably *does* checksum large packets correctly?
I don't have that many rk3399-boards with actual ethernet and even only
the rock64 from rk3328-land, but at least my rk3399-firefly also seems
affected by this.
But so far the rk3399-puma board from Theobroma did not show that ethernet
issue for me, so I've added two Theobroma people who may or may not tell
if they've also seen that issue.
>
> > This is bad for network stability.
> >
> > The previous approach was using force_thresh_dma_mode in the board dts, which
> > does more than we need.
>
> If indeed it is a SoC-level thing (or at least we want to treat it as
> such), then couldn't we just hang it off the existing SoC-specific
> compatibles in dwmac-rk.c and avoid the need for a new DT property at
> all? After all, that's precisely why SoC-specific compatibles are a
> thing in the first place.
>
> Robin.
>
> > Signed-off-by: Leonidas P. Papadakos <papadakospan@gmail.com>
> > ---
> > drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 4 ++++
> > drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c | 2 ++
> > include/linux/stmmac.h | 1 +
> > 3 files changed, 7 insertions(+)
> >
> > diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> > index 6a2e1031a..4552147e9 100644
> > --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> > +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> > @@ -3660,6 +3660,10 @@ static netdev_features_t stmmac_fix_features(struct net_device *dev,
> > if (priv->plat->bugged_jumbo && (dev->mtu > ETH_DATA_LEN))
> > features &= ~NETIF_F_CSUM_MASK;
> >
> > + /* Including very small MTUs of 1498 for Rockchip devices */
> > + if (priv->plat->bugged_tx_coe && (dev->mtu > ETH_DATA_LEN - 2))
> > + features &= ~NETIF_F_CSUM_MASK;
> > +
> > /* Disable tso if asked by ethtool */
> > if ((priv->plat->tso_en) && (priv->dma_cap.tsoen)) {
> > if (features & NETIF_F_TSO)
> > diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
> > index 3031f2bf1..807cf5826 100644
> > --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
> > +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
> > @@ -519,6 +519,8 @@ stmmac_probe_config_dt(struct platform_device *pdev, const char **mac)
> > pr_warn("force_sf_dma_mode is ignored if force_thresh_dma_mode is set.");
> > }
> >
> > + plat->bugged_tx_coe = of_property_read_bool(np, "rockchip,bugged_tx_coe");
> > +
> > of_property_read_u32(np, "snps,ps-speed", &plat->mac_port_sel_speed);
> >
> > plat->axi = stmmac_axi_setup(pdev);
> > diff --git a/include/linux/stmmac.h b/include/linux/stmmac.h
> > index 4335bd771..60c411f43 100644
> > --- a/include/linux/stmmac.h
> > +++ b/include/linux/stmmac.h
> > @@ -162,6 +162,7 @@ struct plat_stmmacenet_data {
> > int pmt;
> > int force_sf_dma_mode;
> > int force_thresh_dma_mode;
> > + int bugged_tx_coe;
> > int riwt_off;
> > int max_speed;
> > int maxmtu;
> >
>
next prev parent reply other threads:[~2019-04-01 19:07 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 18:18 [PATCH 1/2] stmmac: introduce flag to dynamically disable TX offload for rockchip devices Leonidas P. Papadakos
2019-04-01 18:18 ` Leonidas P. Papadakos
2019-04-01 18:31 ` Heiko Stübner
2019-04-01 18:31 ` Heiko Stübner
2019-04-01 18:54 ` Robin Murphy
2019-04-01 18:54 ` Robin Murphy
2019-04-01 19:06 ` Heiko Stübner [this message]
2019-04-01 19:06 ` Heiko Stübner
2019-04-01 19:12 ` Philipp Tomsich
2019-04-01 19:12 ` Philipp Tomsich
2019-04-02 7:59 ` Jose Abreu
2019-04-02 7:59 ` Jose Abreu
2019-04-02 11:49 ` Robin Murphy
2019-04-02 11:49 ` Robin Murphy
2019-04-02 11:53 ` Jose Abreu
2019-04-02 11:53 ` Jose Abreu
2019-04-02 22:08 ` Robin Murphy
2019-04-02 22:08 ` Robin Murphy
2019-04-02 22:48 ` Leonidas P. Papadakos
2019-04-02 22:48 ` Leonidas P. Papadakos
2019-04-03 7:55 ` Jose Abreu
2019-04-03 7:55 ` Jose Abreu
2019-04-03 15:35 ` Leonidas P. Papadakos
2019-04-03 15:35 ` Leonidas P. Papadakos
2019-04-03 15:55 ` Leonidas P. Papadakos
2019-04-03 15:55 ` Leonidas P. Papadakos
2019-04-03 16:12 ` Robin Murphy
2019-04-03 16:12 ` Robin Murphy
2019-04-05 10:24 ` Jose Abreu
2019-04-05 10:24 ` Jose Abreu
2019-04-05 17:58 ` Leonidas P. Papadakos
2019-04-05 17:58 ` Leonidas P. Papadakos
2019-04-05 18:14 ` Leonidas P. Papadakos
2019-04-05 18:14 ` Leonidas P. Papadakos
2019-04-05 18:29 ` Robin Murphy
2019-04-05 18:29 ` Robin Murphy
2019-04-05 18:38 ` Leonidas P. Papadakos
2019-04-05 18:38 ` Leonidas P. Papadakos
2019-04-11 21:09 ` Leonidas P. Papadakos
2019-04-11 21:09 ` Leonidas P. Papadakos
2019-04-12 7:35 ` Jose Abreu
2019-04-12 7:35 ` Jose Abreu
2019-04-12 11:13 ` Leonidas P. Papadakos
2019-04-12 11:13 ` Leonidas P. Papadakos
2019-04-15 8:15 ` Jose Abreu
2019-04-15 8:15 ` Jose Abreu
2019-04-15 21:45 ` Leonidas P. Papadakos
2019-04-15 21:45 ` Leonidas P. Papadakos
2019-04-15 22:19 ` Leonidas P. Papadakos
2019-04-15 22:19 ` Leonidas P. Papadakos
2019-04-16 8:01 ` Jose Abreu
2019-04-16 8:01 ` Jose Abreu
2019-04-16 10:03 ` Leonidas P. Papadakos
2019-04-16 10:03 ` Leonidas P. Papadakos
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=2312344.mOsv7YkeBG@diego \
--to=heiko@sntech.de \
--cc=alexandre.torgue@st.com \
--cc=joabreu@synopsys.com \
--cc=klaus.goger@theobroma-systems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=papadakospan@gmail.com \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=robin.murphy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.