From: Andrew Lunn <andrew@lunn.ch>
To: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
netdev@vger.kernel.org,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Mylène Josserand" <mylene.josserand@bootlin.com>
Subject: Re: Handling an Extra Signal at PHY Reset
Date: Thu, 21 Feb 2019 02:49:38 +0100 [thread overview]
Message-ID: <20190221014938.GQ14879@lunn.ch> (raw)
In-Reply-To: <e647050a0fbadb8445cf6a7a5a2ccfbfd0865592.camel@bootlin.com>
On Tue, Feb 19, 2019 at 10:14:20AM +0100, Paul Kocialkowski wrote:
> Hi,
>
> We are dealing with an Ethernet PHY (Marvell 88E1512) that comes with a
> CONFIG pin that must be connected to one of the other pins of the PHY
> to configure the LSB of the PHY address as well as I/O voltages (see
> section 2.18.1 Hardware Configuration of the datasheet). It must be
> connected "soon after reset" for the PHY to be correctly configured.
Hi Paul
Turns out the datasheet is publicly available.
So you can at run-time configure the voltage. Page 2, register 24, bit
13.
So back to my last question. Can you address the PHY without using the
switch? Even if it has the wrong voltage?
If you can, you could set the correct voltage in the probe() function.
Andrew
next prev parent reply other threads:[~2019-02-21 1:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 9:14 Handling an Extra Signal at PHY Reset Paul Kocialkowski
2019-02-19 9:36 ` Thomas Petazzoni
2019-02-19 12:53 ` Paul Kocialkowski
2019-02-19 13:36 ` Andrew Lunn
2019-02-19 15:06 ` Paul Kocialkowski
2019-02-19 15:40 ` Andrew Lunn
2019-02-20 8:06 ` Thomas Petazzoni
2019-02-19 16:07 ` Florian Fainelli
2019-02-21 9:05 ` Paul Kocialkowski
2019-02-21 1:49 ` Andrew Lunn [this message]
2019-02-21 8:50 ` Paul Kocialkowski
2019-02-21 14:04 ` Andrew Lunn
2019-02-27 8:19 ` Paul Kocialkowski
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=20190221014938.GQ14879@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=mylene.josserand@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=thomas.petazzoni@bootlin.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 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.