From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3] i40e: add support for PTP external synchronization clock
Date: Fri, 31 Jul 2020 21:31:19 +0000 [thread overview]
Message-ID: <BN6PR1101MB2145F88FBECBE0EDBBE065878C4E0@BN6PR1101MB2145.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200728134748.26703-1-piotr.kwapulinski@intel.com>
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
> Piotr Kwapulinski
> Sent: Tuesday, July 28, 2020 6:48 AM
> To: intel-wired-lan at lists.osuosl.org
> Cc: Kwapulinski, Piotr <piotr.kwapulinski@intel.com>
> Subject: [Intel-wired-lan] [PATCH v3] i40e: add support for PTP external
> synchronization clock
>
> Add support for external synchronization clock via GPIOs.
> 1PPS signals are handled via the dedicated 3 GPIOs: SDP3_2,
> SDP3_3 and GPIO_4.
> Previously it was not possible to use the external PTP synchronization clock.
>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
> Reviewed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
> Signed-off-by: Piotr Kwapulinski <piotr.kwapulinski@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e.h | 76 +-
> drivers/net/ethernet/intel/i40e/i40e_main.c | 18 +-
> drivers/net/ethernet/intel/i40e/i40e_ptp.c | 747 +++++++++++++++++-
> .../net/ethernet/intel/i40e/i40e_register.h | 31 +-
> 4 files changed, 845 insertions(+), 27 deletions(-)
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
next prev parent reply other threads:[~2020-07-31 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 13:47 [Intel-wired-lan] [PATCH v3] i40e: add support for PTP external synchronization clock Piotr Kwapulinski
2020-07-31 21:31 ` Bowers, AndrewX [this message]
2020-10-23 10:38 ` [Intel-wired-lan] [PATCH v5] " Piotr Kwapulinski
2020-10-23 10:42 ` Maciej Fijalkowski
2020-10-23 11:15 ` [Intel-wired-lan] [PATCH v6] " Piotr Kwapulinski
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=BN6PR1101MB2145F88FBECBE0EDBBE065878C4E0@BN6PR1101MB2145.namprd11.prod.outlook.com \
--to=andrewx.bowers@intel.com \
--cc=intel-wired-lan@osuosl.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.