From: "Daniel Almeida" <daniel.almeida@collabora.com>
To: "Detlev Casanova" <detlev.casanova@collabora.com>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@kernel.org>
Subject: Re: [PATCH 2/2] doc: visl: Add AV1 support
Date: Fri, 10 Nov 2023 20:46:21 +0000 [thread overview]
Message-ID: <6093-654e9680-3-67fa3a80@264835418> (raw)
In-Reply-To: <20231030193406.70126-3-detlev.casanova@collabora.com>
Hi Detlev,
This does not apply anymore (media_tree/master -> 2e6bf8ce2af120df033fee1ec42f5e78596f5c44)
As for the changes,
Reviewed-by: Daniel Almeida <daniel.almeida@collabora.com>
> Add AV1 information in visl documentation.
>
> Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
> ---
> Documentation/admin-guide/media/visl.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/admin-guide/media/visl.rst b/Documentation/admin-guide/media/visl.rst
> index 7d2dc78341c9..64229857c17c 100644
> --- a/Documentation/admin-guide/media/visl.rst
> +++ b/Documentation/admin-guide/media/visl.rst
> @@ -71,6 +71,7 @@ The following codecs are supported:
> - VP9
> - H.264
> - HEVC
> +- AV1
>
> visl trace events
> -----------------
> @@ -79,6 +80,7 @@ The trace events are defined on a per-codec basis, e.g.:
> .. code-block:: bash
>
> $ ls /sys/kernel/debug/tracing/events/ | grep visl
> + visl_av1_controls
> visl_fwht_controls
> visl_h264_controls
> visl_hevc_controls
> --
> 2.41.0
>
prev parent reply other threads:[~2023-11-10 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 19:27 [PATCH 0/2] visl: Add support for AV1 Detlev Casanova
2023-10-30 19:27 ` [PATCH 1/2] visl: Add AV1 support Detlev Casanova
2023-11-10 20:44 ` Daniel Almeida
2023-10-30 19:27 ` [PATCH 2/2] doc: " Detlev Casanova
2023-11-10 20:46 ` Daniel Almeida [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=6093-654e9680-3-67fa3a80@264835418 \
--to=daniel.almeida@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.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
all inboxes | Powered by JetHome®