From: Richard Cochran <richardcochran@gmail.com> To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com> Cc: linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org, linux-kselftest@vger.kernel.org, jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com, davem@davemloft.net, kuba@kernel.org, shuah@kernel.org, arnd@arndb.de, nikolay@nvidia.com, cong.wang@bytedance.com, colin.king@canonical.com, gustavoars@kernel.org Subject: Re: [RFC net-next 0/7] Add basic SyncE interfaces Date: Wed, 18 Aug 2021 10:05:36 -0700 [thread overview] Message-ID: <20210818170536.GE9992@hoboy.vegasvil.org> (raw) In-Reply-To: <20210816160717.31285-1-arkadiusz.kubalewski@intel.com> On Mon, Aug 16, 2021 at 06:07:10PM +0200, Arkadiusz Kubalewski wrote: > The second part can be used to select the port from which the clock > gets recovered. Each PHY chip can have multiple pins on which the > recovered clock can be propagated. For example, a SyncE-capable PHY > can recover the carrier frequency of the first port, divide it > internally, and output it as a reference clock on PIN 0. This really sounds like its own thing, and not a PHC at all. > Next steps: > - Add CONFIG_SYNCE definition into Kconfig > - Add more configuration interfaces. Aiming at devlink, since this > would be device-wide configuration As a first step, finding an appropriate kernel/user space API would be needed. Thanks, Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Cochran <richardcochran@gmail.com> To: intel-wired-lan@osuosl.org Subject: [Intel-wired-lan] [RFC net-next 0/7] Add basic SyncE interfaces Date: Wed, 18 Aug 2021 10:05:36 -0700 [thread overview] Message-ID: <20210818170536.GE9992@hoboy.vegasvil.org> (raw) In-Reply-To: <20210816160717.31285-1-arkadiusz.kubalewski@intel.com> On Mon, Aug 16, 2021 at 06:07:10PM +0200, Arkadiusz Kubalewski wrote: > The second part can be used to select the port from which the clock > gets recovered. Each PHY chip can have multiple pins on which the > recovered clock can be propagated. For example, a SyncE-capable PHY > can recover the carrier frequency of the first port, divide it > internally, and output it as a reference clock on PIN 0. This really sounds like its own thing, and not a PHC at all. > Next steps: > - Add CONFIG_SYNCE definition into Kconfig > - Add more configuration interfaces. Aiming at devlink, since this > would be device-wide configuration As a first step, finding an appropriate kernel/user space API would be needed. Thanks, Richard
next prev parent reply other threads:[~2021-08-18 17:05 UTC|newest] Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-16 16:07 [RFC net-next 0/7] Add basic SyncE interfaces Arkadiusz Kubalewski 2021-08-16 16:07 ` [Intel-wired-lan] " Arkadiusz Kubalewski 2021-08-16 16:07 ` [RFC net-next 1/7] ptp: Add interface for acquiring DPLL state Arkadiusz Kubalewski 2021-08-16 16:07 ` [Intel-wired-lan] " Arkadiusz Kubalewski 2021-08-16 23:54 ` Richard Cochran 2021-08-16 23:54 ` [Intel-wired-lan] " Richard Cochran 2021-08-17 9:41 ` Machnikowski, Maciej 2021-08-17 9:41 ` [Intel-wired-lan] " Machnikowski, Maciej 2021-08-18 17:02 ` Richard Cochran 2021-08-18 17:02 ` [Intel-wired-lan] " Richard Cochran 2021-08-18 18:14 ` Keller, Jacob E 2021-08-18 18:14 ` Keller, Jacob E 2021-08-18 22:36 ` Machnikowski, Maciej 2021-08-18 22:36 ` [Intel-wired-lan] " Machnikowski, Maciej 2021-08-19 15:34 ` Richard Cochran 2021-08-19 15:34 ` [Intel-wired-lan] " Richard Cochran 2021-08-19 15:40 ` Machnikowski, Maciej 2021-08-19 15:40 ` [Intel-wired-lan] " Machnikowski, Maciej 2021-08-20 15:55 ` Richard Cochran 2021-08-20 15:55 ` [Intel-wired-lan] " Richard Cochran 2021-08-20 18:30 ` Machnikowski, Maciej 2021-08-20 18:30 ` [Intel-wired-lan] " Machnikowski, Maciej 2021-08-22 1:50 ` Richard Cochran 2021-08-22 1:50 ` [Intel-wired-lan] " Richard Cochran 2021-08-22 2:30 ` Richard Cochran 2021-08-22 2:30 ` [Intel-wired-lan] " Richard Cochran 2021-08-23 8:29 ` Machnikowski, Maciej 2021-08-23 8:29 ` [Intel-wired-lan] " Machnikowski, Maciej 2021-08-30 21:06 ` Richard Cochran 2021-08-30 21:06 ` [Intel-wired-lan] " Richard Cochran 2021-08-31 9:29 ` Machnikowski, Maciej 2021-08-31 9:29 ` [Intel-wired-lan] " Machnikowski, Maciej 2021-08-16 16:07 ` [RFC net-next 2/7] selftests/ptp: Add usage of PTP_DPLL_GETSTATE ioctl in testptp Arkadiusz Kubalewski 2021-08-16 16:07 ` [Intel-wired-lan] " Arkadiusz Kubalewski 2021-08-16 23:54 ` Richard Cochran 2021-08-16 23:54 ` [Intel-wired-lan] " Richard Cochran 2021-08-16 16:07 ` [RFC net-next 3/7] ice: add get_dpll_state ptp interface usage Arkadiusz Kubalewski 2021-08-16 16:07 ` [Intel-wired-lan] " Arkadiusz Kubalewski 2021-08-16 16:07 ` [RFC net-next 4/7] net: add ioctl interface for recover reference clock on netdev Arkadiusz Kubalewski 2021-08-16 16:07 ` [Intel-wired-lan] " Arkadiusz Kubalewski 2021-08-16 19:46 ` Arnd Bergmann 2021-08-16 19:46 ` [Intel-wired-lan] " Arnd Bergmann 2021-08-17 10:35 ` Kubalewski, Arkadiusz 2021-08-17 10:35 ` [Intel-wired-lan] " Kubalewski, Arkadiusz 2021-08-22 1:25 ` Richard Cochran 2021-08-22 1:25 ` [Intel-wired-lan] " Richard Cochran 2021-08-16 16:07 ` [RFC net-next 5/7] selftests/net: Add test app for SIOC{S|G}SYNCE Arkadiusz Kubalewski 2021-08-16 16:07 ` [Intel-wired-lan] " Arkadiusz Kubalewski 2021-08-18 11:49 ` kernel test robot 2021-08-16 16:07 ` [RFC net-next 6/7] ice: add SIOC{S|G}SYNCE interface usage to recover reference signal Arkadiusz Kubalewski 2021-08-16 16:07 ` [Intel-wired-lan] " Arkadiusz Kubalewski 2021-08-16 16:07 ` [RFC net-next 7/7] ice: add sysfs interface to configure PHY recovered " Arkadiusz Kubalewski 2021-08-16 16:07 ` [Intel-wired-lan] " Arkadiusz Kubalewski 2021-08-18 17:05 ` Richard Cochran [this message] 2021-08-18 17:05 ` [Intel-wired-lan] [RFC net-next 0/7] Add basic SyncE interfaces Richard Cochran 2021-08-18 17:08 ` Richard Cochran 2021-08-18 17:08 ` [Intel-wired-lan] " Richard Cochran
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=20210818170536.GE9992@hoboy.vegasvil.org \ --to=richardcochran@gmail.com \ --cc=anthony.l.nguyen@intel.com \ --cc=arkadiusz.kubalewski@intel.com \ --cc=arnd@arndb.de \ --cc=colin.king@canonical.com \ --cc=cong.wang@bytedance.com \ --cc=davem@davemloft.net \ --cc=gustavoars@kernel.org \ --cc=intel-wired-lan@lists.osuosl.org \ --cc=jesse.brandeburg@intel.com \ --cc=kuba@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-kselftest@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=nikolay@nvidia.com \ --cc=shuah@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: linkBe 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.