netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Roelof Berg <rberg@berg-solutions.de>
Cc: netdev@vger.kernel.org
Subject: Re: Is my patch interesting for contribution: FixedPHY support for Microchip LAN743x ?
Date: Sat, 21 Mar 2020 01:43:55 +0100	[thread overview]
Message-ID: <20200321004355.GD2702@lunn.ch> (raw)
In-Reply-To: <DD2042A5-68EA-40A1-A4A9-5A1DCE4F9583@berg-solutions.de>

On Fri, Mar 20, 2020 at 02:18:14PM +0100, Roelof Berg wrote:
> Dear Kernel-Heros,
> 
> for our custom PCB I added FixedPHY support to the Microchip lan743x driver. This allows running a combination of lan7431 (MAC) and Microchip ksz9893 (switch) via a direct MII connection, i.e. without any PHYs in between. The .config determines wether (and how) FixedPHY is used, and the patch has 100%ly no (side-)effect in the default setting.
> 
> Is such a patch interesting for the community ?
> 
> Pro:
> + Supports lan7431<->kaz9893, a cost effective way of doing: PCIe<->2x-RJ45
> + Tested
> + Can be a grep-template for others with the same issue, i.e. adding FixedPHY to their driver
> 
> Con:
> - Maybe a more general approach would be better, that allows connecting any driver to a FixedPhy ? Insread of every driver doing its own thing ?

Hi Roelof

You are welcome to post it.

So far, it has been a case of each MAC driver having its own
implementation. However, if you port the MAC driver to use phylink,
not phylib, phylink will handle the fixed PHY without any additional
code.

	Andrew

      reply	other threads:[~2020-03-21  0:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 13:18 Is my patch interesting for contribution: FixedPHY support for Microchip LAN743x ? Roelof Berg
2020-03-21  0:43 ` Andrew Lunn [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=20200321004355.GD2702@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=netdev@vger.kernel.org \
    --cc=rberg@berg-solutions.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).