From: Richard Cochran <richardcochran@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v2 0/4] igb: support PEROUT and EXTTS PTP pin functions on 82580/i354/i350
Date: Thu, 23 Dec 2021 12:03:20 -0800 [thread overview]
Message-ID: <20211223200320.GA29492@hoboy.vegasvil.org> (raw)
In-Reply-To: <20211028143459.903439-1-kernel.hbk@gmail.com>
On Thu, Oct 28, 2021 at 04:34:55PM +0200, Ruud Bos wrote:
> The added EXTTS function has not been tested. However, looking at the data
> sheets, the layout of the registers involved match the i210 exactly except
> for the time registers mentioned before. Hence the almost identical
> implementation.
>
> v2:
> - fix PEROUT on SDP2/SDP3
> - rename incorrectly named sdp function argument to tsintr_tt
> - fix white space issue
>
> Ruud Bos (4):
> igb: move SDP config initialization to separate function
> igb: move PEROUT and EXTTS isr logic to separate functions
> igb: support PEROUT on 82580/i354/i350
> igb: support EXTTS on 82580/i354/i350
For the series:
Acked-by: Richard Cochran <richardcochran@gmail.com>
prev parent reply other threads:[~2021-12-23 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 14:34 [Intel-wired-lan] [PATCH net-next v2 0/4] igb: support PEROUT and EXTTS PTP pin functions on 82580/i354/i350 Ruud Bos
2021-10-28 14:34 ` [Intel-wired-lan] [PATCH net-next v2 1/4] igb: move SDP config initialization to separate function Ruud Bos
2021-12-22 4:20 ` G, GurucharanX
2021-10-28 14:34 ` [Intel-wired-lan] [PATCH net-next v2 2/4] igb: move PEROUT and EXTTS isr logic to separate functions Ruud Bos
2021-12-22 4:19 ` G, GurucharanX
2021-10-28 14:34 ` [Intel-wired-lan] [PATCH net-next v2 3/4] igb: support PEROUT on 82580/i354/i350 Ruud Bos
2021-12-22 4:18 ` G, GurucharanX
2021-10-28 14:34 ` [Intel-wired-lan] [PATCH net-next v2 4/4] igb: support EXTTS " Ruud Bos
2021-12-22 4:17 ` G, GurucharanX
2021-12-23 20:03 ` Richard Cochran [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=20211223200320.GA29492@hoboy.vegasvil.org \
--to=richardcochran@gmail.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