netdev - Re: [PATCH net-next 0/6] net: bcmgenet: PHY initialization rework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <55AD5377.6020401@gmail.com>
Date:	Mon, 20 Jul 2015 13:00:55 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	Jaedon Shin <jaedon.shin@...il.com>
CC:	netdev@...r.kernel.org, David Miller <davem@...emloft.net>,
	Petri Gynther <pgynther@...gle.com>
Subject: Re: [PATCH net-next 0/6] net: bcmgenet: PHY initialization rework

On 17/07/15 06:53, Jaedon Shin wrote:
>> On Jul 17, 2015, at 7:51 AM, Florian Fainelli <f.fainelli@...il.com> wrote:
>>
>> Hi David, Petri, Jaedon,
>>
>> This patch series reworks how we perform PHY initialization and resets in the
>> GENET driver. Although this contains mostly fixes, some of the changes are a
>> bit too intrusive to be backported to 'net' at the moment.
>>
>> Some of the motivations behind these changes were to reduce the time spent in how
>> performing MDIO transactions, since it is better to perform then when we have
>> interrupts enabled. This reduces the bring-up time of GENET from ~600 msecs down
>> to ~8 msecs, and about the same time for suspend/resume.
>>
>> Since I do not currently have a system which is not DT-aware, can you (Petri,
>> Jaedon) give this a try and confirm things keep working as expected?
>>
>> Thanks!
>>
> 
> I tested your patch series on Broadcom 40nm set-top box platform that used
> internal phy. I did not have the exact measurements. but I expect it to improve
> on the interface-up or link-up time. and I compared the changes roughly from
> kernel print time. please see below.

Thanks for testing! The patches are not really meant to improve the link
up/down time, the fact that you are seeing an improvement here is
coincidental and/or not related. The patches are meant to provide an
improvement during system resume (out of S2 and S3) and during the
initial probe of the driver.

Sounds like you tested this with a DT-enabled MIPS platform, do you have
code handy to do the same experiement without DT?

> 
> - before patching
> [    1.865126] bcmgenet 10430000.ethernet eth0: Link is Down
> [    3.941132] bcmgenet 10430000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
> 
> - after patching
> [    3.145127] bcmgenet 10430000.ethernet eth0: Link is Down
> [    4.189140] bcmgenet 10430000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
> 
>> Florian Fainelli (6):
>>  net: bcmgenet: Remove excessive PHY reset
>>  net: bcmgenet: Use correct dev_id for free_irq
>>  net: bcmgenet: Power on integrated GPHY in bcmgenet_power_up()
>>  net: bcmgenet: Determine PHY type before scanning MDIO bus
>>  net: bcmgenet: Delay PHY initialization to bcmgenet_open()
>>  net: bcmgenet: Remove init parameter from bcmgenet_mii_config
>>
>> drivers/net/ethernet/broadcom/genet/bcmgenet.c | 33 +++++-----
>> drivers/net/ethernet/broadcom/genet/bcmgenet.h |  5 +-
>> drivers/net/ethernet/broadcom/genet/bcmmii.c   | 84 ++++++++++++--------------
>> 3 files changed, 59 insertions(+), 63 deletions(-)
>>
>> -- 
>> 2.1.0
>>
> 


-- 
Florian
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html