From: Andrew Lunn <andrew@lunn.ch>
To: Raju Lakkaraju <Raju.Lakkaraju@microsemi.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
Allan Nielsen <Allan.Nielsen@microsemi.com>
Subject: Re: Microsemi VSC 8531/41 PHY Driver
Date: Fri, 29 Jul 2016 10:04:02 +0200 [thread overview]
Message-ID: <20160729080402.GA13798@lunn.ch> (raw)
In-Reply-To: <646450A91FAED74E85C6E9C4D6E936A14532A1E3@avsrvexchmbx1.microsemi.net>
On Thu, Jul 28, 2016 at 06:44:37AM +0000, Raju Lakkaraju wrote:
> Hello Andrew,
>
> Thank you for given valuable comments.
> Please see the my responses inline.
>
> Thanks,
> Raju
>
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@lunn.ch]
> Sent: Tuesday, July 26, 2016 6:14 PM
> To: Raju Lakkaraju
> Cc: netdev@vger.kernel.org; f.fainelli@gmail.com; Allan Nielsen
> Subject: Re: Microsemi VSC 8531/41 PHY Driver
>
> EXTERNAL EMAIL
>
>
> > +/* RGMII Rx Clock delay value change with board lay-out */ static u8
> > +rgmii_rx_clk_delay = RGMII_RX_CLK_DELAY_1_1_NS;
>
> Doesn't this stop you from having a board with two PHYs with different layouts? You should be getting this value from the device tree.
>
> Raju: As of now, RGMII Rx clock delay value should be 1.1 nsec as optimized/recommended value.
> We tested on Beaglebone Black with VSC 8531 PHY.
> We would like to provide new function to configure correct/require value based on PHY layouts
> alone with other RGMII configuration parameters as part of our next implementation.
Hi Raju
Please can you use standard email quoting, just like everybody else does.
Andrew
next prev parent reply other threads:[~2016-07-29 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 9:49 Microsemi VSC 8531/41 PHY Driver Raju Lakkaraju
2016-07-26 11:55 ` Andrew Lunn
2016-07-26 12:20 ` Raju Lakkaraju
2016-07-26 12:43 ` Andrew Lunn
2016-07-28 6:44 ` Raju Lakkaraju
2016-07-28 17:35 ` Florian Fainelli
2016-08-04 9:31 ` Nagaraju Lakkaraju
2016-07-29 8:04 ` Andrew Lunn [this message]
2016-07-29 8:17 ` Andrew Lunn
2016-08-04 9:17 ` Nagaraju Lakkaraju
2016-08-05 12:24 ` Nagaraju Lakkaraju
2016-08-16 19:41 ` Andrew Lunn
2016-08-16 19:48 ` Andrew Lunn
2016-09-08 8:39 ` [PATCH net-next 1/1] net: phy: Fixed checkpatch errors for Microsemi PHYs Raju Lakkaraju
2016-09-10 1:16 ` 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=20160729080402.GA13798@lunn.ch \
--to=andrew@lunn.ch \
--cc=Allan.Nielsen@microsemi.com \
--cc=Raju.Lakkaraju@microsemi.com \
--cc=f.fainelli@gmail.com \
--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 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).