Linux Media Controller development
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Tomasz Figa <tfiga@chromium.org>, Chris Healy <cphealy@gmail.com>
Subject: Re: [PATCH] hantro: Remove dedicated control documentation
Date: Tue, 19 Jul 2022 15:34:24 -0400	[thread overview]
Message-ID: <d9fa1648e63542dc4cc1ff6f56d8cd019a0d3e67.camel@collabora.com> (raw)
In-Reply-To: <20220718214123.73275-2-ezequiel@vanguardiasur.com.ar>

Le lundi 18 juillet 2022 à 18:41 -0300, Ezequiel Garcia a écrit :
> The dedicated control required by the HEVC support
> was removed, and the driver now calculates the value
> internally. Remove the ad-hoc documentation as well.
> 
> Fixes: 3360755ef89ab ("media: hantro: Stop using Hantro dedicated control")
> Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>

Reviewed-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>

> ---
>  .../userspace-api/media/drivers/hantro.rst    | 19 -------------------
>  1 file changed, 19 deletions(-)
>  delete mode 100644 Documentation/userspace-api/media/drivers/hantro.rst
> 
> diff --git a/Documentation/userspace-api/media/drivers/hantro.rst b/Documentation/userspace-api/media/drivers/hantro.rst
> deleted file mode 100644
> index cd9754b4e005..000000000000
> --- a/Documentation/userspace-api/media/drivers/hantro.rst
> +++ /dev/null
> @@ -1,19 +0,0 @@
> -.. SPDX-License-Identifier: GPL-2.0
> -
> -Hantro video decoder driver
> -===========================
> -
> -The Hantro video decoder driver implements the following driver-specific controls:
> -
> -``V4L2_CID_HANTRO_HEVC_SLICE_HEADER_SKIP (integer)``
> -    Specifies to Hantro HEVC video decoder driver the number of data (in bits) to
> -    skip in the slice segment header.
> -    If non-IDR, the bits to be skipped go from syntax element "pic_output_flag"
> -    to before syntax element "slice_temporal_mvp_enabled_flag".
> -    If IDR, the skipped bits are just "pic_output_flag"
> -    (separate_colour_plane_flag is not supported).
> -
> -.. note::
> -
> -        This control is not yet part of the public kernel API and
> -        it is expected to change.


  reply	other threads:[~2022-07-19 19:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 21:41 [PATCH] media: destage Hantro VPU driver Ezequiel Garcia
2022-07-18 21:41 ` [PATCH] hantro: Remove dedicated control documentation Ezequiel Garcia
2022-07-19 19:34   ` Nicolas Dufresne [this message]
2022-07-18 21:41 ` [PATCH] hantro: Remove incorrect HEVC SPS validation Ezequiel Garcia
2022-07-18 21:48   ` Ezequiel Garcia
2022-07-19 19:33 ` [PATCH] media: destage Hantro VPU driver Nicolas Dufresne

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=d9fa1648e63542dc4cc1ff6f56d8cd019a0d3e67.camel@collabora.com \
    --to=nicolas.dufresne@collabora.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=cphealy@gmail.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=tfiga@chromium.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