From: richard.zhao@linaro.org (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] arm/imx6q-sabrelite: add enet phy ksz9021rn fixup
Date: Tue, 13 Dec 2011 16:24:18 +0800 [thread overview]
Message-ID: <1323764658-26381-1-git-send-email-richard.zhao@linaro.org> (raw)
In-Reply-To: <1323757530-19402-1-git-send-email-richard.zhao@linaro.org>
tune phy RGMII pad skew.
Signed-off-by: Richard Zhao <richard.zhao@linaro.org>
---
arch/arm/mach-imx/mach-imx6q.c | 21 +++++++++++++++++++++
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-imx/mach-imx6q.c b/arch/arm/mach-imx/mach-imx6q.c
index d24d6c4..b3dcdcb 100644
--- a/arch/arm/mach-imx/mach-imx6q.c
+++ b/arch/arm/mach-imx/mach-imx6q.c
@@ -16,6 +16,8 @@
#include <linux/of.h>
#include <linux/of_irq.h>
#include <linux/of_platform.h>
+#include <linux/phy.h>
+#include <linux/micrel_phy.h>
#include <asm/hardware/cache-l2x0.h>
#include <asm/hardware/gic.h>
#include <asm/mach/arch.h>
@@ -23,8 +25,27 @@
#include <mach/common.h>
#include <mach/hardware.h>
+/* For imx6q sabrelite board: set KSZ9021RN RGMII pad skew */
+static int ksz9021rn_phy_fixup(struct phy_device *phydev)
+{
+ /* min rx data delay */
+ phy_write(phydev, 0x0b, 0x8105);
+ phy_write(phydev, 0x0c, 0x0000);
+
+ /* max rx/tx clock delay, min rx/tx control delay */
+ phy_write(phydev, 0x0b, 0x8104);
+ phy_write(phydev, 0x0c, 0xf0f0);
+ phy_write(phydev, 0x0b, 0x104);
+
+ return 0;
+}
+
static void __init imx6q_init_machine(void)
{
+ if (of_machine_is_compatible("fsl,imx6q-sabrelite"))
+ phy_register_fixup_for_uid(PHY_ID_KSZ9021, MICREL_PHY_ID_MASK,
+ ksz9021rn_phy_fixup);
+
of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL);
imx6q_pm_init();
--
1.7.5.4
next prev parent reply other threads:[~2011-12-13 8:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 6:25 [PATCH V2 0/7] imx: add imx6 sabrelite board Richard Zhao
2011-12-13 6:25 ` [PATCH V2 1/7] dts/imx: rename gpio labels to consistent with hw spec Richard Zhao
2011-12-13 9:41 ` Shawn Guo
2011-12-13 10:40 ` Richard Zhao
2011-12-13 6:25 ` [PATCH V2 2/7] arm/imx6: add imx6q sabrelite board support Richard Zhao
2011-12-13 11:56 ` Shawn Guo
2011-12-13 12:54 ` Richard Zhao
2011-12-13 13:33 ` Shawn Guo
2011-12-14 11:05 ` Sascha Hauer
2011-12-14 14:11 ` Richard Zhao
2011-12-13 6:25 ` [PATCH V2 3/7] arm/imx: cpufreq: add multi-core support Richard Zhao
2011-12-13 6:25 ` [PATCH V2 4/7] arm/imx: fix cpufreq section mismatch Richard Zhao
2011-12-14 0:47 ` Richard Zhao
2011-12-13 6:25 ` [PATCH V2 5/7] arm/imx: add cpu_voltage to cpu_op Richard Zhao
2011-12-13 6:25 ` [PATCH V2 6/7] arm/imx6q: register arm_clk as cpu_clk to clkdev Richard Zhao
2011-12-13 6:25 ` [PATCH V2 7/7] arm/imx6q: add cpufreq support Richard Zhao
2011-12-13 10:23 ` Sascha Hauer
2011-12-13 10:38 ` Richard Zhao
2011-12-13 19:04 ` Rob Lee
2011-12-14 1:29 ` Richard Zhao
2011-12-13 12:19 ` Shawn Guo
2011-12-13 14:20 ` Sascha Hauer
2011-12-13 15:01 ` Richard Zhao
2011-12-13 8:24 ` Richard Zhao [this message]
2011-12-13 12:07 ` [PATCH 1/1] arm/imx6q-sabrelite: add enet phy ksz9021rn fixup Shawn Guo
2011-12-13 12:13 ` Richard Zhao
2011-12-13 12:47 ` Shawn Guo
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=1323764658-26381-1-git-send-email-richard.zhao@linaro.org \
--to=richard.zhao@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).