netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net] net: phy: micrel: set soft_reset callback to genphy_soft_reset for KSZ9031
Date: Thu, 10 Jan 2019 13:27:09 -0800	[thread overview]
Message-ID: <20190110212709.GO5540@atomide.com> (raw)
In-Reply-To: <b6ee55ef-6cfc-e8a9-9108-535f912992d4@gmail.com>

* Heiner Kallweit <hkallweit1@gmail.com> [190110 19:41]:
> On 10.01.2019 20:24, Florian Fainelli wrote:
> > On 1/10/19 11:22 AM, Heiner Kallweit wrote:
> >> So far genphy_soft_reset was used automatically if the PHY driver
> >> didn't implement the soft_reset callback. This changed with the
> >> mentioned commit and broke KSZ9031. To fix this configure the
> >> KSZ9031 PHY driver to use genphy_soft_reset.
> >>
> >> Fixes: 6e2d85ec0559 ("net: phy: Stop with excessive soft reset")
> >> Reported-by: Tony Lindgren <tony@atomide.com>
> >> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> > 
> > Thanks a lot for following up with the people at TI on this. We should
> > really get a better understanding of what the issue is, and whether
> > there is a possibly better workaround that could be developed which is
> > not just as hard as a big hammer software reset. Maybe we can get some
> > people/contacts at Micrel to help here.
> > 
> In ksz9031_config_init() quite some settings are done and IMO it's not
> that unusual that it takes a soft reset for such settings to become
> effective. But I agree it would be nice if somebody from the PHY vendor
> could comment on whether a soft reset is actually needed. Not sure who
> has a contact to Microchip.

Adding Sekhar to Cc, maybe he has some contacts to ask.

> If the feedback takes time it may be better to apply the soft reset as
> fix and replace it later in case we have a less intrusive option.

Yes please let's fix the regression first and then patch
more later as needed.

Regards,

Tony

> >> ---
> >>  drivers/net/phy/micrel.c | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
> >> index c33384710..7828d17f0 100644
> >> --- a/drivers/net/phy/micrel.c
> >> +++ b/drivers/net/phy/micrel.c
> >> @@ -1070,6 +1070,7 @@ static struct phy_driver ksphy_driver[] = {
> >>  	.driver_data	= &ksz9021_type,
> >>  	.probe		= kszphy_probe,
> >>  	.config_init	= ksz9031_config_init,
> >> +	.soft_reset	= genphy_soft_reset,
> >>  	.read_status	= ksz9031_read_status,
> >>  	.ack_interrupt	= kszphy_ack_interrupt,
> >>  	.config_intr	= kszphy_config_intr,
> >>
> > 
> > 
> 

  reply	other threads:[~2019-01-10 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 19:22 [PATCH net] net: phy: micrel: set soft_reset callback to genphy_soft_reset for KSZ9031 Heiner Kallweit
2019-01-10 19:24 ` Florian Fainelli
2019-01-10 19:41   ` Heiner Kallweit
2019-01-10 21:27     ` Tony Lindgren [this message]
2019-01-10 21:29       ` Tony Lindgren
2019-01-11 11:22       ` Sekhar Nori
2019-01-10 21:24 ` Tony Lindgren
2019-01-13  5:14 ` Florian Fainelli
2019-01-16  5:41 ` David Miller

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=20190110212709.GO5540@atomide.com \
    --to=tony@atomide.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.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).