From: Jacob Keller <jacob.e.keller@intel.com>
To: Karol Kolacinski <karol.kolacinski@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, <anthony.l.nguyen@intel.com>,
<przemyslaw.kitszel@intel.com>
Subject: Re: [PATCH v3 iwl-next 4/4] ice: combine cross timestamp functions for E82x and E830
Date: Thu, 25 Jul 2024 09:31:31 -0700 [thread overview]
Message-ID: <b60a8fef-3262-4921-a8ba-360465eb8832@intel.com> (raw)
In-Reply-To: <20240725093932.54856-10-karol.kolacinski@intel.com>
On 7/25/2024 2:34 AM, Karol Kolacinski wrote:
> From: Jacob Keller <jacob.e.keller@intel.com>
>
> The E830 and E82x devices use essentially the same logic for performing
> a crosstimestamp. The only difference is that E830 hardware has
> different offsets. Instead of having two implementations, combine them
> into a single ice_capture_crosststamp() function.
>
> Also combine the wrapper functions which call
> get_device_system_crosststamp() into a single ice_ptp_getcrosststamp()
> function.
>
The commit message could probably be updated since I think this is
referring to E830 code which is only in our internal branch. I guess you
must have squashed this together with the original E830 implementation
rather than sending that up and then this refactor/cleanup?
Not a huge deal, but it is somewhat confusing when reading the actual
patch code.
Thanks,
Jake
next prev parent reply other threads:[~2024-07-25 16:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 9:34 [PATCH v3 iwl-next 0/4] ice: Implement PTP support for E830 devices Karol Kolacinski
2024-07-25 9:34 ` [PATCH v3 iwl-next 1/4] " Karol Kolacinski
2024-07-26 13:17 ` [Intel-wired-lan] " Alexander Lobakin
2024-07-25 9:34 ` [PATCH v3 iwl-next 2/4] ice: Process TSYN IRQ in a separate function Karol Kolacinski
2024-07-26 13:22 ` [Intel-wired-lan] " Alexander Lobakin
2024-07-25 9:34 ` [PATCH v3 iwl-next 3/4] ice: Add timestamp ready bitmap for E830 products Karol Kolacinski
2024-07-26 13:25 ` [Intel-wired-lan] " Alexander Lobakin
2024-07-25 9:34 ` [PATCH v3 iwl-next 4/4] ice: combine cross timestamp functions for E82x and E830 Karol Kolacinski
2024-07-25 16:31 ` Jacob Keller [this message]
2024-07-26 13:37 ` [Intel-wired-lan] " Alexander Lobakin
2024-07-26 23:16 ` Jacob Keller
2024-08-05 16:21 ` Kolacinski, Karol
2024-08-07 13:54 ` Alexander Lobakin
2024-08-07 14:26 ` Kolacinski, Karol
2024-08-08 13:00 ` Alexander Lobakin
2024-08-08 14:20 ` Jakub Kicinski
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=b60a8fef-3262-4921-a8ba-360465eb8832@intel.com \
--to=jacob.e.keller@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=karol.kolacinski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).