From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/bridge: dw-hdmi-qp: Return -EOPNOTSUPP in HDMI audio functions
Date: Mon, 25 May 2026 22:33:16 +1000 [thread overview]
Message-ID: <review-overall-20260519-fix-hdmi-audio-warnings-v1-1-9608966c993f@collabora.com> (raw)
In-Reply-To: <20260519-fix-hdmi-audio-warnings-v1-1-9608966c993f@collabora.com>
Overall Series Review
Subject: drm/bridge: dw-hdmi-qp: Return -EOPNOTSUPP in HDMI audio functions
Author: Detlev Casanova <detlev.casanova@collabora.com>
Patches: 1
Reviewed: 2026-05-25T22:33:16.962963
---
This is a single-patch series that changes the error code returned by the `dw_hdmi_qp_audio_enable` and `dw_hdmi_qp_audio_prepare` callbacks from `-ENODEV` (and implicit success-when-not-ready) to `-EOPNOTSUPP` when `tmds_char_rate == 0` (i.e., HDMI is not connected).
The change is well-motivated and correct. The ASoC framework's `snd_soc_ret()` function (`sound/soc/soc-utils.c:18-42`) explicitly suppresses logging for `-EOPNOTSUPP` and `-ENOTSUPP`, while all other negative error codes (including the previous `-ENODEV`) produce `dev_err` messages. This means the old code was generating spurious error logs whenever audio operations were attempted while HDMI was disconnected — a normal and frequent runtime condition.
The semantic choice is also correct: `-EOPNOTSUPP` ("operation not supported") accurately describes a transient state where the hardware exists but clocks aren't enabled yet, whereas `-ENODEV` ("no such device") incorrectly suggests the hardware is absent.
**Verdict: Looks good. Suitable for merging.**
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-25 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 18:00 [PATCH] drm/bridge: dw-hdmi-qp: Return -EOPNOTSUPP in HDMI audio functions Detlev Casanova
2026-05-25 12:33 ` Claude Code Review Bot [this message]
2026-05-25 12:33 ` Claude review: " Claude Code Review 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=review-overall-20260519-fix-hdmi-audio-warnings-v1-1-9608966c993f@collabora.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox