From: Roger Quadros <rogerq@ti.com>
To: <f.fainelli@gmail.com>, <andrew@lunn.ch>
Cc: <davem@davemloft.net>, <kyle.roeschley@ni.com>, <nsekhar@ti.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"stable # v4 . 9+" <stable@vger.kernel.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
"Andrew F. Davis" <afd@ti.com>
Subject: Re: [PATCH v3 1/2] net: phy: Fix PHY AN done state machine for interrupt driven PHYs
Date: Tue, 11 Apr 2017 14:17:12 +0300 [thread overview]
Message-ID: <203afff4-7dd7-e185-000a-1689a97dfb67@ti.com> (raw)
In-Reply-To: <bfaac2be-175b-c370-43ce-7a11b2933e1c@ti.com>
Hi,
On 28/03/17 13:05, Roger Quadros wrote:
> +Andrew Davis & Sekhar.
>
> Hi,
>
> Andrew Davis posted a few comments offline which I'm clarifying here.
>
> On 27/03/17 14:59, Roger Quadros wrote:
>> The Ethernet link on an interrupt driven PHY was not coming up if the
>> Ethernet cable was plugged before the Ethernet interface was brought up.
>>
>> The PHY state machine seems to be stuck from RUNNING to AN state
>> with no new interrupts from the PHY. So it doesn't know when the
>> PHY Auto-negotiation has been completed and doesn't transition to RUNNING
>> state with ANEG done thus netif_carrier_on() is never called.
>>
>> NOTE: genphy_config_aneg() will not restart PHY Auto-negotiation of
>> advertisement parameters didn't change.
>
> Is phy->config_aneg expected to *always* restart auto-negotiation even if
> advertisement parameters didn't change?
> If so then we'll need to fix genphy_config_aneg().
>
>>
>> Fix this by scheduling the PHY state machine in phy_start_aneg().
>> There is no way of knowing in phy.c whether auto-negotiation was
>> restarted or not by the PHY driver so we just wait for the next
>> poll/interrupt to update the PHY state machine.
>>
>> Fixes: 3c293f4e08b5 ("net: phy: Trigger state machine on state change and not polling.")
>> Cc: stable <stable@vger.kernel.org> # v4.9+
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> ---
>> v3: Fix typo in commit message
>>
>> drivers/net/phy/phy.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c
>> index 1be69d8..49dedf8 100644
>> --- a/drivers/net/phy/phy.c
>> +++ b/drivers/net/phy/phy.c
>> @@ -630,6 +630,10 @@ int phy_start_aneg(struct phy_device *phydev)
>>
>> out_unlock:
>> mutex_unlock(&phydev->lock);
>> + if (!err && phy_interrupt_is_valid(phydev))
>> + queue_delayed_work(system_power_efficient_wq,
>> + &phydev->state_queue, HZ);
>> +
>> return err;
>> }
>> EXPORT_SYMBOL(phy_start_aneg);
>>
>
> There is still room for optimization for interrupt driven PHYs as I still
> see a delay of 1 second between "ifconfig ethx up" and link status coming up
> if cable was already plugged in. In fact if Auto-negotiation was already completed
> and not required to be restarted, the PHY state machine should have move from
> AN to RUNNING instantly without expecting a PHY interrupt.
>
> How can we get rid of the unnecessary delay in the case where auto-negotiation
> is not restarted?
> Should we check for phy_aneg_done() immediately after issuing a phy_start_aneg()
> in phy_state_machine() and switch from PHY_AN to PHY_RUNNING?
>
> This should avoid the need to re-schedule the state machine in phy_start_angeg().
Any comments on my questions?
cheers,
-roger
next prev parent reply other threads:[~2017-04-11 11:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 11:02 [PATCH v2 0/2] net: phy: state machine fixes " Roger Quadros
2017-03-22 11:02 ` [PATCH v2 1/2] net: phy: Fix PHY AN done state machine " Roger Quadros
2017-03-23 9:52 ` Sergei Shtylyov
2017-03-27 11:50 ` Roger Quadros
2017-03-27 11:59 ` [PATCH v3 " Roger Quadros
2017-03-28 10:05 ` Roger Quadros
2017-04-11 11:17 ` Roger Quadros [this message]
2017-04-19 16:28 ` Florian Fainelli
2017-03-30 12:59 ` Madalin-Cristian Bucur
2017-03-30 20:02 ` Florian Fainelli
2017-03-31 9:19 ` Roger Quadros
2017-03-22 11:02 ` [PATCH v2 2/2] net: phy: Don't miss phy_suspend() on PHY_HALTED for PHYs with interrupts Roger Quadros
2017-04-19 16:31 ` Florian Fainelli
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=203afff4-7dd7-e185-000a-1689a97dfb67@ti.com \
--to=rogerq@ti.com \
--cc=afd@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kyle.roeschley@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=sergei.shtylyov@cogentembedded.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome