LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Anderson <seanga2@gmail.com>
To: chzigotzky@xenosoft.de, Madalin Bucur <madalin.bucur@nxp.com>,
	"David S. Miller" <davem@davemloft.net>
Cc: darren@stevens-zone.net, rtd2@xtra.co.nz,
	Sean Anderson <sean.anderson@seco.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	madskateman@gmail.com, Jakub Kicinski <kuba@kernel.org>,
	matthew@a-eon.biz, Paolo Abeni <pabeni@redhat.com>,
	linuxppc-dev@lists.ozlabs.org, davem@davemloft.net,
	info@xenosoft.de
Subject: Re: [FSL P50x0] DPAA Ethernet issue
Date: Sun, 1 Jan 2023 13:11:07 -0500	[thread overview]
Message-ID: <a40020bd-c190-4283-1977-9e4d9627b888@gmail.com> (raw)
In-Reply-To: <0bfc8f3d-cb62-25f4-2590-ff424adbe48a@xenosoft.de>

[-- Attachment #1: Type: text/plain, Size: 2378 bytes --]

Hi Christian,

+CC netdev folks

> Hi All,
> 
> The DPAA Ethernet doesn’t work anymore on our FSL P5020/P5040 boards [1] 
> since the first updates after the final kernel 6.1 [2].
> We bisected yesterday [3] and found the problematic commit [4]. I was 
> able to revert it. After that the DPAA Ethernet works again. I created a 
> patch for reverting the commit [4]. After patching and compiling, the 
> DPAA Ethernet also works again.

Thank you for testing this. Unfortunately, I have no P-series hardware,
so I was unable to test the 10gec/dtsec parts of this conversion. I had
hoped that this would get tested by someone with the hardware (at NXP)
before now, but it seems you get to be the "lucky" first user.

I see you have labeled one of your kernels as supporting QEMU.  Do you
happen to have instructions for running Linux on QEMU?

> It seems, that the new driver doesn’t work with our onboard DPAA network 
> interfaces.
> 
> Could you please check your commit? [4]

Can you try the following patch. I think my mail client will mangle it,
so I have also attached it to this email.

 From 3898c62106025209b26527ad1516b339eebb62f1 Mon Sep 17 00:00:00 2001
From: Sean Anderson <seanga2@gmail.com>
Date: Sun, 1 Jan 2023 13:00:21 -0500
Subject: [PATCH] net: dpaa: Fix dtsec check for PCS availability

We want to fail if the PCS is not available, not if it is available. Fix
this condition.

Fixes: 5d93cfcf7360 ("net: dpaa: Convert to phylink")
Reported-by: Christian Zigotzky <info@xenosoft.de>
Signed-off-by: Sean Anderson <seanga2@gmail.com>
---
  drivers/net/ethernet/freescale/fman/fman_dtsec.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/freescale/fman/fman_dtsec.c b/drivers/net/ethernet/freescale/fman/fman_dtsec.c
index 3c87820ca202..3462f2b78680 100644
--- a/drivers/net/ethernet/freescale/fman/fman_dtsec.c
+++ b/drivers/net/ethernet/freescale/fman/fman_dtsec.c
@@ -1431,7 +1431,7 @@ int dtsec_initialization(struct mac_device *mac_dev,
  	dtsec->dtsec_drv_param->tx_pad_crc = true;
  
  	phy_node = of_parse_phandle(mac_node, "tbi-handle", 0);
-	if (!phy_node || of_device_is_available(phy_node)) {
+	if (!phy_node || !of_device_is_available(phy_node)) {
  		of_node_put(phy_node);
  		err = -EINVAL;
  		dev_err_probe(mac_dev->dev, err,
-- 
2.37.1

[-- Attachment #2: 0001-net-dpaa-Fix-dtsec-check-for-PCS-availability.patch --]
[-- Type: text/x-patch, Size: 1213 bytes --]

From 3898c62106025209b26527ad1516b339eebb62f1 Mon Sep 17 00:00:00 2001
From: Sean Anderson <seanga2@gmail.com>
Date: Sun, 1 Jan 2023 13:00:21 -0500
Subject: [PATCH] net: dpaa: Fix dtsec check for PCS availability

We want to fail if the PCS is not available, not if it is available. Fix
this condition.

Fixes: 5d93cfcf7360 ("net: dpaa: Convert to phylink")
Reported-by: Christian Zigotzky <info@xenosoft.de>
Signed-off-by: Sean Anderson <seanga2@gmail.com>
---
 drivers/net/ethernet/freescale/fman/fman_dtsec.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/freescale/fman/fman_dtsec.c b/drivers/net/ethernet/freescale/fman/fman_dtsec.c
index 3c87820ca202..3462f2b78680 100644
--- a/drivers/net/ethernet/freescale/fman/fman_dtsec.c
+++ b/drivers/net/ethernet/freescale/fman/fman_dtsec.c
@@ -1431,7 +1431,7 @@ int dtsec_initialization(struct mac_device *mac_dev,
 	dtsec->dtsec_drv_param->tx_pad_crc = true;
 
 	phy_node = of_parse_phandle(mac_node, "tbi-handle", 0);
-	if (!phy_node || of_device_is_available(phy_node)) {
+	if (!phy_node || !of_device_is_available(phy_node)) {
 		of_node_put(phy_node);
 		err = -EINVAL;
 		dev_err_probe(mac_dev->dev, err,
-- 
2.37.1


  reply	other threads:[~2023-01-01 20:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01 14:18 [FSL P50x0] DPAA Ethernet issue Christian Zigotzky
2023-01-01 18:11 ` Sean Anderson [this message]
2023-01-02  3:32   ` Christian Zigotzky
2023-01-03  4:03     ` Christian Zigotzky
2023-01-03 19:59       ` Christian Zigotzky
2023-01-02  7:58 ` Linux kernel regression tracking (#info)
2023-01-03 20:17   ` Sean Anderson

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=a40020bd-c190-4283-1977-9e4d9627b888@gmail.com \
    --to=seanga2@gmail.com \
    --cc=chzigotzky@xenosoft.de \
    --cc=darren@stevens-zone.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=info@xenosoft.de \
    --cc=kuba@kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madalin.bucur@nxp.com \
    --cc=madskateman@gmail.com \
    --cc=matthew@a-eon.biz \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rtd2@xtra.co.nz \
    --cc=sean.anderson@seco.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