From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Ben Hoff <hoff.benjamin.k@gmail.com>, linux-media@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, mchehab@kernel.org,
hverkuil@kernel.org, lukas.bulwahn@redhat.com
Subject: Re: [RFC PATCH v1 0/2] media: pci: AVMatrix HWS capture driver refresh
Date: Mon, 3 Nov 2025 15:57:31 +0100 [thread overview]
Message-ID: <b38c4013-fabb-4469-bfa9-9296a88d244a@kernel.org> (raw)
In-Reply-To: <20251027195638.481129-1-hoff.benjamin.k@gmail.com>
Hi Ben,
Thank you for working on this!
On 27/10/2025 20:56, Ben Hoff wrote:
> Hi all,
>
> This RFC series significantly refactors the downstream AVMatrix HWS PCIe
> capture driver so it is maintainable in-tree and aligns with upstream
> media driver expectations. The new implementation follows V4L2 and ALSA
> subsystem patterns, splits the hardware plumbing across focused source
> files, and introduces proper runtime PM and interrupt handling. The goal
> is to keep future maintenance manageable while providing a direct path for
> existing users of the vendor tree.
>
> Current status / open items:
> - Audio capture paths have been refactored from the vendor driver but have
> not yet been validated on real hardware. I would appreciate guidance
> on whether you would prefer that I drop the ALSA pieces from the
> initial submission and stage them as a follow-up once I finish
> validation.
> - `v4l2-compliance` passes for each video node, and I have exercised
> basic capture in OBS. I still plan to do heavier soak testing across
> all inputs and audio channels, as well as cover the suspend/resume
> paths.
>
> Any feedback on the overall structure, subsystem integration, and in
> particular the best way to stage the audio support would be very welcome.
I think you have two options:
1) wait until you finish the audio validation, or
2) make this a staging driver (drivers/staging/media), add the audio part
later and then move it to drivers/media/pci.
Regarding this driver: I gather that this is a rework of a GPL out-of-tree
driver? Can you should at least add a URL that driver? That should definitely
be part of the commit log of the driver.
Is the vendor involved in this upstream driver work? Or you just took their
code and made it suitable for mainlining? Just curious.
Finally, for the next v1 please include the v4l2-compliance output in the
cover letter. And make sure you compile v4l2-compliance from the v4l-utils
git repo so you are using the latest and greatest version.
Regards,
Hans
> Once I hear back on the preferred direction I will respin this as a
> formal v1 submission.
>
> Thanks for taking a look!
>
> Ben
>
> Ben Hoff (2):
> media: pci: add AVMatrix HWS capture driver
> MAINTAINERS: add entry for AVMatrix HWS driver
>
> MAINTAINERS | 6 +
> drivers/media/pci/Kconfig | 1 +
> drivers/media/pci/Makefile | 1 +
> drivers/media/pci/hws/Kconfig | 13 +
> drivers/media/pci/hws/Makefile | 4 +
> drivers/media/pci/hws/hws.h | 194 +++
> drivers/media/pci/hws/hws_audio.c | 571 +++++++++
> drivers/media/pci/hws/hws_audio.h | 22 +
> drivers/media/pci/hws/hws_irq.c | 281 +++++
> drivers/media/pci/hws/hws_irq.h | 12 +
> drivers/media/pci/hws/hws_pci.c | 708 +++++++++++
> drivers/media/pci/hws/hws_reg.h | 142 +++
> drivers/media/pci/hws/hws_v4l2_ioctl.c | 576 +++++++++
> drivers/media/pci/hws/hws_v4l2_ioctl.h | 32 +
> drivers/media/pci/hws/hws_video.c | 1542 ++++++++++++++++++++++++
> drivers/media/pci/hws/hws_video.h | 24 +
> 16 files changed, 4129 insertions(+)
> create mode 100644 drivers/media/pci/hws/Kconfig
> create mode 100644 drivers/media/pci/hws/Makefile
> create mode 100644 drivers/media/pci/hws/hws.h
> create mode 100644 drivers/media/pci/hws/hws_audio.c
> create mode 100644 drivers/media/pci/hws/hws_audio.h
> create mode 100644 drivers/media/pci/hws/hws_irq.c
> create mode 100644 drivers/media/pci/hws/hws_irq.h
> create mode 100644 drivers/media/pci/hws/hws_pci.c
> create mode 100644 drivers/media/pci/hws/hws_reg.h
> create mode 100644 drivers/media/pci/hws/hws_v4l2_ioctl.c
> create mode 100644 drivers/media/pci/hws/hws_v4l2_ioctl.h
> create mode 100644 drivers/media/pci/hws/hws_video.c
> create mode 100644 drivers/media/pci/hws/hws_video.h
>
next prev parent reply other threads:[~2025-11-03 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 19:56 Ben Hoff
2025-10-27 19:56 ` [RFC PATCH v1 1/2] media: pci: add AVMatrix HWS capture driver Ben Hoff
2025-11-03 14:46 ` Hans Verkuil
2025-10-27 19:56 ` [RFC PATCH v1 2/2] MAINTAINERS: add entry for AVMatrix HWS driver Ben Hoff
2025-11-03 14:48 ` Hans Verkuil
2025-11-03 14:57 ` Hans Verkuil [this message]
2025-11-21 9:32 ` [RFC PATCH v1 0/2] media: pci: AVMatrix HWS capture driver refresh Ben Hoff
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=b38c4013-fabb-4469-bfa9-9296a88d244a@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=lukas.bulwahn@redhat.com \
--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
Powered by JetHome