From: Marek Vasut <marex@denx.de>
To: Alexandre Pereira da Silva <aletes.xgr@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Hector Palacios <hector.palacios@digi.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: KSZ8051 breakage
Date: Wed, 18 Sep 2013 16:20:06 +0200 [thread overview]
Message-ID: <201309181620.06885.marex@denx.de> (raw)
In-Reply-To: <CAAAP30HuZBw-Vo0ZgbYd_-BqTQwjDFpTDpUrSrwRTSNRmXtBiA@mail.gmail.com>
Dear Alexandre Pereira da Silva,
> Hi,
>
> The commit
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/driv
> ers/net/phy/micrel.c?id=b818d1a7f72575eef17e00dc4085512c9cc8897dbreaks
> KSZ8051MNL phy
>
> Micrel gone wrong here. The PHY ID of KSZ8051 is the same as KSZ8031, even
> the revision code matches.
>
> In my custom board, I cannot run these instructions or else my cpu will
> lock up:
> const u16 val = KSZPHY_OMSO_B_CAST_OFF | KSZPHY_OMSO_RMII_OVERRIDE;
> phy_write(phydev, MII_KSZPHY_OMSO, val);
>
> This is a board property and not a phy one. Ideally, the phy should be
> correctly strapped at the hardware level for the board in question, so no
> changes in this registers should be needed.
>
> I think we could add a OF property to set these options, what do you think?
> If that, I would also propose to convert the 50MHZ flag to OF as well.
>
> Other option is to handle this the same way as the 50MHZ flag, that is
> being set by board code.
I wouldn't mind, but we should use something generic the other PHYs can use as
well.
Best regards,
Marek Vasut
parent reply other threads:[~2013-09-18 14:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAAAP30HuZBw-Vo0ZgbYd_-BqTQwjDFpTDpUrSrwRTSNRmXtBiA@mail.gmail.com>]
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=201309181620.06885.marex@denx.de \
--to=marex@denx.de \
--cc=aletes.xgr@gmail.com \
--cc=davem@davemloft.net \
--cc=hector.palacios@digi.com \
--cc=linux-kernel@vger.kernel.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.