From: sashiko-bot@kernel.org
To: "Pranay Samala" <pranay.samala@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] video/hdmi: Add hdmi_eotf_get_name()
Date: Tue, 06 Oct 2026 05:48:09 +0000 [thread overview]
Message-ID: <20261006054809.8C12D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261006054004.285744-2-pranay.samala@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] video/hdmi: missing hdmi_eotf_get_name() usage in hdmi_drm_infoframe_log()
--
commit b4b5c92367345e70aebcf91cfdea62895c2744ff
Author: Pranay Samala <pranay.samala@intel.com>
video/hdmi: Add hdmi_eotf_get_name()
This patch introduces hdmi_eotf_get_name() to provide human-readable strings
for electro-optical transfer functions. The helper is placed next to other
similar hdmi string helpers.
> diff --git a/drivers/video/hdmi.c b/drivers/video/hdmi.c
> index 45b42f14a7503..cd62afcd38d7d 100644
> --- a/drivers/video/hdmi.c
> +++ b/drivers/video/hdmi.c
[ ... ]
> +const char *hdmi_eotf_get_name(enum hdmi_eotf eotf)
> +{
> + switch (eotf) {
> + case HDMI_EOTF_TRADITIONAL_GAMMA_SDR:
> + return "Traditional gamma SDR";
> + case HDMI_EOTF_TRADITIONAL_GAMMA_HDR:
> + return "Traditional gamma HDR";
> + case HDMI_EOTF_SMPTE_ST2084:
> + return "SMPTE ST2084";
> + case HDMI_EOTF_BT_2100_HLG:
> + return "BT.2100 HLG";
> + }
> + return "Invalid";
> +}
> +EXPORT_SYMBOL(hdmi_eotf_get_name);
> +
> static void hdmi_drm_infoframe_log(const char *level,
> struct device *dev,
> const struct hdmi_drm_infoframe *frame)
[Severity: Low]
This isn't a bug, but could hdmi_drm_infoframe_log() be updated to use this
new helper?
Currently, the function logs the eotf field as a raw integer:
drivers/video/hdmi.c:hdmi_drm_infoframe_log() {
...
hdmi_log("eotf: %d\n", frame->eotf);
...
}
Updating this to use hdmi_eotf_get_name() would match the surrounding log
format conventions.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261006054004.285744-1-pranay.samala@intel.com?part=1
next prev parent reply other threads:[~2026-10-06 5:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 5:40 [PATCH v2 0/2] Expose HDR status in debugfs Pranay Samala
2026-10-06 5:40 ` [PATCH v2 1/2] video/hdmi: Add hdmi_eotf_get_name() Pranay Samala
2026-10-06 5:48 ` sashiko-bot [this message]
2026-10-06 5:40 ` [PATCH v2 2/2] drm/i915/debugfs: Add HDR status to i915_display_info Pranay Samala
2026-10-06 5:48 ` ✓ CI.KUnit: success for Expose HDR status in debugfs Patchwork
2026-10-06 6:29 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-06 15:01 ` ✓ Xe.CI.FULL: " Patchwork
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=20261006054809.8C12D1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=pranay.samala@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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