* Question about commit 44dddd14059 in DPDK e1000 driver
@ 2022-03-08 14:03 Francesco Mancino
0 siblings, 0 replies; only message in thread
From: Francesco Mancino @ 2022-03-08 14:03 UTC (permalink / raw)
To: dev
I have a question about some changes to the e1000 driver that where
committed in 2020 (commit 44dddd14059f151f39f7e075b887decfc9a10f11).
I see that e1000_power_down_phy_copper_82575 has been replaced by
e1000_power_down_phy_copper_base, but the two functions are not the same.
more specifically in the old function we had this code:
-STATIC void e1000_power_down_phy_copper_82575(struct e1000_hw *hw)
-{
- struct e1000_phy_info *phy = &hw->phy;
-
- if (!(phy->ops.check_reset_block))
- return;
-
- /* If the management interface is not enabled, then power down */
- if (!(e1000_enable_mng_pass_thru(hw) ||
phy->ops.check_reset_block(hw)))
- e1000_power_down_phy_copper(hw);
-
- return;
-}
And the new looks like this:
+void e1000_power_down_phy_copper_base(struct e1000_hw *hw)
+{
+ struct e1000_phy_info *phy = &hw->phy;
+
+ if (!(phy->ops.check_reset_block))
+ return;
+
+ /* If the management interface is not enabled, then power down */
+ if (phy->ops.check_reset_block(hw))
+ e1000_power_down_phy_copper(hw);
+}
The 'if' condition is different, and almost opposite.
Is this intentional?
In my usecase I do not manage to put the link down with the most recent
DPDK (21.11), but it worked fine with 19.11. Should a configure
something differently?
Best regards,
Francesco Mancino
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-03-08 14:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-08 14:03 Question about commit 44dddd14059 in DPDK e1000 driver Francesco Mancino
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).