public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: smitha.t@samsung.com (Smitha T Murthy)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v4 00/12] Add MFC v10.10 support
Date: Tue, 13 Jun 2017 10:54:11 +0530	[thread overview]
Message-ID: <1497331451.22203.8.camel@smitha-fedora> (raw)
In-Reply-To: <95f6389c-4535-75c0-dcc9-6076b76777a0@samsung.com>

On Fri, 2017-06-09 at 19:36 +0200, Sylwester Nawrocki wrote:
> On 04/06/2017 08:11 AM, Smitha T Murthy wrote:
> > This patch series adds MFC v10.10 support. MFC v10.10 is used in some
> > of Exynos7 variants.
> > 
> > This adds support for following:
> > 
> > * Add support for HEVC encoder and decoder
> > * Add support for VP9 decoder
> > * Update Documentation for control id definitions
> > * Update computation of min scratch buffer size requirement for V8 onwards
> Smitha, do you have any updates on this?  IIRC, there were few things
> which needed corrections but we were rather close to the final version.
> 
> --
> Thanks,
> Sylwester
> 
Hi Sylwester,

Sorry, I am currently held up with some other work. I will try to make
time and work on the next the updated patch series soon.

Regards,
Smitha

      reply	other threads:[~2017-06-13  5:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170406060957epcas1p36f883512ccfaf24359d1b31a6d199d87@epcas1p3.samsung.com>
2017-04-06  6:11 ` [Patch v4 00/12] Add MFC v10.10 support Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 01/12] [media] s5p-mfc: Rename IS_MFCV8 macro Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 02/12] [media] s5p-mfc: Adding initial support for MFC v10.10 Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 03/12] [media] s5p-mfc: Use min scratch buffer size as provided by F/W Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 04/12] [media] s5p-mfc: Support MFCv10.10 buffer requirements Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 05/12] [media] videodev2.h: Add v4l2 definition for HEVC Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 06/12] [media] v4l2-ioctl: add HEVC format description Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 07/12] Documentation: v4l: Documentation for HEVC v4l2 definition Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 08/12] [media] s5p-mfc: Add support for HEVC decoder Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 09/12] [media] s5p-mfc: Add VP9 decoder support Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 10/12] [media] v4l2: Add v4l2 control IDs for HEVC encoder Smitha T Murthy
2017-04-06 13:14     ` Sylwester Nawrocki
2017-04-07  8:31       ` Smitha T Murthy
2017-04-07  9:25         ` Sylwester Nawrocki
2017-04-07  9:54           ` Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 11/12] [media] s5p-mfc: Add support " Smitha T Murthy
2017-04-06  6:11   ` [Patch v4 12/12] Documention: v4l: Documentation for HEVC CIDs Smitha T Murthy
2017-04-06 13:33     ` Hans Verkuil
2017-04-07  8:37       ` Smitha T Murthy
2017-04-06 14:47     ` Sylwester Nawrocki
2017-04-07 10:03       ` Smitha T Murthy
2017-04-07 10:26         ` Sylwester Nawrocki
2017-04-07 12:08           ` Smitha T Murthy
2017-06-09 17:36   ` [Patch v4 00/12] Add MFC v10.10 support Sylwester Nawrocki
2017-06-13  5:24     ` Smitha T Murthy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1497331451.22203.8.camel@smitha-fedora \
    --to=smitha.t@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox