From: Miroslav Lichvar <mlichvar@redhat.com>
To: chrony-users@chrony.tuxfamily.org
Cc: "intel-wired-lan@lists.osuosl.org" <intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] 5.10 -> 6.1 i211 second PPS pin on SDP-3 gone
Date: Tue, 31 Jan 2023 15:40:13 +0100 [thread overview]
Message-ID: <Y9koTVr+6rY/O2sc@localhost> (raw)
In-Reply-To: <4fc70178-dea4-4b88-dc32-8774f977af27@bluematt.me>
On Mon, Jan 30, 2023 at 11:24:19PM -0800, Matt Corallo wrote:
> I have a device with two separate PPS time sources wired up to two of the
> Software Defined Pins on an Intel i211 NIC (ala
> https://blog.dan.drown.org/apu2-ntp-server-2/). This works great with chrony
> 4.0 (and even better in 4.3, thanks!) on Linux 5.10.
>
> However, I just tried to upgrade to 6.1 and the second PPS went silent. The
> testptp utility in the kernel tree shows the first pin working fine, but
> when I hook the fourth pin up to channel two (as chrony does as well), I get
> radio silence.
I suspect it was broken in commit cf99c1dd7b77 ("igb: move PEROUT
and EXTTS isr logic to separate functions"), which seems to confused
the number of timestamping channels with number of pins.
Can you please try it with this change?
--- a/drivers/net/ethernet/intel/igb/igb_main.c
+++ b/drivers/net/ethernet/intel/igb/igb_main.c
@@ -6874,7 +6874,7 @@ static void igb_extts(struct igb_adapter *adapter, int tsintr_tt)
struct ptp_clock_event event;
struct timespec64 ts;
- if (pin < 0 || pin >= IGB_N_EXTTS)
+ if (pin < 0 || pin >= IGB_N_SDP)
return;
if (hw->mac.type == e1000_82580 ||
If that works, I'll submit it as a proper patch.
--
Miroslav Lichvar
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-01-31 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 7:24 [Intel-wired-lan] 5.10 -> 6.1 i211 second PPS pin on SDP-3 gone Matt Corallo
2023-01-31 14:40 ` Miroslav Lichvar [this message]
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=Y9koTVr+6rY/O2sc@localhost \
--to=mlichvar@redhat.com \
--cc=chrony-users@chrony.tuxfamily.org \
--cc=intel-wired-lan@lists.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