From: Dipayaan Roy <dipayaan.roy@oss.qualcomm.com>
To: linux-media@vger.kernel.org
Cc: vikash.garodia@oss.qualcomm.com,
dikshita.agarwal@oss.qualcomm.com, abhinav.kumar@linux.dev,
bod@kernel.org, mchehab@kernel.org, p.zabel@pengutronix.de,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] media: qcom: iris: improve error diagnostics
Date: Fri, 6 Nov 2026 15:31:22 +0000 [thread overview]
Message-ID: <20261106153126.120858-1-dipayaan.roy@oss.qualcomm.com> (raw)
The Iris driver can return probe errors or enter error states without
logging enough context to identify the failed operation or firmware
response. This makes failures difficult to diagnose from kernel logs.
Improve probe error reporting, include available return codes and status
values in existing messages, and add focused diagnostics for system and
session failures. Report recovery failures and provide debug-level
messages for successful recovery and less actionable events.
Dipayaan Roy (3):
media: qcom: iris: improve probe error reporting
media: qcom: iris: add error and status details to diagnostics
media: qcom: iris: Improve diagnostics for system and session failures
drivers/media/platform/qcom/iris/iris_core.c | 2 +
.../platform/qcom/iris/iris_hfi_common.c | 4 +-
.../qcom/iris/iris_hfi_gen1_response.c | 16 +++-
.../qcom/iris/iris_hfi_gen2_response.c | 15 ++-
.../media/platform/qcom/iris/iris_hfi_queue.c | 12 ++-
drivers/media/platform/qcom/iris/iris_probe.c | 95 ++++++++++++++-----
drivers/media/platform/qcom/iris/iris_state.c | 5 +-
drivers/media/platform/qcom/iris/iris_utils.c | 2 +
drivers/media/platform/qcom/iris/iris_vb2.c | 2 +-
drivers/media/platform/qcom/iris/iris_vdec.c | 3 +-
drivers/media/platform/qcom/iris/iris_venc.c | 3 +-
drivers/media/platform/qcom/iris/iris_vidc.c | 2 +-
drivers/media/platform/qcom/iris/iris_vpu3x.c | 19 ++--
drivers/media/platform/qcom/iris/iris_vpu4x.c | 4 +-
.../platform/qcom/iris/iris_vpu_common.c | 15 +--
15 files changed, 141 insertions(+), 58 deletions(-)
--
2.43.0
next reply other threads:[~2026-11-06 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 15:31 Dipayaan Roy [this message]
2026-11-06 15:31 ` [PATCH 1/3] media: qcom: iris: improve probe error reporting Dipayaan Roy
2026-11-09 7:17 ` Vishnu Reddy
2026-11-06 15:31 ` [PATCH 2/3] media: qcom: iris: add error and status details to diagnostics Dipayaan Roy
2026-11-09 7:25 ` Vishnu Reddy
2026-11-06 15:31 ` [PATCH 3/3] media: qcom: iris: Improve diagnostics for system and session failures Dipayaan Roy
2026-11-09 7:53 ` Vishnu Reddy
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=20261106153126.120858-1-dipayaan.roy@oss.qualcomm.com \
--to=dipayaan.roy@oss.qualcomm.com \
--cc=abhinav.kumar@linux.dev \
--cc=bod@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=vikash.garodia@oss.qualcomm.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
all inboxes | Powered by JetHome®