From: Johan Hovold <johan@kernel.org>
To: Bruno Thomsen <bth@kamstrup.dk>
Cc: Johan Hovold <johan@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"bruno.thomsen@gmail.com" <bruno.thomsen@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: phy/micrel: KSZ8031RNL RMII clock reconfiguration bug
Date: Mon, 17 Nov 2014 17:00:38 +0100 [thread overview]
Message-ID: <20141117160038.GB14630@localhost> (raw)
In-Reply-To: <915054555B5659448ACF8A70E114824D01704BD71E@Exchange2010.kamstrup.dk>
On Mon, Nov 17, 2014 at 02:56:45PM +0000, Bruno Thomsen wrote:
> > Did you specify a led-mode as well, or was the Operation Mode Strap
> > Override (OMSO) write the first access after the soft reset?
>
> No led-mode was specified so OMSO was the first write.
Did you try setting a led-mode before changing the clock mode? Perhaps
that could also trigger the problem (i.e. when the clock-mode change
isn't the first write after reset).
> > Would you able to test my series on your setup, and possibly a
> > couple of diagnostic patches on top?
>
> Sure, I can try later this week.
Much appreciated. I'll resend the last part of the series (which is not
already in linux-next) and make sure to put you on CC.
Thanks,
Johan
prev parent reply other threads:[~2014-11-17 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 14:48 [PATCH] phy/micrel: KSZ8031RNL RMII clock reconfiguration bug Bruno Thomsen
2014-10-10 10:02 ` Angelo Dureghello
2014-10-10 11:24 ` Bruno Thomsen
2014-10-14 16:41 ` David Miller
2014-11-11 19:41 ` Johan Hovold
2014-11-12 12:17 ` Bruno Thomsen
2014-11-15 14:18 ` Johan Hovold
2014-11-17 14:56 ` Bruno Thomsen
2014-11-17 16:00 ` Johan Hovold [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=20141117160038.GB14630@localhost \
--to=johan@kernel.org \
--cc=bruno.thomsen@gmail.com \
--cc=bth@kamstrup.dk \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).