From: Andrew Lunn <andrew@lunn.ch>
To: Harini Katakam <harini.katakam@amd.com>
Cc: hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
harinikatakamlinux@gmail.com, michal.simek@amd.com,
radhey.shyam.pandey@amd.com
Subject: Re: [PATCH] net: phy: dp83867: Extend RX strap quirk for SGMII mode
Date: Thu, 13 Oct 2022 15:24:30 +0200 [thread overview]
Message-ID: <Y0gRjoOOJQmGQ6Ao@lunn.ch> (raw)
In-Reply-To: <20221013072833.28558-1-harini.katakam@amd.com>
On Thu, Oct 13, 2022 at 12:58:33PM +0530, Harini Katakam wrote:
> When RX strap in HW is not set to MODE 3 or 4, bit 7 and 8 in CF4
> register should be set. The former is already handled in
> dp83867_config_init; add the latter in SGMII specific initialization.
>
> Signed-off-by: Harini Katakam <harini.katakam@amd.com>
> ---
> drivers/net/phy/dp83867.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/net/phy/dp83867.c b/drivers/net/phy/dp83867.c
> index 6939563d3b7c..a2aac9032af6 100644
> --- a/drivers/net/phy/dp83867.c
> +++ b/drivers/net/phy/dp83867.c
> @@ -853,6 +853,13 @@ static int dp83867_config_init(struct phy_device *phydev)
> else
> val &= ~DP83867_SGMII_TYPE;
> phy_write_mmd(phydev, DP83867_DEVADDR, DP83867_SGMIICTL, val);
> + /* This is a SW workaround for link instability if RX_CTRL is
> + * not strapped to mode 3 or 4 in HW. This is required for SGMII
> + * in addition to clearing bit 7, handled above.
> + */
Blank line before a comment please.
Should this have a fixes tag? Are there deployed boards which are
broken because of this? Or do you have a new board, using SGMII, which
is not deployed yet?
Andrew
next prev parent reply other threads:[~2022-10-13 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 7:28 Harini Katakam
2022-10-13 13:24 ` Andrew Lunn [this message]
2022-10-14 4:30 ` Katakam, Harini
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=Y0gRjoOOJQmGQ6Ao@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harini.katakam@amd.com \
--cc=harinikatakamlinux@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.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
all inboxes | Powered by JetHome®