From: Karol Kolacinski <karol.kolacinski@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org,
Karol Kolacinski <karol.kolacinski@intel.com>,
anthony.l.nguyen@intel.com, jesse.brandeburg@intel.com
Subject: [Intel-wired-lan] [PATCH v3 iwl-next 0/9] ice: fix timestamping in reset process
Date: Tue, 22 Aug 2023 14:40:35 +0200 [thread overview]
Message-ID: <20230822124044.301654-1-karol.kolacinski@intel.com> (raw)
PTP reset process has multiple places where timestamping can end up in
an incorrect state.
This series introduces a proper state machine for PTP and refactors
a large part of the code to ensure that timestamping does not break.
Jacob Keller (8):
ice: use ice_pf_src_tmr_owned where available
ice: pass reset type to PTP reset functions
ice: rename PTP functions and fields
ice: factor out ice_ptp_rebuild_owner()
ice: remove ptp_tx ring parameter flag
ice: modify tstamp_config only during TS mode set
ice: restore timestamp configuration after reset
ice: stop destroying and reinitalizing Tx tracker during reset
Karol Kolacinski (1):
ice: introduce PTP state machine
---
V2 -> V3: Adjusted commit authors and added base commit
V1 -> V2: Adjusted commit S-o-bs and messages
drivers/net/ethernet/intel/ice/ice.h | 1 -
drivers/net/ethernet/intel/ice/ice_ethtool.c | 2 +-
drivers/net/ethernet/intel/ice/ice_main.c | 16 +-
drivers/net/ethernet/intel/ice/ice_ptp.c | 331 ++++++++++++-------
drivers/net/ethernet/intel/ice/ice_ptp.h | 36 +-
drivers/net/ethernet/intel/ice/ice_txrx.c | 3 -
drivers/net/ethernet/intel/ice/ice_txrx.h | 1 -
7 files changed, 247 insertions(+), 143 deletions(-)
base-commit: c924ca3252117385328b3aa1b2b507b5c93c4c47
--
2.39.2
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2023-08-22 12:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 12:40 Karol Kolacinski [this message]
2023-08-22 12:40 ` [Intel-wired-lan] [PATCH v3 iwl-next 1/9] ice: use ice_pf_src_tmr_owned where available Karol Kolacinski
2023-08-22 12:40 ` [Intel-wired-lan] [PATCH v3 iwl-next 2/9] ice: introduce PTP state machine Karol Kolacinski
2023-08-22 12:40 ` [Intel-wired-lan] [PATCH v3 iwl-next 3/9] ice: pass reset type to PTP reset functions Karol Kolacinski
2023-08-22 12:40 ` [Intel-wired-lan] [PATCH v3 iwl-next 4/9] ice: rename PTP functions and fields Karol Kolacinski
2023-08-23 20:45 ` Jacob Keller
2023-08-23 20:56 ` Jacob Keller
2023-08-23 20:57 ` Jacob Keller
2023-08-22 12:40 ` [Intel-wired-lan] [PATCH v3 iwl-next 5/9] ice: factor out ice_ptp_rebuild_owner() Karol Kolacinski
2023-08-22 12:40 ` [Intel-wired-lan] [PATCH v3 iwl-next 6/9] ice: remove ptp_tx ring parameter flag Karol Kolacinski
2023-08-22 12:40 ` [Intel-wired-lan] [PATCH v3 iwl-next 7/9] ice: modify tstamp_config only during TS mode set Karol Kolacinski
2023-08-22 12:40 ` [Intel-wired-lan] [PATCH v3 iwl-next 8/9] ice: restore timestamp configuration after reset Karol Kolacinski
2023-08-22 12:40 ` [Intel-wired-lan] [PATCH v3 iwl-next 9/9] ice: stop destroying and reinitalizing Tx tracker during reset Karol Kolacinski
2023-08-23 20:53 ` Tony Nguyen
2023-08-29 10:35 ` Kolacinski, Karol
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=20230822124044.301654-1-karol.kolacinski@intel.com \
--to=karol.kolacinski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.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