Commit 185d4c8b authored by Ariel Elior's avatar Ariel Elior Committed by David S. Miller

bnx2x: remove false warning regarding interrupt number

Since version 7.4 the FW configures in the pci config space the max
number of interrupts available to the physical function, instead of
the exact number to use.
This causes a false warning in driver when comparing the number of
configured interrupts to the number about to be used.
Signed-off-by: default avatarAriel Elior <ariele@broadcom.com>
Signed-off-by: default avatarEilon Greenstein <eilong@broadcom.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent c0d680e5
...@@ -9831,12 +9831,13 @@ static void __devinit bnx2x_get_igu_cam_info(struct bnx2x *bp) ...@@ -9831,12 +9831,13 @@ static void __devinit bnx2x_get_igu_cam_info(struct bnx2x *bp)
} }
#ifdef CONFIG_PCI_MSI #ifdef CONFIG_PCI_MSI
/* /* Due to new PF resource allocation by MFW T7.4 and above, it's
* It's expected that number of CAM entries for this functions is equal * optional that number of CAM entries will not be equal to the value
* to the number evaluated based on the MSI-X table size. We want a * advertised in PCI.
* harsh warning if these values are different! * Driver should use the minimal value of both as the actual status
* block count
*/ */
WARN_ON(bp->igu_sb_cnt != igu_sb_cnt); bp->igu_sb_cnt = min_t(int, bp->igu_sb_cnt, igu_sb_cnt);
#endif #endif
if (igu_sb_cnt == 0) if (igu_sb_cnt == 0)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment