venc: Set max supported AVC level to OMX_VIDEO_AVCLevel42 on 8916

 * Venus supports this level and it's needed for HSR.

Change-Id: I5bc6a77ff14cebbc8457fdf23636185d054ba203
Revert "mm-video-v4l2: Update video resolution when updating crop"

This reverts commit 1fb9417d029fe2bd1478ffcf8dde4f2355b2aaf8.
Reverting the change because video resolution is not expected
to be updated based on the crop parameters from video driver.
Alternatively change-id I22ddc9961a271eea379a08534c769f2842142d8f
will resolve the failure.

Change-Id: I3954cadec21eb6c8da40c792d87995f817be1efb
mm-video: vdec: Correct video driver's crop parameters handling

Remove updating video resolution when crop parameters are changed
Update video resolution only when "port settings changed sufficient"
event is received from the driver. Make sure the video resolution
is updated after all the pending fbds are rendered with the old
resolution by queuing the event in ftb queue instead of cmd queue.

Change-Id: I22ddc9961a271eea379a08534c769f2842142d8f
mm_video: vidc: Update buffer geometry with stride and scanline

Update buffer geometry dimensions using stride and snanline.
Earlier it was updated conditionally to handle downscalar case.
Now component is fetching all updated dimensions in case of
crop event, so stride and scanline can be used for the same.

Change-Id: If44a6df8498bff2ce39c9428b3708adbee7b8542
mm-video: vdec: Get updated resolution along with output buffers

In case of smooth streaming the driver width/height might be
be updated multiple times before VIDIOC_G_FMT call was made to
the driver to get first updated width/height itself if the input
sequence has Header(w1xh1), AU data, Header(w2xh2), AU data and so on.
So client need to get the width/height along with output buffer itself
to update the display with correct width/height for every output frame
and skip calling VIDIOC_G_FMT to driver to get width/height.

Change-Id: I31992315a84350ddb7a43577dc70235ad9a8bc8f
mm-video: vidc: Avoid setting invalid timestamp of eos NAL

In arbitrary mode when eos NAL is appened at the end, while
coalscing with destination buffer, the actual timestamp is
overwritten with LLONG_MAX. This will lead to error log and
setting the flag V4L2_QCOM_BUF_TIMESTAMP_INVALID in driver,
which is not needed.

Change-Id: I87a63c4cb9d8259280b781cdd553050580809e8e
Merge branch 'cm-11.0' of https://github.com/CyanogenMod/android_hardware_qcom_media-caf-new into cm-11.0