All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Machnikowski, Maciej" <maciej.machnikowski@intel.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"nikolay@nvidia.com" <nikolay@nvidia.com>,
	"cong.wang@bytedance.com" <cong.wang@bytedance.com>,
	"colin.king@canonical.com" <colin.king@canonical.com>,
	"gustavoars@kernel.org" <gustavoars@kernel.org>,
	"Bross, Kevin" <kevin.bross@intel.com>,
	"Stanton, Kevin B" <kevin.b.stanton@intel.com>,
	Ahmad Byagowi <abyagowi@fb.com>
Subject: RE: [RFC net-next 1/7] ptp: Add interface for acquiring DPLL state
Date: Mon, 23 Aug 2021 08:29:14 +0000	[thread overview]
Message-ID: <PH0PR11MB4951C8C972C5123E7FC5DAFEEAC49@PH0PR11MB4951.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210822023057.GA6481@hoboy.vegasvil.org>



> -----Original Message-----
> From: Richard Cochran <richardcochran@gmail.com>
> Sent: Sunday, August 22, 2021 4:31 AM
> Subject: Re: [RFC net-next 1/7] ptp: Add interface for acquiring DPLL state
> 
> On Fri, Aug 20, 2021 at 06:30:02PM +0000, Machnikowski, Maciej wrote:
> 
> > Since the 40.5.2 is not applicable to higher-speed ethernet which
> > don't use auto-negotiation, but rather the link training sequence
> > where the RX side always syncs its clock to the TX side.
> 
> By "the RX side always syncs its clock to the TX side" do you mean the RX
> channel synchronizes to the link partner's TX channel?
> 
> Wow, that brings back the 100 megabit scheme I guess.  That's cool, because
> the same basic idea applies to the PHYTER then.
> 

Yes! Sounds very similar! :)

> Still we are doing to need a way for user space to query the HW topology to
> discover whether a given ports may be syntonized from a second port.  I
> don't think your pin selection thing works unless user space can tell what the
> pins are connected to.
> 
> Thanks,
> Richard

And a good catch! I'll update the RFC to add the query functionality and move the SyncE logic/pins to the netdev subsystem.

Thanks 

WARNING: multiple messages have this Message-ID (diff)
From: Machnikowski, Maciej <maciej.machnikowski@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC net-next 1/7] ptp: Add interface for acquiring DPLL state
Date: Mon, 23 Aug 2021 08:29:14 +0000	[thread overview]
Message-ID: <PH0PR11MB4951C8C972C5123E7FC5DAFEEAC49@PH0PR11MB4951.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210822023057.GA6481@hoboy.vegasvil.org>



> -----Original Message-----
> From: Richard Cochran <richardcochran@gmail.com>
> Sent: Sunday, August 22, 2021 4:31 AM
> Subject: Re: [RFC net-next 1/7] ptp: Add interface for acquiring DPLL state
> 
> On Fri, Aug 20, 2021 at 06:30:02PM +0000, Machnikowski, Maciej wrote:
> 
> > Since the 40.5.2 is not applicable to higher-speed ethernet which
> > don't use auto-negotiation, but rather the link training sequence
> > where the RX side always syncs its clock to the TX side.
> 
> By "the RX side always syncs its clock to the TX side" do you mean the RX
> channel synchronizes to the link partner's TX channel?
> 
> Wow, that brings back the 100 megabit scheme I guess.  That's cool, because
> the same basic idea applies to the PHYTER then.
> 

Yes! Sounds very similar! :)

> Still we are doing to need a way for user space to query the HW topology to
> discover whether a given ports may be syntonized from a second port.  I
> don't think your pin selection thing works unless user space can tell what the
> pins are connected to.
> 
> Thanks,
> Richard

And a good catch! I'll update the RFC to add the query functionality and move the SyncE logic/pins to the netdev subsystem.

Thanks 

  reply	other threads:[~2021-08-23  8:29 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 [this message]
2021-08-23  8:29                       ` 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 ` [RFC net-next 0/7] Add basic SyncE interfaces Richard Cochran
2021-08-18 17:05   ` [Intel-wired-lan] " 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=PH0PR11MB4951C8C972C5123E7FC5DAFEEAC49@PH0PR11MB4951.namprd11.prod.outlook.com \
    --to=maciej.machnikowski@intel.com \
    --cc=abyagowi@fb.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=kevin.b.stanton@intel.com \
    --cc=kevin.bross@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=richardcochran@gmail.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: 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.