All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Sofus Forstreuter" <sofus.c@icloud.com>
Cc: devicetree@vger.kernel.org, media-ci@linuxtv.org,
	conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH 01/14] media: v4l2: Add P210 pixel format
Date: Fri, 18 Sep 2026 13:26:10 +0000	[thread overview]
Message-ID: <20260918132610.8F30E1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918-avd-v1-1-49977931f455@icloud.com>

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Low] media: v4l2: incomplete UAPI documentation for P210 format
- [Low] media: v4l2: incorrect bits-per-pixel comment for V4L2_PIX_FMT_P210
- [Low] media: v4l2: reStructuredText underline too short for section title
--

commit babd80a26581f15a410f128ba302cfa3a34c05de
Author: Sofus Forstreuter <sofus.c@icloud.com>

media: v4l2: Add P210 pixel format

This commit adds support for the P210 pixel format. P210 is a YUV format
with 10-bits per component with interleaved UV.

> diff --git a/Documentation/userspace-api/media/v4l/pixfmt-yuv-planar.rst b/Documentation/userspace-api/media/v4l/pixfmt-yuv-planar.rst
> index 0631919bd667b..8509f2415c9b8 100644
> --- a/Documentation/userspace-api/media/v4l/pixfmt-yuv-planar.rst
> +++ b/Documentation/userspace-api/media/v4l/pixfmt-yuv-planar.rst
[ ... ]
> @@ -834,8 +841,9 @@ number of lines as the luma plane.
>  
>  .. _V4L2_PIX_FMT_P010:
>  .. _V4L2-PIX-FMT-P010-4L4:
> +.. _V4L2-PIX-FMT-P210:
>  
> -P010 and tiled P010
> +P010, tiled P010 and P210
>  -------------------

[Severity: Low]
Is this underline length still correct? The section title was extended to
include P210, but the underline remains 19 characters, which might cause a
Sphinx documentation build warning.

>  
>  P010 is like NV12 with 10 bits per component, expanded to 16 bits.

[Severity: Low]
Does this description need an update to cover P210? The section title now
includes P210, but the text exclusively describes the 4:2:0 layout of P010
without clarifying P210's 4:2:2 structure.

> diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
> index 5373dba640fae..b5949c378f2eb 100644
> --- a/include/uapi/linux/videodev2.h
> +++ b/include/uapi/linux/videodev2.h
[ ... ]
> @@ -659,6 +659,7 @@ struct v4l2_pix_format {
>  #define V4L2_PIX_FMT_NV42    v4l2_fourcc('N', 'V', '4', '2') /* 24  Y/CrCb 4:4:4  */
>  #define V4L2_PIX_FMT_P010    v4l2_fourcc('P', '0', '1', '0') /* 24  Y/CbCr 4:2:0 10-bit per component */
>  #define V4L2_PIX_FMT_P012    v4l2_fourcc('P', '0', '1', '2') /* 24  Y/CbCr 4:2:0 12-bit per component */
> +#define V4L2_PIX_FMT_P210    v4l2_fourcc('P', '2', '1', '0') /* 24  Y/CbCr 4:2:2 10-bit per component */

[Severity: Low]
Is the bits-per-pixel comment accurate here? The comment states "24" average
bits per pixel, which is correct for 4:2:0 formats like P010, but shouldn't
a 4:2:2 format like P210 have an average of 32 bits per pixel?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260918-avd-v1-0-49977931f455@icloud.com?part=1

  reply	other threads:[~2026-09-18 13:26 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 13:15 [PATCH 00/14] media: apple: add avd driver Sofus Forstreuter
2026-09-18 13:15 ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 01/14] media: v4l2: Add P210 pixel format Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:26   ` sashiko-bot [this message]
2026-09-18 13:15 ` [PATCH 02/14] dt-bindings: media: add apple,avd Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:22   ` sashiko-bot
2026-09-19  6:46   ` Krzysztof Kozlowski
2026-09-19  6:46     ` Krzysztof Kozlowski
2026-09-20  7:53     ` Sofus Forstreuter
2026-09-20  7:53       ` Sofus Forstreuter
2026-09-20 10:08       ` Krzysztof Kozlowski
2026-09-20 10:08         ` Krzysztof Kozlowski
2026-09-20 11:08         ` Sofus Forstreuter
2026-09-20 11:08           ` Sofus Forstreuter
2026-09-20  8:10   ` Andy Yan
2026-09-20  8:10     ` Andy Yan
2026-09-20 10:50     ` [PATCH " Sofus Forstreuter
2026-09-20 10:50       ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 03/14] arm64: dts: apple: t8103: add avd nodes Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:25   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 04/14] arm64: dts: apple: t8112: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:25   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 05/14] arm64: dts: apple: t8122: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:24   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 06/14] arm64: dts: apple: t600x: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 07/14] arm64: dts: apple: t602x: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 08/14] arm64: dts: apple: t6030: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:28   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 09/14] arm64: dts: apple: t6031: " Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 10/14] media: apple: add avd driver Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:36   ` sashiko-bot
2026-09-19  6:49   ` Krzysztof Kozlowski
2026-09-19  6:49     ` Krzysztof Kozlowski
2026-09-19 10:49     ` Sofus Forstreuter
2026-09-19 10:49       ` Sofus Forstreuter
2026-09-18 13:15 ` [PATCH 11/14] media: apple: avd: add h264 support Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:40   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 12/14] media: apple: avd: add vp9 support Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:42   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 13/14] media: apple: avd: add hevc support Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:46   ` sashiko-bot
2026-09-18 13:15 ` [PATCH 14/14] media: apple: avd: add av1 support Sofus Forstreuter
2026-09-18 13:15   ` Sofus Forstreuter
2026-09-18 13:43   ` sashiko-bot

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=20260918132610.8F30E1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=media-ci@linuxtv.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=sofus.c@icloud.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.