From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: iMX6Q FEC: transmit queue 0 timed out
Date: Tue, 22 Jul 2014 16:15:38 +0800 [thread overview]
Message-ID: <20140722081536.GD5485@dragon> (raw)
In-Reply-To: <CAOpc7mHvddM1bCex13yPTRrEkFqYvk2YHYajZeMn+MG83neUBA@mail.gmail.com>
On Wed, Jul 16, 2014 at 10:41:10AM +0200, Holger Schurig wrote:
> Andy,
>
> to revive an old thread: I now got ethernet working. Basically, I
> needed to set the system so that the PHY is generating the ref-clock.
> I found even code in arch/arm/mach-imx/mach-imx6q.c that controls
> setting of GPR1[21] from the device tree. However, I wasn't really
> able to come up with a device-tree that triggers the code
> IMX6Q_GPR1_ENET_CLK_SEL_PAD. For example, Neither
> Documentation/devicetree/bindings/net/fsl-fec.txt nor any other file
> there mention anything on how to do this.
>
> Currently I disable the 3rd clock. I changed the default
> clocks = <&clks 117>, <&clks 117>, <&clks 190>;
> clock-names = "ipg", "ahb", "ptp";
> (from imx6qdl.dtsi) to my dts:
> clocks = <&clks 117>, <&clks 117>;
> clock-names = "ipg", "ahb";
>
> Would I have needed to create some dummy clock, e.g. "ext-phy-clk" and
> specified that as a third clock in my dts?
Since in your setup PHY is generating the reference clock, you need to
define this clock in your board dts, and overwrite the 'ptp' clock with
it, something like the following.
clocks {
#address-cells = <1>;
#size-cells = <0>;
rmii_clk: clock at 0 {
compatible = "fixed-clock";
reg = <0>;
#clock-cells = <0>;
clock-frequency = <25000000>; /* 25MHz for example */
clock-output-names = "rmii_ref_clk";
};
};
&fec {
clocks = <&clks 117>, <&clks 117>, <&rmii_clk>;
};
prev parent reply other threads:[~2014-07-22 8:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 12:27 iMX6Q FEC: transmit queue 0 timed out Holger Schurig
2014-06-02 12:42 ` Russell King - ARM Linux
2014-06-02 13:15 ` Holger Schurig
2014-06-02 13:33 ` Russell King - ARM Linux
2014-06-02 14:11 ` Holger Schurig
2014-06-03 3:22 ` fugang.duan at freescale.com
2014-06-03 15:45 ` Holger Schurig
[not found] ` <a97d34741f694cd2b89b4c7f0bebc114@BLUPR03MB373.namprd03.prod.outlook.com>
2014-06-04 11:50 ` Holger Schurig
2014-06-04 13:50 ` Russell King - ARM Linux
2014-07-16 8:41 ` Holger Schurig
2014-07-22 8:15 ` Shawn Guo [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=20140722081536.GD5485@dragon \
--to=shawn.guo@freescale.com \
--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).