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: Wed, 4 Jun 2014 14:50:47 +0100 [thread overview]
Message-ID: <20140604135047.GC23430@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOpc7mHxYVOUQVcTqPH9pLXtqNaxgeqJGoJ=U4cRNgSzOpj7Wg@mail.gmail.com>
On Wed, Jun 04, 2014 at 01:50:54PM +0200, Holger Schurig wrote:
> The PHY can be controlled if he creates or consume the REF CLK with
> the signal on it's pin nINTSEL during the low->high transition of the
> reset. I guess that whoever toggles this (i must dig into it, but the
> reset pin is described in the device tree) doesn't care (or can't
> care) how nINTSEL is set and so in Linux mode the modes of the two
> devices don't harmonize.
It sounds like you need to add appropriate pull-ups/pull-downs on the
iMX6 configure the phy. This is why imx6qdl-microsom-ar8035.dtsi has
different settings from the normal RGMII pullups/downs - in the case
of AR8035, a number of pins including the receive pins determine reset
options. See the comments in that file concerning "pin strapping".
--
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-04 13:50 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 [this message]
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=20140604135047.GC23430@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.