Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 v5 iwl-next 0/6] ice: fix timestamping in reset process
Date: Mon,  8 Jan 2024 13:47:11 +0100	[thread overview]
Message-ID: <20240108124717.1845481-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 (5):
  ice: pass reset type to PTP reset functions
  ice: rename verify_cached to has_ready_bitmap
  ice: rename ice_ptp_tx_cfg_intr
  ice: factor out ice_ptp_rebuild_owner()
  ice: stop destroying and reinitalizing Tx tracker during reset

Karol Kolacinski (1):
  ice: introduce PTP state machine

V4 -> V5: rebased the series
V2 -> V3: rebased the series and fixed Tx timestamps missing
V1 -> V2: rebased the series and dropped already merged patches

 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    |   4 +-
 drivers/net/ethernet/intel/ice/ice_ptp.c     | 231 +++++++++++--------
 drivers/net/ethernet/intel/ice/ice_ptp.h     |  34 ++-
 5 files changed, 166 insertions(+), 106 deletions(-)


base-commit: 006c8fe67ee86e7810f2aa3b365ab6de65cf2299
-- 
2.40.1


             reply	other threads:[~2024-01-08 12:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 12:47 Karol Kolacinski [this message]
2024-01-08 12:47 ` [Intel-wired-lan] [PATCH v5 iwl-next 1/6] ice: introduce PTP state machine Karol Kolacinski
2024-01-12 17:32   ` Pucha, HimasekharX Reddy
2024-01-15 10:32   ` Simon Horman
2024-01-17 22:07     ` Keller, Jacob E
2024-01-19 16:55       ` Simon Horman
2024-01-08 12:47 ` [Intel-wired-lan] [PATCH v5 iwl-next 2/6] ice: pass reset type to PTP reset functions Karol Kolacinski
2024-01-12 17:33   ` Pucha, HimasekharX Reddy
2024-01-08 12:47 ` [Intel-wired-lan] [PATCH v5 iwl-next 3/6] ice: rename verify_cached to has_ready_bitmap Karol Kolacinski
2024-01-12 17:33   ` Pucha, HimasekharX Reddy
2024-01-15 10:36   ` Simon Horman
2024-01-17 22:10     ` Keller, Jacob E
2024-01-08 12:47 ` [Intel-wired-lan] [PATCH v5 iwl-next 4/6] ice: rename ice_ptp_tx_cfg_intr Karol Kolacinski
2024-01-12 17:33   ` Pucha, HimasekharX Reddy
2024-01-08 12:47 ` [Intel-wired-lan] [PATCH v5 iwl-next 5/6] ice: factor out ice_ptp_rebuild_owner() Karol Kolacinski
2024-01-12 17:33   ` Pucha, HimasekharX Reddy
2024-01-15 10:39   ` Simon Horman
2024-01-18 17:36     ` Kolacinski, Karol
2024-01-08 12:47 ` [Intel-wired-lan] [PATCH v5 iwl-next 6/6] ice: stop destroying and reinitalizing Tx tracker during reset Karol Kolacinski
2024-01-12 17:32   ` Pucha, HimasekharX Reddy

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=20240108124717.1845481-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