mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Justin Chen <justin.chen@broadcom.com>, netdev@vger.kernel.org
Cc: Broadcom internal kernel review list 
	<bcm-kernel-feedback-list@broadcom.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: phy: broadcom: stub c45 read/write for 54810
Date: Fri, 11 Aug 2023 16:40:01 -0700	[thread overview]
Message-ID: <87e4f794-669f-8d43-793c-b8c1878cbd15@broadcom.com> (raw)
In-Reply-To: <1691796578-846-1-git-send-email-justin.chen@broadcom.com>

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



On 8/11/2023 4:29 PM, Justin Chen wrote:
> The 54810 does not support c45. The mmd_phy_indirect accesses return
> arbirtary values leading to odd behavior like saying it supports EEE
> when it doesn't. We also see that reading/writing these non-existent
> MMD registers leads to phy instability in some cases.
> 
> Signed-off-by: Justin Chen <justin.chen@broadcom.com>

Thanks for submitting this fix, I would be tempted to slap a:

Fixes: b14995ac2527 ("net: phy: broadcom: Add BCM54810 PHY entry")

so we get it back ported to stable trees where appropriate. It is not 
clear whether we should return -EINVAL vs. -EOPNOTSUPP which may more 
clearly indicate the inability to support MMD registers?
-- 
Florian

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]

  reply	other threads:[~2023-08-11 23:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 23:29 Justin Chen
2023-08-11 23:40 ` Florian Fainelli [this message]
2023-08-11 23:47   ` Justin Chen
2023-08-11 23:54     ` Florian Fainelli
2023-08-12 14:23     ` 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=87e4f794-669f-8d43-793c-b8c1878cbd15@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=justin.chen@broadcom.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 \
    /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®