openbcm

commit 1122325a610a115fce4439dcc0d8356af942d54c
parent 60da5b586fe1c064d2fd00772a7f6364b94899d8
Author: Broadcom SDK Release <sdk.releases@broadcom.com>
Date:   Thu, 18 Apr 2019 16:05:52 +0300

SDK-166533: Flags supported and Ramon API fix.

Devices: 88790_A0
Module: SOC

Symptom:
Support to add new flags in _cmicx_sbusdma_reg_array_write_prog()

Diffstat:
M
sdk-6.5.16/src/soc/common/sbusdma.c
 | 
16
+++++++++++++++-

1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/sdk-6.5.16/src/soc/common/sbusdma.c b/sdk-6.5.16/src/soc/common/sbusdma.c
@@ -97,7 +97,21 @@ _soc_mem_array_sbusdma_read(int unit, soc_mem_t mem, unsigned array_index,
     param.index_begin = index_min;
     param.index_end = index_max;
     param.copyno = copyno;
-    param.flags = 0;
+
+#if defined(BCM_TRIDENT2_SUPPORT) || defined(BCM_TRIDENT2PLUS_SUPPORT) || defined(BCM_MONTEREY_SUPPORT) || defined(BCM_APACHE_SUPPORT)
+    if (SOC_IS_TRIDENT2X(unit)) {
+        /* The ser and access flags use different macros, using the same bits.
+         They were not designed to be specified by the same values.
+         The argument contains a flags field supporting
+         SOC_MEM_WRITE_* values, and does not support any _SOC_SER_FLAG_* flags.
+         TD2X device seem to have code specifying SOC_MEM_WRITE_* flags in serflags arguments. */
+        param.flags = ser_flags;
+    }
+    else
+#endif
+    {
+        param.flags = 0;
+    }
     param.buffer = buffer;
     param.vchan = vchan;