From: Andrew Lunn <andrew@lunn.ch>
To: Tomas Hlavacek <tmshlvck@gmail.com>
Cc: netdev@vger.kernel.org, Pavol Kor?ek <ikorcek@fit.vutbr.cz>,
Martin Strba?ka <martin.strbacka@nic.cz>
Subject: Re: RFC: blueprint for proxy PHY module
Date: Thu, 25 Feb 2016 16:24:33 +0100 [thread overview]
Message-ID: <20160225152433.GA7681@lunn.ch> (raw)
In-Reply-To: <1456406760.28260.6@smtp.gmail.com>
On Thu, Feb 25, 2016 at 02:26:00PM +0100, Tomas Hlavacek wrote:
> Hello!
>
> We have a board with a MAC in SoC that has SGMII connected through a
> signal switch to either 10/100/1000 wired PHY or to a SFP cage. The
> signal switch is set to pass signal to the wired PHY by default.
> When the MOD-DEF0 pin from SFP cage is low (which acts as a
> transceiver-present signal) the wired PHY is being disconnected and
> the SGMII is passed to the SFP cage. We also have the signal
> connected to a GPIO input, so we can detect the SFP presence from
> software. And there is always-connected MDIO to the wired PHY.
>
> Now I use two different DTBs for testing purposes, one has a
> configuration for the wired PHY and another one uses fixed-link for
> SFP. And I have to reboot in order to switch from one to another.
>
> My idea is to create a "proxy PHY" module that would take state from
> one of two (or more) underlying PHYs and pass it to the NIC driver.
> The selection of the active PHY would come from userspace. (There
> will be a board-specific
> daemon that would react to the GPIO change and set the proper PHY
> accordingly.) Question is how to connect the userspace? I think that
> corresponding file in /sys would do the job, but I am not sure
> whether it is the proper way of doing that. (?)
>
> What do you think about it?
Hi Tomas
Have you looked at Russell Kings phylink patchset?
https://lwn.net/Articles/667055/
Andrew
next prev parent reply other threads:[~2016-02-25 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 13:26 RFC: blueprint for proxy PHY module Tomas Hlavacek
2016-02-25 15:24 ` Andrew Lunn [this message]
2016-02-25 15:31 ` Andrew Lunn
2016-03-02 14:24 ` Tomas Hlavacek
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=20160225152433.GA7681@lunn.ch \
--to=andrew@lunn.ch \
--cc=ikorcek@fit.vutbr.cz \
--cc=martin.strbacka@nic.cz \
--cc=netdev@vger.kernel.org \
--cc=tmshlvck@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