[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210818170846.GF9992@hoboy.vegasvil.org>
Date: Wed, 18 Aug 2021 10:08:46 -0700
From: Richard Cochran <richardcochran@...il.com>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
Cc: linux-kernel@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
netdev@...r.kernel.org, linux-kselftest@...r.kernel.org,
jesse.brandeburg@...el.com, anthony.l.nguyen@...el.com,
davem@...emloft.net, kuba@...nel.org, shuah@...nel.org,
arnd@...db.de, nikolay@...dia.com, cong.wang@...edance.com,
colin.king@...onical.com, gustavoars@...nel.org
Subject: Re: [RFC net-next 0/7] Add basic SyncE interfaces
On Mon, Aug 16, 2021 at 06:07:10PM +0200, Arkadiusz Kubalewski wrote:
> Multiple reference clock sources can be available. PHY ports recover
> the frequency at which the transmitter sent the data on the RX side.
> Alternatively, we can use external sources like 1PPS GPS, etc.
There is a generic PHY subsystem (drivers/phy) used by USB, PCIe, CAN,
and so on. Why not use that?
Thanks,
Richard
Powered by blists - more mailing lists