From: Dinh Nguyen <dinguyen@kernel.org>
To: "Ooi, Joyce" <joyce.ooi@intel.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
See Chin Liang <chin.liang.see@intel.com>,
Yves Vandervennet <yves.vandervennet@intel.com>,
Ong Hean Loong <hean.loong.ong@intel.com>
Subject: Re: [PATCH] arm64: dts: stratix10: Change pad skew values for EMAC0 PHY driver
Date: Tue, 24 Apr 2018 10:13:50 -0500 [thread overview]
Message-ID: <cb89395b-b3cc-c9f1-26d4-419803c93b86@kernel.org> (raw)
In-Reply-To: <1524538918-21141-1-git-send-email-joyce.ooi@intel.com>
On 04/23/2018 10:01 PM, Ooi, Joyce wrote:
> The HPS EMAC0 drive strength is changed to 4mA because the initial 8mA
> drive strength has caused CE test to fail. This requires changes on the
> pad skew for EMAC0 PHY driver. Based on several measurements done, Tx
> clock does not require the extra 0.96ns delay.
>
> Signed-off-by: Ooi, Joyce <joyce.ooi@intel.com>
> ---
> .../boot/dts/altera/socfpga_stratix10_socdk.dts | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
> index 0007564..8785f78 100644
> --- a/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
> +++ b/arch/arm64/boot/dts/altera/socfpga_stratix10_socdk.dts
> @@ -79,7 +79,7 @@
> rxd2-skew-ps = <420>; /* 0ps */
> rxd3-skew-ps = <420>; /* 0ps */
> txen-skew-ps = <0>; /* -420ps */
> - txc-skew-ps = <1860>; /* 960ps */
> + txc-skew-ps = <900>; /* 0ps */
> rxdv-skew-ps = <420>; /* 0ps */
> rxc-skew-ps = <1680>; /* 780ps */
> };
>
Applied, thanks!
Dinh
prev parent reply other threads:[~2018-04-24 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 3:01 [PATCH] arm64: dts: stratix10: Change pad skew values for EMAC0 PHY driver Ooi, Joyce
2018-04-24 15:13 ` Dinh Nguyen [this message]
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=cb89395b-b3cc-c9f1-26d4-419803c93b86@kernel.org \
--to=dinguyen@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chin.liang.see@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=hean.loong.ong@intel.com \
--cc=joyce.ooi@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=yves.vandervennet@intel.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).