From: Andrew Lunn <andrew@lunn•ch>
To: Teresa Remmet <t.remmet@phytec•de>
Cc: Alexandru Gagniuc <alex.g@adaptrum•com>,
"David S. Miller" <davem@davemloft•net>,
Mugunthan V N <mugunthanvnm@ti•com>,
Grygorii Strashko <grygorii.strashko@ti•com>,
linux-omap@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: net: ti: cpsw-phy-sel: RGMII is not working on AM335x
Date: Wed, 11 Jan 2017 16:14:07 +0100 [thread overview]
Message-ID: <20170111151407.GW22820@lunn.ch> (raw)
In-Reply-To: <1484122463.3777.1.camel@phytec.de>
> So I wonder what is correct now? As for me the patch makes RGMII unusable.
> Has anyone an explanation?
Hi Teresa
In your device tree, what phy-mode do you have?
And does your hardware require an RGMII delay in order that it works?
Andrew
next prev parent reply other threads:[~2017-01-11 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 8:14 net: ti: cpsw-phy-sel: RGMII is not working on AM335x Teresa Remmet
2017-01-11 15:14 ` Andrew Lunn [this message]
2017-01-11 15:57 ` Teresa Remmet
2017-01-11 20:18 ` Alex
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=20170111151407.GW22820@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=alex.g@adaptrum$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=grygorii.strashko@ti$(echo .)com \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=mugunthanvnm@ti$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=t.remmet@phytec$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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