: [PATCH v3 02/13] OMAP: DMA: Introduce errata
handling feature
G, Manjunath Kondaiah manj...@ti.com writes:
Implement errata handling to use flags instead of cpu_is_*
and cpu_class_* in the code.
The errata flags are initialized at init time and during runtime
we are using
G, Manjunath Kondaiah manj...@ti.com writes:
[...]
+ if (omap_type() == OMAP3430_REV_ES1_0)
+ SET_DMA_ERRATA(DMA_ERRATA_i88);
+
+ /*
+ * Errata 3.2/3.3: sometimes 0 is returned if CSAC/CDAC is
This doesn't look like a unique errata identifier. Chapter 3
is usually
: Re: [PATCH v3 02/13] OMAP: DMA: Introduce errata
handling feature
G, Manjunath Kondaiah manj...@ti.com writes:
[...]
+if (omap_type() == OMAP3430_REV_ES1_0)
+SET_DMA_ERRATA(DMA_ERRATA_i88);
+
+/*
+ * Errata 3.2/3.3: sometimes 0
G, Manjunath Kondaiah manj...@ti.com writes:
Implement errata handling to use flags instead of cpu_is_*
and cpu_class_* in the code.
The errata flags are initialized at init time and during runtime
we are using the errata variable (via the IS_DMA_ERRATA macro)
to execute the required errata
Implement errata handling to use flags instead of cpu_is_*
and cpu_class_* in the code.
The errata flags are initialized at init time and during runtime
we are using the errata variable (via the IS_DMA_ERRATA macro)
to execute the required errata workaround.
Reused errata handling patch from
