All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hau <hau@realtek.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	nic_swsd <nic_swsd@realtek.com>, Andrew Lunn <andrew@lunn.ch>
Subject: RE: [PATCH net-next v5] r8169: add support for rtl8168h(revid 0x2a) + rtl8211fs fiber application
Date: Fri, 9 Dec 2022 15:29:29 +0000	[thread overview]
Message-ID: <8b38c9f4552346ed84ba204b3e5edd5d@realtek.com> (raw)
In-Reply-To: <7f460a37-d6f5-603f-2a6c-c65bae56f76b@gmail.com>

> 
> OK, I think I get a better idea of your setup.
> So it seems RTL8211FS indeed acts as media converter. Link status on MDI
> side of RTL8211FS reflects link status on fiber/serdes side.
> RTL8168H PHY has no idea whether it's connected to RJ45 magnetics or to the
> MDI side of a RTL8211FS.
> 
> I think for configuring RTL8211FS you have two options:
> 1. Extend the Realtek PHY driver to support RTL8211FS fiber mode 2.
> Configure RTL8211FS from userspace (phytool, mii-tool, ..). However to be
> able to do this you may need to add a dummy netdevice
>    that RTL8211FS is attached to. When going with this option it may be better
> to avoid phylib taking control of RTL8211FS.
>    This can be done by setting the phy_mask of the bit-banged mii_bus.

Thanks for your advaice.
Is that possible for us to register a PHY fixup function(phy_register_fixup()) to setup rtl8211fs instead of setup it in PHY driver?

 ------Please consider the environment before printing this e-mail.


  reply	other threads:[~2022-12-09 15:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 14:39 [PATCH net-next v5] r8169: add support for rtl8168h(revid 0x2a) + rtl8211fs fiber application Chunhao Lin
2022-12-03 14:54 ` Heiner Kallweit
2022-12-03 17:47   ` Andrew Lunn
2022-12-04 22:40 ` Heiner Kallweit
2022-12-07 17:43   ` Hau
2022-12-07 21:41     ` Heiner Kallweit
2022-12-08 15:59       ` Hau
2022-12-08 21:35         ` Heiner Kallweit
2022-12-09 15:29           ` Hau [this message]
2022-12-09 23:02             ` Heiner Kallweit
2022-12-12 14:11               ` Hau
2022-12-12 22:17                 ` Heiner Kallweit
2022-12-13 16:23                   ` Hau

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=8b38c9f4552346ed84ba204b3e5edd5d@realtek.com \
    --to=hau@realtek.com \
    --cc=andrew@lunn.ch \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.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.