From: Florian Fainelli <f.fainelli@gmail.com>
To: Jaedon Shin <jaedon.shin@gmail.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Petri Gynther <pgynther@google.com>
Subject: Re: [PATCH net-next 0/6] net: bcmgenet: PHY initialization rework
Date: Mon, 20 Jul 2015 13:00:55 -0700 [thread overview]
Message-ID: <55AD5377.6020401@gmail.com> (raw)
In-Reply-To: <BA3C0C60-58CC-4D5F-9FD0-201E29F5542F@gmail.com>
On 17/07/15 06:53, Jaedon Shin wrote:
>> On Jul 17, 2015, at 7:51 AM, Florian Fainelli <f.fainelli@gmail.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
next prev parent reply other threads:[~2015-07-20 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 22:51 [PATCH net-next 0/6] net: bcmgenet: PHY initialization rework Florian Fainelli
2015-07-16 22:51 ` [PATCH net-next 1/6] net: bcmgenet: Remove excessive PHY reset Florian Fainelli
2015-07-16 22:51 ` [PATCH net-next 2/6] net: bcmgenet: Use correct dev_id for free_irq Florian Fainelli
2015-07-16 22:51 ` [PATCH net-next 3/6] net: bcmgenet: Power on integrated GPHY in bcmgenet_power_up() Florian Fainelli
2015-07-16 22:51 ` [PATCH net-next 4/6] net: bcmgenet: Determine PHY type before scanning MDIO bus Florian Fainelli
2015-07-16 22:51 ` [PATCH net-next 5/6] net: bcmgenet: Delay PHY initialization to bcmgenet_open() Florian Fainelli
2015-07-16 22:51 ` [PATCH net-next 6/6] net: bcmgenet: Remove init parameter from bcmgenet_mii_config Florian Fainelli
2015-07-17 13:53 ` [PATCH net-next 0/6] net: bcmgenet: PHY initialization rework Jaedon Shin
2015-07-20 20:00 ` Florian Fainelli [this message]
2015-07-21 3:48 ` David Miller
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=55AD5377.6020401@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=jaedon.shin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pgynther@google.com \
/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;
as well as URLs for NNTP newsgroup(s).