All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: rmk+kernel@armlinux.org.uk, alexander.levin@verizon.com,
	davem@davemloft.net, stable@vger.kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "net: phy: fix resume handling" has been added to the 4.14-stable tree
Date: Wed, 28 Feb 2018 17:27:34 +0100	[thread overview]
Message-ID: <20180228162734.GA6860@kroah.com> (raw)
In-Reply-To: <20180228154348.GB29484@lunn.ch>

On Wed, Feb 28, 2018 at 04:43:48PM +0100, Andrew Lunn wrote:
> > When a PHY has the BMCR_PDOWN bit set, it may decide to ignore writes
> > to other registers, or reset the registers to power-on defaults.
> > Micrel PHYs do this for their interrupt registers.
> > 
> > The current structure of phylib tries to enable interrupts before
> > resuming (and releasing) the BMCR_PDOWN bit.  This fails, causing
> > Micrel PHYs to stop working after a suspend/resume sequence if they
> > are using interrupts.
> > 
> > Fix this by ensuring that the PHY driver resume methods do not take
> > the phydev->lock mutex themselves, but the callers of phy_resume()
> > take that lock.  This then allows us to move the call to phy_resume()
> > before we enable interrupts in phy_start().
> 
> Hi Greg
> 
> This patch introduces some issues. You don't want this patch on its
> own, you want it in combination with:
> 
> Fixes: 9c2c2e62df3f ("net: phy: Restore phy_resume() locking assumption")
> 
> Which went into David Millers net tree yesterday and should be making
> its way towards stable.
> 
> I suggest you hold off on this patch, until you can do both at the
> same time.

Thanks for letting me know, I've now dropped this.

greg k-h

  reply	other threads:[~2018-02-28 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 15:26 Patch "net: phy: fix resume handling" has been added to the 4.14-stable tree gregkh
2018-02-28 15:43 ` Andrew Lunn
2018-02-28 16:27   ` Greg KH [this message]
2018-03-16 12:38     ` Greg KH

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=20180228162734.GA6860@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.levin@verizon.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.