[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DB5PR0401MB2183495D42037728D1738301E8720@DB5PR0401MB2183.eurprd04.prod.outlook.com>
Date: Wed, 11 May 2016 02:15:13 +0000
From: Shaohui Xie <shaohui.xie@....com>
To: Florian Fainelli <f.fainelli@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>
CC: Andrew Lunn <andrew@...n.ch>
Subject: RE: [PATCH] net: phylib: fix interrupts re-enablement in phy_start
> -----Original Message-----
> From: Florian Fainelli [mailto:f.fainelli@...il.com]
> Sent: Wednesday, May 11, 2016 2:25 AM
> To: shh.xie@...il.com; netdev@...r.kernel.org; davem@...emloft.net
> Cc: Shaohui Xie <shaohui.xie@....com>; Andrew Lunn <andrew@...n.ch>
> Subject: Re: [PATCH] net: phylib: fix interrupts re-enablement in phy_start
>
> On 05/10/2016 02:42 AM, shh.xie@...il.com wrote:
> > From: Shaohui Xie <Shaohui.Xie@....com>
> >
> > If phy was suspended and is starting, current driver always enable
> > phy's interrupts, if phy works in polling, phy can raise unexpected
> > interrupt which will not be handled, the interrupt will block system
> > enter suspend again. So interrupts should only be re-enabled if phy
> > works in interrupt.
>
> Your explanation makes sense. The commit message could you use some
> improvements like s/phy/PHY/ and "works in interrupt mode", but that is not a
> huge thing.
[S.H] Thank you for the comment.
I should make the commit message more precise and will make improvement in
future patch submission.
Regards,
Shaohui
Powered by blists - more mailing lists