From: Daniel Mack <daniel@zonque.org>
To: Mason <slash.tmp@free.fr>, netdev@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Mugunthan <mugunthanvnm@ti.com>,
"David S. Miller" <davem@davemloft.net>,
Matus Ujhelyi <ujhelyi.m@gmail.com>
Subject: Re: Atheros 8035 PHY only works when at803x_config_init() is commented out
Date: Fri, 10 Apr 2015 12:21:58 +0200 [thread overview]
Message-ID: <5527A446.8030202@zonque.org> (raw)
In-Reply-To: <55279F65.9090202@free.fr>
On 04/10/2015 12:01 PM, Mason wrote:
> Daniel Mack wrote:
>> A company I used to work with ships various hardware models in
>> quantities which features this chip, and they're using the unpatched
>> mainline kernel version of the driver.
Meh. I just double-checked the references again and figured the final
verions of the hardware design featured a 8030 model, not 8035. Sorry
for that.
So there might be a difference, and maybe the 8035 needs special
treatment. Then again, Fabio said he has a 8035 working.
>>> Maybe on my PHY, writing BMCR_RESET to BMCR triggers a SW reset,
>>> while it triggers a HW reset on other boards?
>>
>> AFAIK, the chip does not do this, no. But even if it did,
>
> Did you forget to finish that sentence? :-)
Even if it did, the kernel driver should still be able to set up the
device just fine.
>> I'd still go and check if there's anything in one of the chained
>> bootloaders that does some magic. One other thing that might give you a
>> hint is to manually pull the RESET line low for a short time right when
>> the kernel decompressor is started. That way, the kernel has to deal
>> with a device that has just seen a hardware reset. Just see if that
>> makes any difference.
>
> I'd force a HW reset by jiggling the appropriate GPIO pin?
> Like you did in the at803x.c driver?
Yes. But that's just to gain more ideas where to look for, and possibly
find a pattern.
Daniel
next prev parent reply other threads:[~2015-04-10 10:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 16:28 Atheros 8035 PHY only works when at803x_config_init() is commented out Mason
2015-04-08 17:29 ` Florian Fainelli
2015-04-08 21:37 ` Mason
2015-04-09 11:44 ` Mason
2015-04-09 13:15 ` Mason
2015-04-09 13:36 ` Daniel Mack
2015-04-09 14:38 ` Mason
2015-04-09 15:22 ` Mason
2015-04-09 15:32 ` Daniel Mack
2015-04-09 15:58 ` Mason
2015-04-09 17:25 ` Florian Fainelli
2015-04-09 18:52 ` Mason
2015-04-09 19:00 ` Florian Fainelli
2015-04-09 19:30 ` Mason
2015-04-09 20:26 ` Florian Fainelli
2015-04-09 22:10 ` Mason
2015-04-09 22:30 ` Florian Fainelli
2015-04-09 22:31 ` Fabio Estevam
2015-04-10 10:27 ` Fabio Estevam
2015-04-10 15:04 ` Mason
2015-04-10 9:33 ` Daniel Mack
2015-04-10 10:01 ` Mason
2015-04-10 10:21 ` Daniel Mack [this message]
2015-04-09 19:05 ` Mason
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=5527A446.8030202@zonque.org \
--to=daniel@zonque.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=slash.tmp@free.fr \
--cc=ujhelyi.m@gmail.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).