From: "Marek Behún" <kabel@kernel.org>
To: Kurt Cancemi <kurt@x64architecture.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] net: phy: marvell: Fixed handing of delays with plain RGMII interface
Date: Tue, 29 Jun 2021 02:23:35 +0200 [thread overview]
Message-ID: <20210629022335.1d27efc9@thinkpad> (raw)
In-Reply-To: <CADujJWWoWRyW3S+f3F_Zhq9H90QZ1W4eu=5dyad3DeMLHFp2TA@mail.gmail.com>
On Mon, 28 Jun 2021 19:09:49 -0400
Kurt Cancemi <kurt@x64architecture.com> wrote:
> I’m sorry if I proposed this wrong (I am new to the kernel mailing list), I
> acknowledge that this is probably not the way to fix the problem, I wanted
> to discuss why my fix is necessary. In the cover email I explained that I
> used (in the device tree) “rgmii-id” for the “phy-connection-type” and the
> DPAA memac correctly reports that the PHY type is “PHY_INTERFACE_MODE_RGMII_ID”
> but without my patch the RX and TX delay flags are not set on the
> underlying Marvell PHY and I receive RX and TX errors on every network
> request. Maybe there is some type of incompatibility between the Freescale
> DPAA1 Ethernet driver and the Marvell PHY?
Which driver again?
drivers/net/ethernet/freescale/dpaa
or
drivers/net/ethernet/freescale/dpaa2
?
next prev parent reply other threads:[~2021-06-29 0:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 19:28 [PATCH 0/1] Possible Issue Setting the Delay Flags in the Marvell Net PHY Driver Kurt Cancemi
2021-06-28 19:28 ` [PATCH 1/1] net: phy: marvell: Fixed handing of delays with plain RGMII interface Kurt Cancemi
2021-06-28 22:49 ` Marek Behún
2021-06-28 23:01 ` Marcin Wojtas
2021-06-29 0:05 ` Kurt Cancemi
2021-06-29 0:21 ` Marek Behún
[not found] ` <CADujJWWoWRyW3S+f3F_Zhq9H90QZ1W4eu=5dyad3DeMLHFp2TA@mail.gmail.com>
2021-06-29 0:23 ` Marek Behún [this message]
2021-06-29 1:12 ` Kurt Cancemi
2021-06-29 10:52 ` Marek Behún
2021-06-29 15:08 ` Andrew Lunn
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=20210629022335.1d27efc9@thinkpad \
--to=kabel@kernel.org \
--cc=kurt@x64architecture.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).