From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
mchehab@kernel.org, hans.verkuil@cisco.com
Cc: linux-amlogic@lists.infradead.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH v6 0/4] media: meson: vdec: Add compliant H264 support
Date: Mon, 02 Mar 2020 17:23:29 +0100 [thread overview]
Message-ID: <7h4kv6sp32.fsf@baylibre.com> (raw)
In-Reply-To: <20200219140156.22893-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> Hello,
>
> This patch series aims to bring H.264 support as well as compliance update
> to the amlogic stateful video decoder driver.
>
> The issue in the V1 patchset at [1] is solved by patch #1 following comments
> and requirements from hans. It moves the full draining & stopped state tracking
> and handling from vicodec to core v4l2-mem2mem.
>
> The vicodec changes still passes the v4l2-utils "media-test" tests, log at [5]:
> [...]
> vicodec media controller compliance tests
Tested on meson-sm1-sei610.
Tested-by: Kevin Hilman <khilman@baylibre.com>
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
mchehab@kernel.org, hans.verkuil@cisco.com
Cc: linux-amlogic@lists.infradead.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH v6 0/4] media: meson: vdec: Add compliant H264 support
Date: Mon, 02 Mar 2020 17:23:29 +0100 [thread overview]
Message-ID: <7h4kv6sp32.fsf@baylibre.com> (raw)
In-Reply-To: <20200219140156.22893-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> Hello,
>
> This patch series aims to bring H.264 support as well as compliance update
> to the amlogic stateful video decoder driver.
>
> The issue in the V1 patchset at [1] is solved by patch #1 following comments
> and requirements from hans. It moves the full draining & stopped state tracking
> and handling from vicodec to core v4l2-mem2mem.
>
> The vicodec changes still passes the v4l2-utils "media-test" tests, log at [5]:
> [...]
> vicodec media controller compliance tests
Tested on meson-sm1-sei610.
Tested-by: Kevin Hilman <khilman@baylibre.com>
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
mchehab@kernel.org, hans.verkuil@cisco.com
Cc: Neil Armstrong <narmstrong@baylibre.com>,
linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] media: meson: vdec: Add compliant H264 support
Date: Mon, 02 Mar 2020 17:23:29 +0100 [thread overview]
Message-ID: <7h4kv6sp32.fsf@baylibre.com> (raw)
In-Reply-To: <20200219140156.22893-1-narmstrong@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> Hello,
>
> This patch series aims to bring H.264 support as well as compliance update
> to the amlogic stateful video decoder driver.
>
> The issue in the V1 patchset at [1] is solved by patch #1 following comments
> and requirements from hans. It moves the full draining & stopped state tracking
> and handling from vicodec to core v4l2-mem2mem.
>
> The vicodec changes still passes the v4l2-utils "media-test" tests, log at [5]:
> [...]
> vicodec media controller compliance tests
Tested on meson-sm1-sei610.
Tested-by: Kevin Hilman <khilman@baylibre.com>
Kevin
next prev parent reply other threads:[~2020-03-02 16:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 14:01 [PATCH v6 0/4] media: meson: vdec: Add compliant H264 support Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-02-19 14:01 ` [PATCH v6 1/4] media: v4l2-mem2mem: handle draining, stopped and next-buf-is-last states Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-02-19 14:01 ` [PATCH v6 2/4] media: vicodec: use v4l2-mem2mem draining, stopped and next-buf-is-last states handling Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-02-19 14:01 ` [PATCH v6 3/4] media: meson: vdec: bring up to compliance Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-02-19 14:01 ` [PATCH v6 4/4] media: meson: vdec: add H.264 decoding support Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-02-19 14:01 ` Neil Armstrong
2020-03-02 16:23 ` Kevin Hilman [this message]
2020-03-02 16:23 ` [PATCH v6 0/4] media: meson: vdec: Add compliant H264 support Kevin Hilman
2020-03-02 16:23 ` Kevin Hilman
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=7h4kv6sp32.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=narmstrong@baylibre.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.