From: Soumyadeep Hore <soumyadeep.hore@intel.com>
To: bruce.richardson@intel.com, manoj.kumar.subbarao@intel.com,
aman.deep.singh@intel.com, dev@dpdk.org
Cc: Grzegorz Nitka <grzegorz.nitka@intel.com>, stable@dpdk.org
Subject: [PATCH v1 6/6] net/ice/base: fix 'adjust' timer programming for E830
Date: Tue, 10 Mar 2026 05:52:18 -0400 [thread overview]
Message-ID: <20260310095218.703423-16-soumyadeep.hore@intel.com> (raw)
In-Reply-To: <20260310095218.703423-1-soumyadeep.hore@intel.com>
From: Grzegorz Nitka <grzegorz.nitka@intel.com>
Fix incorrect 'adjust the timer' programming sequence for E830 devices
series. Only shadow registers GLTSYN_SHADJ were programmed in the current
implementation. According to the specification [1], write to command
GLTSYN_CMD register is also required with CMD field set to "Adjust the
Time" value, for the timer adjustment to take the effect.
The flow was broken for the adjustment less than S32_MAX/MIN range
(around +/- 2 seconds). For bigger adjustment, non-atomic programming
flow is used, involving set timer programming. Non-atomic flow is
implemented correctly.
Fixes: 881169950d80 ("net/ice/base: implement initial PTP support for E830")
Cc: stable@dpdk.org
Signed-off-by: Soumyadeep Hore <soumyadeep.hore@intel.com>
Signed-off-by: Grzegorz Nitka <grzegorz.nitka@intel.com>
---
drivers/net/intel/ice/base/ice_ptp_hw.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/intel/ice/base/ice_ptp_hw.c b/drivers/net/intel/ice/base/ice_ptp_hw.c
index 7d16965674..5688f969ce 100644
--- a/drivers/net/intel/ice/base/ice_ptp_hw.c
+++ b/drivers/net/intel/ice/base/ice_ptp_hw.c
@@ -6083,7 +6083,7 @@ int ice_ptp_write_incval_locked(struct ice_hw *hw, u64 incval,
*/
int ice_ptp_adj_clock(struct ice_hw *hw, s32 adj, bool lock_sbq)
{
- int err;
+ int err = 0;
u8 tmr_idx;
tmr_idx = hw->func_caps.ts_func_info.tmr_index_owned;
@@ -6101,8 +6101,8 @@ int ice_ptp_adj_clock(struct ice_hw *hw, s32 adj, bool lock_sbq)
err = ice_ptp_prep_phy_adj_eth56g(hw, adj, lock_sbq);
break;
case ICE_PHY_E830:
- /* E830 sync PHYs automatically after setting GLTSYN_SHADJ */
- return 0;
+ /* E830 sync PHYs automatically after setting cmd register */
+ break;
case ICE_PHY_E810:
err = ice_ptp_prep_phy_adj_e810(hw, adj, lock_sbq);
break;
--
2.47.1
next prev parent reply other threads:[~2026-03-09 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 9:52 [PATCH v1 0/6] Update ICE Base Driver Soumyadeep Hore
2026-03-10 9:52 ` [PATCH v1 1/6] net/ice/base: update crash on invalid topology Soumyadeep Hore
2026-03-10 9:52 ` [PATCH v1 2/6] net/ice/base: resolve comparison-with-wider-type violations Soumyadeep Hore
2026-03-10 9:52 ` [PATCH v1 3/6] net/ice/base: enable LLDP filter control for E830 Soumyadeep Hore
2026-03-10 9:52 ` [PATCH v1 4/6] net/ice/base: support RDMA on 4+ ports of E830 Soumyadeep Hore
2026-03-10 9:52 ` [PATCH v1 5/6] net/ice/base: add pending admin queue events API Soumyadeep Hore
2026-03-10 9:52 ` Soumyadeep Hore [this message]
2026-03-10 14:08 ` [PATCH v1 0/6] Update ICE Base Driver Bruce Richardson
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=20260310095218.703423-16-soumyadeep.hore@intel.com \
--to=soumyadeep.hore@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=grzegorz.nitka@intel.com \
--cc=manoj.kumar.subbarao@intel.com \
--cc=stable@dpdk.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