From: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>
To: "Machnikowski, Maciej" <maciej.machnikowski@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
Vadim Fedorenko <vfedorenko@novek.ru>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"Byagowi, Ahmad" <abyagowi@fb.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"idosch@idosch.org" <idosch@idosch.org>,
"mkubecek@suse.cz" <mkubecek@suse.cz>,
"saeed@kernel.org" <saeed@kernel.org>,
"michael.chan@broadcom.com" <michael.chan@broadcom.com>,
"petrm@nvidia.com" <petrm@nvidia.com>
Subject: RE: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks
Date: Wed, 15 Dec 2021 12:14:39 +0000 [thread overview]
Message-ID: <DM6PR11MB4657CE134223B65B5F2EF5F29B769@DM6PR11MB4657.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW5PR11MB58126A8F6466A8EAD1293D5EEA749@MW5PR11MB5812.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Machnikowski, Maciej <maciej.machnikowski@intel.com>
> Sent: poniedziałek, 13 grudnia 2021 09:54
> To: Jakub Kicinski <kuba@kernel.org>
> Cc: netdev@vger.kernel.org; intel-wired-lan@lists.osuosl.org; Kubalewski, Arkadiusz <arkadiusz.kubalewski@intel.com>; richardcochran@gmail.com; Byagowi, Ahmad <abyagowi@fb.com>; Nguyen, Anthony L <anthony.l.nguyen@intel.com>; davem@davemloft.net; linux-kselftest@vger.kernel.org; idosch@idosch.org; mkubecek@suse.cz; saeed@kernel.org; michael.chan@broadcom.com; petrm@nvidia.com; Vadim Fedorenko <vfedorenko@novek.ru>
> Subject: RE: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks
>
> > -----Original Message-----
> > From: Jakub Kicinski <kuba@kernel.org>
> > Sent: Friday, December 10, 2021 5:17 PM
> > To: Machnikowski, Maciej <maciej.machnikowski@intel.com>
> > Cc: netdev@vger.kernel.org; intel-wired-lan@lists.osuosl.org;
> > Kubalewski, Arkadiusz <arkadiusz.kubalewski@intel.com>;
> > richardcochran@gmail.com; Byagowi, Ahmad <abyagowi@fb.com>; Nguyen,
> > Anthony L <anthony.l.nguyen@intel.com>; davem@davemloft.net; linux-
> > kselftest@vger.kernel.org; idosch@idosch.org; mkubecek@suse.cz;
> > saeed@kernel.org; michael.chan@broadcom.com; petrm@nvidia.com; Vadim
> > Fedorenko <vfedorenko@novek.ru>
> > Subject: Re: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks
> >
> > On Fri, 10 Dec 2021 14:45:46 +0100 Maciej Machnikowski wrote:
> > > Synchronous Ethernet networks use a physical layer clock to
> > > syntonize the frequency across different network elements.
> > >
> > > Basic SyncE node defined in the ITU-T G.8264 consist of an Ethernet
> > > Equipment Clock (EEC) and have the ability to synchronize to
> > > reference frequency sources.
> > >
> > > This patch series is a prerequisite for EEC object and adds ability
> > > to enable recovered clocks in the physical layer of the netdev object.
> > > Recovered clocks can be used as one of the reference signal by the EEC.
> > >
> > > Further work is required to add the DPLL subsystem, link it to the
> > > netdev object and create API to read the EEC DPLL state.
> >
> > You missed CCing Vadim. I guess Ccing the right people may be right up
> > there with naming things as the hardest things in SW development..
> >
> > Anyway, Vadim - do you have an ETA on the first chunk of the PLL work?
>
> Sounds about right :) thanks for adding Vadim!
>
Good day Vadim,
Can we help on the new PLL interfaces?
I can start some works related to that, although would need a guidance
from the expert.
Where to place it?
What in-kernel interfaces to use?
Any other high level tips that could be useful?
Or if you already started some work, could you please share some
information?
WARNING: multiple messages have this Message-ID (diff)
From: Kubalewski, Arkadiusz <arkadiusz.kubalewski@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v5 net-next 0/4] Add ethtool interface for RClocks
Date: Wed, 15 Dec 2021 12:14:39 +0000 [thread overview]
Message-ID: <DM6PR11MB4657CE134223B65B5F2EF5F29B769@DM6PR11MB4657.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW5PR11MB58126A8F6466A8EAD1293D5EEA749@MW5PR11MB5812.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Machnikowski, Maciej <maciej.machnikowski@intel.com>
> Sent: poniedzia?ek, 13 grudnia 2021 09:54
> To: Jakub Kicinski <kuba@kernel.org>
> Cc: netdev at vger.kernel.org; intel-wired-lan at lists.osuosl.org; Kubalewski, Arkadiusz <arkadiusz.kubalewski@intel.com>; richardcochran at gmail.com; Byagowi, Ahmad <abyagowi@fb.com>; Nguyen, Anthony L <anthony.l.nguyen@intel.com>; davem at davemloft.net; linux-kselftest at vger.kernel.org; idosch at idosch.org; mkubecek at suse.cz; saeed at kernel.org; michael.chan at broadcom.com; petrm at nvidia.com; Vadim Fedorenko <vfedorenko@novek.ru>
> Subject: RE: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks
>
> > -----Original Message-----
> > From: Jakub Kicinski <kuba@kernel.org>
> > Sent: Friday, December 10, 2021 5:17 PM
> > To: Machnikowski, Maciej <maciej.machnikowski@intel.com>
> > Cc: netdev at vger.kernel.org; intel-wired-lan at lists.osuosl.org;
> > Kubalewski, Arkadiusz <arkadiusz.kubalewski@intel.com>;
> > richardcochran at gmail.com; Byagowi, Ahmad <abyagowi@fb.com>; Nguyen,
> > Anthony L <anthony.l.nguyen@intel.com>; davem at davemloft.net; linux-
> > kselftest at vger.kernel.org; idosch at idosch.org; mkubecek at suse.cz;
> > saeed at kernel.org; michael.chan at broadcom.com; petrm at nvidia.com; Vadim
> > Fedorenko <vfedorenko@novek.ru>
> > Subject: Re: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks
> >
> > On Fri, 10 Dec 2021 14:45:46 +0100 Maciej Machnikowski wrote:
> > > Synchronous Ethernet networks use a physical layer clock to
> > > syntonize the frequency across different network elements.
> > >
> > > Basic SyncE node defined in the ITU-T G.8264 consist of an Ethernet
> > > Equipment Clock (EEC) and have the ability to synchronize to
> > > reference frequency sources.
> > >
> > > This patch series is a prerequisite for EEC object and adds ability
> > > to enable recovered clocks in the physical layer of the netdev object.
> > > Recovered clocks can be used as one of the reference signal by the EEC.
> > >
> > > Further work is required to add the DPLL subsystem, link it to the
> > > netdev object and create API to read the EEC DPLL state.
> >
> > You missed CCing Vadim. I guess Ccing the right people may be right up
> > there with naming things as the hardest things in SW development..
> >
> > Anyway, Vadim - do you have an ETA on the first chunk of the PLL work?
>
> Sounds about right :) thanks for adding Vadim!
>
Good day Vadim,
Can we help on the new PLL interfaces?
I can start some works related to that, although would need a guidance
from the expert.
Where to place it?
What in-kernel interfaces to use?
Any other high level tips that could be useful?
Or if you already started some work, could you please share some
information?
next prev parent reply other threads:[~2021-12-15 12:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 13:45 [PATCH v5 net-next 0/4] Add ethtool interface for RClocks Maciej Machnikowski
2021-12-10 13:45 ` [Intel-wired-lan] " Maciej Machnikowski
2021-12-10 13:45 ` [PATCH v5 net-next 1/4] ice: add support detecting features based on netlist Maciej Machnikowski
2021-12-10 13:45 ` [Intel-wired-lan] " Maciej Machnikowski
2021-12-10 13:45 ` [PATCH v5 net-next 2/4] ethtool: Add ability to configure recovered clock for SyncE feature Maciej Machnikowski
2021-12-10 13:45 ` [Intel-wired-lan] " Maciej Machnikowski
2021-12-10 13:45 ` [PATCH v5 net-next 3/4] ice: add support for monitoring SyncE DPLL state Maciej Machnikowski
2021-12-10 13:45 ` [Intel-wired-lan] " Maciej Machnikowski
2021-12-10 13:45 ` [PATCH v5 net-next 4/4] ice: add support for recovered clocks Maciej Machnikowski
2021-12-10 13:45 ` [Intel-wired-lan] " Maciej Machnikowski
2021-12-10 16:16 ` [PATCH v5 net-next 0/4] Add ethtool interface for RClocks Jakub Kicinski
2021-12-10 16:16 ` [Intel-wired-lan] " Jakub Kicinski
2021-12-13 8:53 ` Machnikowski, Maciej
2021-12-13 8:53 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-12-15 12:14 ` Kubalewski, Arkadiusz [this message]
2021-12-15 12:14 ` Kubalewski, Arkadiusz
2021-12-15 22:27 ` Vadim Fedorenko
2021-12-15 22:27 ` [Intel-wired-lan] " Vadim Fedorenko
2021-12-17 0:01 ` Kubalewski, Arkadiusz
2021-12-17 0:01 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2022-01-19 22:33 ` Kubalewski, Arkadiusz
2022-01-19 22:33 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2021-12-12 11:47 ` Ido Schimmel
2021-12-12 11:47 ` [Intel-wired-lan] " Ido Schimmel
2021-12-15 12:13 ` Machnikowski, Maciej
2021-12-15 12:13 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-12-20 13:50 ` Ido Schimmel
2021-12-20 13:50 ` [Intel-wired-lan] " Ido Schimmel
2021-12-21 22:12 ` Machnikowski, Maciej
2021-12-21 22:12 ` [Intel-wired-lan] " Machnikowski, Maciej
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=DM6PR11MB4657CE134223B65B5F2EF5F29B769@DM6PR11MB4657.namprd11.prod.outlook.com \
--to=arkadiusz.kubalewski@intel.com \
--cc=abyagowi@fb.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.machnikowski@intel.com \
--cc=michael.chan@broadcom.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=richardcochran@gmail.com \
--cc=saeed@kernel.org \
--cc=vfedorenko@novek.ru \
/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.