Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dvora Fuxbrumer <dvorax.fuxbrumer@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH next-queue v2 1/2] igc: Enable internal i225 PPS
Date: Sun, 11 Apr 2021 10:15:44 +0300	[thread overview]
Message-ID: <771f5092-3762-4312-0760-c9e709c96ee7@linux.intel.com> (raw)
In-Reply-To: <20210219013104.54436-2-ederson.desouza@intel.com>

On 19/02/2021 03:31, Ederson de Souza wrote:
> The i225 device can produce one interrupt on the full second, much
> like i210 - from where this patch is inspired.
> 
> This patch sets up the full second interruption on the i225 and when
> receiving it, it sends a PPS event to PTP (Precision Time Protocol)
> kernel subsystem.
> 
> The PTP subsystem exposes the PPS events via ioctl and sysfs, and one
> can use the `testptp` tool (tools/testing/selftests/ptp) to check that
> the events are being generated.
> 
> Signed-off-by: Ederson de Souza <ederson.desouza@intel.com>
> ---
>   drivers/net/ethernet/intel/igc/igc.h      |  2 ++
>   drivers/net/ethernet/intel/igc/igc_main.c |  8 +++++++
>   drivers/net/ethernet/intel/igc/igc_ptp.c  | 28 ++++++++++++++++++++++-
>   3 files changed, 37 insertions(+), 1 deletion(-)
> 
Tested-by: Dvora Fuxbrumer <dvorax.fuxbrumer@linux.intel.com>

  reply	other threads:[~2021-04-11  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19  1:31 [Intel-wired-lan] [PATCH next-queue v2 0/2] PPS and SDP support for i225 Ederson de Souza
2021-02-19  1:31 ` [Intel-wired-lan] [PATCH next-queue v2 1/2] igc: Enable internal i225 PPS Ederson de Souza
2021-04-11  7:15   ` Dvora Fuxbrumer [this message]
2021-02-19  1:31 ` [Intel-wired-lan] [PATCH next-queue v2 2/2] igc: enable auxiliary PHC functions for the i225 Ederson de Souza
2021-04-11  7:16   ` Dvora Fuxbrumer

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=771f5092-3762-4312-0760-c9e709c96ee7@linux.intel.com \
    --to=dvorax.fuxbrumer@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox