From: Oliver Graute <oliver.graute@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
netdev@vger.kernel.org, f.fainelli@gmail.com, johan@kernel.org,
bth@kamstrup.dk
Subject: Re: Micrel Phy KSZ8031 clock select setting in dts
Date: Wed, 22 Jun 2016 10:18:06 +0200 [thread overview]
Message-ID: <20160622081806.GA15450@graute-opti> (raw)
In-Reply-To: <20160621061603.GV9677@pengutronix.de>
On 21/06/16, Sascha Hauer wrote:
> On Mon, Jun 20, 2016 at 07:14:06PM +0200, Oliver Graute wrote:
> > On 20/06/16, Andrew Lunn wrote:
> > > > &fec1 {
> > > > pinctrl-names = "default";
> > > > pinctrl-0 = <&pinctrl_enet1>;
> > > > phy-mode = "rmii";
> > > > micrel,rmii-reference-clock-select-25-mhz;
> > > > clocks,rmii-ref;
> > >
> > > You are adding phy properties, not MAC properties. Please put them in
> > > the phy node.
> >
> > yes, you are right. I fixed this and added the clock like sascha and
> > sergei proposed. (thx to you all)
> >
> > my dts node now looks like this:
> >
> > &fec1 {
> > pinctrl-names = "default";
> > pinctrl-0 = <&pinctrl_enet1>;
> > phy-mode = "rmii";
> > status = "okay";
> >
> > mdio {
> > #address-cells = <1>;
> > #size-cells = <0>;
> >
> > ethphy0: ethernet-phy@0 {
> > compatible = "micrel,ksz8031";
> > micrel,rmii-reference-clock-select-25-mhz;
> > clocks = <&mdc>;
> > clock-names = "rmii-ref";
> > phy-handle = <ðphy0>;
> > reg = <0>;
> > };
> >
> > };
> >
> > mdc: rmii-ref {
> > #clock-cells = <0>;
> > compatible ="fixed-clock";
> > clock-frequency = <50000000>;
> > };
> > };
>
> To make that clear: Which phy do you have: KSZ8031RNL or KSZ8031RNLI?
> The former has 25MHz default input clock whereas the latter has 50MHz
> default input clock.
according the circuit diagram I have KSZ803RNLI.
>
> I assume you have the KSZ8031RNL and use it with 50MHz (so the non
> default case), hence you have to set the KSZPHY_RMII_REF_CLK_SEL bit.
> The "micrel,rmii-reference-clock-select-25-mhz" means "Setting the bit
> selects 25MHz" which is not the case here, so you have to remove the
> property.
ok if I removing the property "micrel,rmii-reference-clock-select-25-mhz"
and removing my changes in micrel.c it now works as well.
> Could it be that your initial setting just did not work because of other
> mistakes, like no correct clock?
yes that was the case. Many thanks for the helpful notes.
Best Regards,
Oliver
next prev parent reply other threads:[~2016-06-22 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 13:04 Micrel Phy KSZ8031 clock select setting in dts Oliver Graute
2016-06-17 13:48 ` Sergei Shtylyov
2016-06-19 19:29 ` Oliver Graute
2016-06-20 6:21 ` Sascha Hauer
2016-06-20 12:08 ` Oliver Graute
2016-06-20 12:45 ` Andrew Lunn
2016-06-20 17:14 ` Oliver Graute
2016-06-21 6:16 ` Sascha Hauer
2016-06-22 8:18 ` Oliver Graute [this message]
2016-06-20 12:56 ` Sergei Shtylyov
2016-06-20 13:12 ` Sascha Hauer
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=20160622081806.GA15450@graute-opti \
--to=oliver.graute@gmail.com \
--cc=andrew@lunn.ch \
--cc=bth@kamstrup.dk \
--cc=f.fainelli@gmail.com \
--cc=johan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sergei.shtylyov@cogentembedded.com \
/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).