From: Heiner Kallweit <hkallweit1@gmail.com>
To: Hau <hau@realtek.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Kai-Heng Feng <kai.heng.feng@canonical.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 17:33:47 +0100 [thread overview]
Message-ID: <f02b9df7-d57d-d7b6-c0fd-e03e6681dcc8@gmail.com> (raw)
In-Reply-To: <20200306155824.GH25183@lunn.ch>
On 06.03.2020 16:58, Andrew Lunn wrote:
>> This chip can get fiber info through I2C. It also can detect LOS or control TX Disable via GPIO.
>
I think the question is whether the chip exposes these signals for kernel use.
- Is there any register to read e.g. LOS status from?
- Is the I2C bus accessed only by chip firmware, or can the OS access the I2C bus somehow?
> O.K. Good
>
> You should be looking at using phylink to manage the SFP.
>
> Andrew
>
prev parent reply other threads:[~2020-03-06 16:34 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
2020-03-06 15:58 ` Andrew Lunn
2020-03-06 16:33 ` Heiner Kallweit [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=f02b9df7-d57d-d7b6-c0fd-e03e6681dcc8@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=anthony.wong@canonical.com \
--cc=hau@realtek.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 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.