From: Hau <hau@realtek.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Linux Netdev List <netdev@vger.kernel.org>,
"Kernel development list" <linux-kernel@vger.kernel.org>,
Anthony Wong <anthony.wong@canonical.com>,
Jason Yen <jason.yen@canonical.com>
Subject: RE: SFP+ support for 8168fp/8117
Date: Fri, 6 Mar 2020 15:34:47 +0000 [thread overview]
Message-ID: <1252a766545b48aeafdff9702566565c@realtek.com> (raw)
In-Reply-To: 20200304152849.GE3553@lunn.ch
>
> > > Hi Kai-Heng,
> > >
> > > For adding SFP+ support for rtl8168fp, 1.Some power saving features
> > > must be disabled, like APDLS/EEE/EEEPLUS...
> > > 2.PHY capability must be set to auto-negation.
> > >
> > > I am kind of busy this week. I will try to add support for this chip
> > > into
> > upstream next week.
> >
> > Is it possible to access the I2C bus? The GPIO lines from the SFP
> > socket like LOS, TX Disable?
> >
This chip can get fiber info through I2C. It also can detect LOS or control TX Disable via GPIO.
Thanks,
Hau
------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2020-03-06 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 6:59 SFP+ support for 8168fp/8117 Kai Heng Feng
2020-01-02 15:21 ` Andrew Lunn
2020-01-02 16:46 ` Kai-Heng Feng
2020-01-02 21:24 ` Heiner Kallweit
2020-01-03 4:53 ` Kai-Heng Feng
2020-02-13 6:14 ` Kai-Heng Feng
2020-02-14 9:07 ` Hau
2020-02-17 6:37 ` Kai Heng Feng
2020-02-19 14:22 ` Hau
2020-02-19 14:48 ` Kai-Heng Feng
2020-02-27 8:49 ` Kai-Heng Feng
2020-03-04 15:24 ` Hau
2020-03-04 15:28 ` Andrew Lunn
2020-03-05 12:36 ` Hau
2020-03-06 15:34 ` Hau [this message]
2020-03-06 15:58 ` Andrew Lunn
2020-03-06 16:33 ` Heiner Kallweit
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=1252a766545b48aeafdff9702566565c@realtek.com \
--to=hau@realtek.com \
--cc=andrew@lunn.ch \
--cc=anthony.wong@canonical.com \
--cc=hkallweit1@gmail.com \
--cc=jason.yen@canonical.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).