From: Jaeden Amero <jaeden.amero@ni.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] net/phy: micrel: Center FLP timing at 16ms
Date: Fri, 05 Jun 2015 17:50:15 -0500 [thread overview]
Message-ID: <557227A7.2080603@ni.com> (raw)
In-Reply-To: <5572261A.1070801@gmail.com>
On 06/05/2015 05:43 PM, Florian Fainelli wrote:
> On 05/06/15 15:40, Jaeden Amero wrote:
>> Link failures have been observed when using the KSZ9031 with HP 1810-8G
>> and HP 1910-8G network switches. Center the FLP timing at 16ms to help
>> avoid intermittent link failures.
>>
>> From the KSZ9031RNX and KSZ9031MNX data sheets revision 2.2, section
>> "Auto-Negotiation Timing":
>> The KSZ9031[RNX or MNX] Fast Link Pulse (FLP) burst-to-burst
>> transmit timing for Auto-Negotiation defaults to 8ms. IEEE 802.3
>> Standard specifies this timing to be 16ms +/-8ms. Some PHY link
>> partners need to receive the FLP with 16ms centered timing;
>> otherwise, there can be intermittent link failures and long
>> link-up times.
>>
>> After KSZ9031[RNX or MNX] power-up/reset, program the following
>> register sequence to set the FLP timing to 16ms
>>
>> Write Register Dh = 0x0000 // Set up register address for MMD – Device Address 0h
>> Write Register Eh = 0x0004 // Select Register 4h of MMD – Device Address 0h
>> Write Register Dh = 0x4000 // Select register data for MMD – Device Address 0h, Register 4h
>> Write Register Eh = 0x0006 // Write value 0x0006 to MMD – Device Address 0h, Register 4h
>> Write Register Dh = 0x0000 // Set up register address for MMD – Device Address 0h
>> Write Register Eh = 0x0003 // Select Register 3h of MMD – Device Address 0h
>> Write Register Dh = 0x4000 // Select register data for MMD – Device Address 0h, Register 3h
>> Write Register Eh = 0x1A80 // Write value 0x1A80 to MMD – Device Address 0h, Register 3h
>> Write Register 0h, Bit [9] = 1 // Restart Auto-Negotiation
>
> Quoting a portion of the data-sheet on how to do this programming is
> very strange considering that the code is going to be the reference, not
> the commit message.
I included it for lack of something better to quote that explained
which values to set when. I'd be happy to revise the message as this
appears too strange.
> Other than that, this looks reasonable.
Thanks very much for the review.
Cheers,
Jaeden
next prev parent reply other threads:[~2015-06-05 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 22:40 [PATCH v3 0/3] net/phy: micrel: Center FLP timing at 16ms Jaeden Amero
2015-06-05 22:40 ` [PATCH v3 1/3] net/phy: micrel: Be more const correct Jaeden Amero
2015-06-05 22:40 ` [PATCH v3 2/3] net/phy: micrel: Comment MMD address of extended registers Jaeden Amero
2015-06-05 22:40 ` [PATCH v3 3/3] net/phy: micrel: Center FLP timing at 16ms Jaeden Amero
2015-06-05 22:40 ` Jaeden Amero
2015-06-05 22:43 ` Florian Fainelli
2015-06-05 22:50 ` Jaeden Amero [this message]
2015-06-05 22:44 ` [PATCH v3 0/3] " 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=557227A7.2080603@ni.com \
--to=jaeden.amero@ni.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.