From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: iMX6Q FEC: transmit queue 0 timed out
Date: Mon, 2 Jun 2014 14:33:53 +0100 [thread overview]
Message-ID: <20140602133352.GC933@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOpc7mFbJQNeBmOG0C-Qn856MmhtUkTq=QeDPC-EWXryi6sFGg@mail.gmail.com>
On Mon, Jun 02, 2014 at 03:15:21PM +0200, Holger Schurig wrote:
> Transmit clocking and pinmux? Do you mean ENET_TX_EN? Yep, that's
> set. Somehow barebox can send, it's just Linux that doesn't want to do
> it. Note that ENET_TX_CLK is not muxed, as it is for MII, not for
> RMII.
>
> In case I confuse what you meant, here are excerpts from my DTS:
It's probably ENET_REF_CLK that's the cause of the problem.
> pinctrl_fec: fecgrp {
> fsl,pins = <
> MX6QDL_PAD_ENET_TXD0__ENET_TX_DATA0 0x1b030
> MX6QDL_PAD_ENET_TXD1__ENET_TX_DATA1 0x1b030
> MX6QDL_PAD_ENET_TX_EN__ENET_TX_EN 0x1b030
> MX6QDL_PAD_ENET_RXD0__ENET_RX_DATA0 0x1b030
> MX6QDL_PAD_ENET_RXD1__ENET_RX_DATA1 0x1b030
> MX6QDL_PAD_ENET_RX_ER__ENET_RX_ER 0x1b030
> MX6QDL_PAD_ENET_MDIO__ENET_MDIO 0x0B850
> MX6QDL_PAD_ENET_MDC__ENET_MDC 0x1b030
> MX6QDL_PAD_ENET_CRS_DV__ENET_RX_EN 0x1b030
> MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0x1b030
> >;
> };
On the Microsom, I need:
MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0xc0000000
Does that work for you?
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-06-02 13:33 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 [this message]
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
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=20140602133352.GC933@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).