(no commit message)

diff --git a/openpower/sv/compliancy_levels.mdwn b/openpower/sv/compliancy_levels.mdwn
index 11d54bf788acd0e4a3ac58c3bd811476d65d214c..809de7f4aee9080d2e287d5c19506c0c293b3ab5 100644 (file)
--- a/openpower/sv/compliancy_levels.mdwn
+++ b/openpower/sv/compliancy_levels.mdwn
@@ -29,12 +29,11 @@ Summary of Compliancy Levels, each Level includes all lower levels:
   Predicates, if used, may still raise illegal instruction trap.
 * **DSP/AV**: 128 registers,
    element-width
-  overrides, and all Modes (Saturation, Fail-First, Predicate-Result,
-  Mapreduce/Iteration)
+  overrides, and Saturation and Mapreduce/Iteration Modes.
 * **3D/Advanced/Supercomputing**:  all SV Branch instructions;
-  crweird instructions;
+  crweird and vector-assist instructions (`set-before-first` etc);
   Matrix, DCT/FFT and Indexing
-  REMAP capability
+  REMAP capability; Fail-First and Predicate-Result Modes.
 
 These requirements within each Level constitute the minimum mandatory
 capabilities.
@@ -113,3 +112,11 @@ This level is best suited to high-performance power-efficient but
 specialist Compute workloads.  128 GPRs, FPRs and CR Fields are all
 required, as is element-width overrides to allow data processing
 down to the 8-bit level.
+
+All SVP64 Modes are required to be implemented in hardware: Saturation
+in particular is a necessity for Audio DSP work. Reduction as well to
+assist with Audio/Video.
+
+It is not mandatory for this Level to have DCT/FFT REMAP Capability but
+due to the high prevalence of DCT and FFT in Audio, Video and DSP
+workloads it is strongly recommended.