The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Sergej Bauer <sbauer@blackbox.su>,
	"David S. Miller" <davem@davemloft.net>,
	Andrew Lunn <andrew@lunn.ch>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Bryan Whitehead <bryan.whitehead@microchip.com>,
	Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Rob Herring <robh@kernel.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] add virtual PHY for PHY-less devices
Date: Thu, 17 Sep 2020 15:16:30 -0700	[thread overview]
Message-ID: <b708f713-4840-7521-1d3d-e4aba5b3fc5e@gmail.com> (raw)
In-Reply-To: <20200917214030.646-1-sbauer@blackbox.su>



On 9/17/2020 2:40 PM, Sergej Bauer wrote:
> From: sbauer@blackbox.su
> 
>      Here is a kernel related part of my work which was helps to develop brand
> new PHY device.
> 
>      It is migth be helpful for developers work with PHY-less lan743x
> (7431:0011 in my case). It's just a fake virtual PHY which can change speed of
> network card processing as a loopback device. Baud rate can be tuned with
> ethtool from command line or by means of SIOCSMIIREG ioctl. Duplex mode not
> configurable and it's allways DUPLEX_FULL.
> 
>      It also provides module parameter mii_regs for setting initial values of
> IEEE 802.3 Control Register.

You appear to have re-implemented the fixed PHY driver, please use that 
instead of rolling your own.
-- 
Florian

  parent reply	other threads:[~2020-09-17 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 21:40 [PATCH] add virtual PHY for PHY-less devices Sergej Bauer
2020-09-17 22:15 ` Andrew Lunn
2020-09-18  0:17   ` Sergej Bauer
2020-09-18  1:31     ` Florian Fainelli
2020-09-17 22:16 ` Florian Fainelli [this message]
2020-09-18  0:58   ` Sergej Bauer

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=b708f713-4840-7521-1d3d-e4aba5b3fc5e@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=bryan.whitehead@microchip.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sbauer@blackbox.su \
    /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