From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Ben Hoff <hoff.benjamin.k@gmail.com>, linux-media@vger.kernel.org
Cc: mchehab@kernel.org, hverkuil@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] media: hws: fix shared IRQ and video quiesce handling
Date: Tue, 22 Sep 2026 15:36:12 +0200 [thread overview]
Message-ID: <d9a03faa-3df9-478e-aa73-fa6e7840b3b8@kernel.org> (raw)
In-Reply-To: <20260915010111.101551-1-hoff.benjamin.k@gmail.com>
Hi Ben,
On 15/09/2026 03:01, Ben Hoff wrote:
> HWS quiescence currently disables a shared IRQ descriptor and calls
> vb2_streamoff() without the queue's state mutex. This can prevent other
> devices on the interrupt line from being serviced and race userspace
> capture operations during suspend or shutdown.
>
> Remove diagnostic register accesses first, then restrict IRQ quiescence
> to the HWS function and serialize monitor and queue transitions. Runtime
> readiness checks report an unready core without resetting shared hardware
> while capture buffers may still be owned by another channel.
>
> Based on media-next/next at b38d06ad1e13 ("media: ipu6: Fix up missing
> IWYU issue"). Apply the three patches in order.
>
> AI assistance: OpenAI Codex using GPT-6 assisted with this submission.
> Each patch includes Assisted-by: Codex:GPT-6 to identify the agent and model.
So I'm marking this series as Changes Requested.
It is not so much the code, but the awful AI generated commit messages.
For example. patch 1/3 makes lots of changes, but the commit message doesn't
even say why this is needed. It tells you it keeps code, but obviously
you can't see what that code is in the patch because it is, well, kept :-)
To me this patch just looks like a big cleanup patch, ditching old debug
code that is no longer needed. Which sounds like a perfectly find commit
log message.
I suggest deleting the commit messages and rewriting them yourself in
words that a human would use ('serialize video quiesce with queue state':
really? What the heck does that even mean?)
Remember that AI can be very useful, but in the end it is a human (i.e.
me) that has to review it.
Regards,
Hans
>
> Validation:
> - Applied and built every patch boundary as an external module with W=1
> against the prepared x86_64 kernel, with CONFIG_PM_SLEEP=y.
> - Strict checkpatch and git diff --check pass.
> - Hardware capture and system-sleep tests have not been run for this
> extracted series.
>
> Ben Hoff (3):
> media: hws: remove debug controls and lifecycle tracing
> media: hws: quiesce interrupts without disabling shared IRQ
> media: hws: serialize video quiesce with queue state
>
> drivers/media/pci/hws/hws.h | 2 +
> drivers/media/pci/hws/hws_irq.c | 84 +-----------
> drivers/media/pci/hws/hws_pci.c | 181 ++++---------------------
> drivers/media/pci/hws/hws_v4l2_ioctl.c | 14 --
> drivers/media/pci/hws/hws_video.c | 144 ++------------------
> 5 files changed, 44 insertions(+), 381 deletions(-)
>
>
> base-commit: b38d06ad1e13c32970d58039c154f009b81a3368
>
prev parent reply other threads:[~2026-09-22 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 1:01 [PATCH 0/3] media: hws: fix shared IRQ and video quiesce handling Ben Hoff
2026-09-15 1:01 ` [PATCH 1/3] media: hws: remove debug controls and lifecycle tracing Ben Hoff
2026-09-15 1:01 ` [PATCH 2/3] media: hws: quiesce interrupts without disabling shared IRQ Ben Hoff
2026-09-15 1:01 ` [PATCH 3/3] media: hws: serialize video quiesce with queue state Ben Hoff
2026-09-22 13:36 ` Hans Verkuil [this message]
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=d9a03faa-3df9-478e-aa73-fa6e7840b3b8@kernel.org \
--to=hverkuil+cisco@kernel.org \
--cc=hoff.benjamin.k@gmail.com \
--cc=hverkuil@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.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