[Libva] [PATCH 33/42] API: h264 encode: document DPB usage.

[Xiang, Haihao]

From: Gwenole Beauchesne <gwenole.beauchesne at intel.com>

---
 va/va_enc_h264.h |   17 ++++++++++++++---
 1 files changed, 14 insertions(+), 3 deletions(-)

diff --git a/va/va_enc_h264.h b/va/va_enc_h264.h
index 4a7e7ee..cd2a3bd 100644
--- a/va/va_enc_h264.h
+++ b/va/va_enc_h264.h
@@ -231,10 +231,21 @@ typedef struct _VAEncSequenceParameterBufferH264 {
  * \c vaRenderPicture() call as this picture parameter buffer.
  */
 typedef struct _VAEncPictureParameterBufferH264 {
-    /** \brief Information about the picture to be encoded. */
+    /**
+     * \brief Information about the picture to be encoded.
+     *
+     * See #VAPictureH264 for further description of each field.
+     * Note that CurrPic.picture_id represents the reconstructed
+     * (decoded) picture. User provides a scratch VA surface ID here.
+     */
     VAPictureH264   CurrPic;
-    /** \brief Decoded Picture Buffer (DPB).
-     *  XXX: is this really used?
+    /**
+     * \brief Decoded Picture Buffer (DPB).
+     *
+     * This array represents the list of reconstructed (decoded)
+     * frames used as reference. It is important to keep track of
+     * reconstructed frames so that they can be used later on as
+     * reference for P or B-frames encoding.
      */
     VAPictureH264   ReferenceFrames[16];
     /**
-- 
1.7.4.1