lkml.org 
[lkml]   [2019]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
SubjectRe: [RFC] net: phy: read link status twice when phy_check_link_status()
From
Date


On 2019/7/27 2:14, Heiner Kallweit wrote:
> On 26.07.2019 11:53, Yonglong Liu wrote:
>> According to the datasheet of Marvell phy and Realtek phy, the
>> copper link status should read twice, or it may get a fake link
>> up status, and cause up->down->up at the first time when link up.
>> This happens more oftem at Realtek phy.
>>
> This is not correct, there is no fake link up status.
> Read the comment in genphy_update_link, only link-down events
> are latched. Means if the first read returns link up, then there
> is no need for a second read. And in polling mode we don't do a
> second read because we want to detect also short link drops.
>
> It would be helpful if you could describe your actual problem
> and whether you use polling or interrupt mode.
>

[ 44.498633] hns3 0000:bd:00.1 eth5: net open
[ 44.504273] hns3 0000:bd:00.1: reg=0x1, data=0x79ad -> called from phy_start_aneg
[ 44.532348] hns3 0000:bd:00.1: reg=0x1, data=0x798d -> called from phy_state_machine,update link.

According to the datasheet:
reg 1.5=0 now, means copper auto-negotiation not complete
reg 1.2=1 now, means link is up

We can see that, when we read the link up, the auto-negotiation
is not complete yet, so the speed is invalid.

I don't know why this happen, maybe this state is keep from bios?
Or we may do something else in the phy initialize to fix it?
And also confuse that why read twice can fix it?

[ 44.554063] hns3 0000:bd:00.1: invalid speed (-1)
[ 44.560412] hns3 0000:bd:00.1 eth5: failed to adjust link.
[ 45.194870] hns3 0000:bd:00.1 eth5: link up
[ 45.574095] hns3 0000:bd:00.1: phyid=3, reg=0x1, data=0x7989
[ 46.150051] hns3 0000:bd:00.1 eth5: link down
[ 46.598074] hns3 0000:bd:00.1: phyid=3, reg=0x1, data=0x7989
[ 47.622075] hns3 0000:bd:00.1: phyid=3, reg=0x1, data=0x79a9
[ 48.646077] hns3 0000:bd:00.1: phyid=3, reg=0x1, data=0x79ad
[ 48.934050] hns3 0000:bd:00.1 eth5: link up
[ 49.702140] hns3 0000:bd:00.1: phyid=3, reg=0x1, data=0x79ad

>> I add a fake status read, and can solve this problem.
>>
>> I also see that in genphy_update_link(), had delete the fake
>> read in polling mode, so I don't know whether my solution is
>> correct.
>>
>> Or provide a phydev->drv->read_status functions for the phy I
>> used is more acceptable?
>>
>> Signed-off-by: Yonglong Liu <liuyonglong@huawei.com>
>> ---
>> drivers/net/phy/phy.c | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c
>> index ef7aa73..0c03edc 100644
>> --- a/drivers/net/phy/phy.c
>> +++ b/drivers/net/phy/phy.c
>> @@ -1,4 +1,7 @@
>> // SPDX-License-Identifier: GPL-2.0+
>> + err = phy_read_status(phydev);
>> + if (err)
>> + return err;
>
> This seems to be completely wrong at that place.
>

Sorry, this can be ignore.

>> /* Framework for configuring and reading PHY devices
>> * Based on code in sungem_phy.c and gianfar_phy.c
>> *
>> @@ -525,6 +528,11 @@ static int phy_check_link_status(struct phy_device *phydev)
>>
>> WARN_ON(!mutex_is_locked(&phydev->lock));
>>
>> + /* Do a fake read */
>> + err = phy_read(phydev, MII_BMSR);
>> + if (err < 0)
>> + return err;
>> +
>> err = phy_read_status(phydev);
>> if (err)
>> return err;
>>
>
>
> .
>

\
 
 \ /
  Last update: 2019-07-29 06:01    [W:0.103 / U:2.592 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site