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