blob: e96f873ea913bff0112def78cd8ac5f01db84c42 [file] [log] [blame]
b.liue9582032025-04-17 19:18:16 +08001From 3cf2ff1c53b41c60fcb7667a11c4947fe5136de7 Mon Sep 17 00:00:00 2001
2From: Madalin Bucur <madalin.bucur@nxp.com>
3Date: Thu, 7 Mar 2019 16:33:37 +0200
4Subject: [PATCH] sdk_dpaa: remove the QM_FQCTRL_PREFERINCACHE flag
5
6Only a limited number of FQs can be in the cache, setting the
7QM_FQCTRL_PREFERINCACHE flag for all FQs is not useful.
8
9Signed-off-by: Madalin Bucur <madalin.bucur@nxp.com>
10---
11 drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.c | 2 --
12 1 file changed, 2 deletions(-)
13
14--- a/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.c
15+++ b/drivers/net/ethernet/freescale/sdk_dpaa/dpaa_eth_common.c
16@@ -1237,8 +1237,6 @@ int dpa_fq_init(struct dpa_fq *dpa_fq, b
17 memset(&initfq, 0, sizeof(initfq));
18
19 initfq.we_mask = QM_INITFQ_WE_FQCTRL;
20- /* FIXME: why would we want to keep an empty FQ in cache? */
21- initfq.fqd.fq_ctrl = QM_FQCTRL_PREFERINCACHE;
22
23 /* Try to reduce the number of portal interrupts for
24 * Tx Confirmation FQs.