public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: anatoly.burakov@intel.com,
	Bruce Richardson <bruce.richardson@intel.com>,
	stable@dpdk.org
Subject: [PATCH] net/ice/base: fix double HW reinitialization
Date: Thu, 26 Mar 2026 18:20:35 +0000	[thread overview]
Message-ID: <20260326182035.726123-1-bruce.richardson@intel.com> (raw)

After downloading an alternate scheduler topology, the HW needs to be
reinitialized. Since commit b47c1229d617 ("net/ice/base: improve global
config lock behavior"), a reinitialization is done in the topology
download code itself, so we need to remove the extra initialization from
the calling code.

Fixes: b47c1229d617 ("net/ice/base: improve global config lock behavior")
Cc: stable@dpdk.org

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
 drivers/net/intel/ice/base/ice_ddp.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/drivers/net/intel/ice/base/ice_ddp.c b/drivers/net/intel/ice/base/ice_ddp.c
index 68e75be4d2..ae80d93656 100644
--- a/drivers/net/intel/ice/base/ice_ddp.c
+++ b/drivers/net/intel/ice/base/ice_ddp.c
@@ -1359,10 +1359,6 @@ enum ice_ddp_state ice_init_pkg(struct ice_hw *hw, u8 *buf, u32 len, bool load_s
 				  res);
 			return ICE_DDP_PKG_ERR;
 		}
-		ice_debug(hw, ICE_DBG_INIT,
-			  "Topology download successful, reinitializing device\n");
-		ice_deinit_hw(hw);
-		ice_init_hw(hw);
 	}
 
 	/* initialize package info */
-- 
2.51.0


             reply	other threads:[~2026-03-26 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 18:20 Bruce Richardson [this message]
2026-03-27 11:21 ` [PATCH] net/ice/base: fix double HW reinitialization Loftus, Ciara
2026-03-27 11:45   ` 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=20260326182035.726123-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --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