From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "luo.liu.linux" <luo.liu.linux@163.com>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] media:v4l2-async:debugfs for registered subdevices
Date: Fri, 13 Mar 2026 13:42:42 +0200 [thread overview]
Message-ID: <abP4Mr_s8JRpQH0B@kekkonen.localdomain> (raw)
In-Reply-To: <5e63e8aa.943f.19ce6ee4ad5.Coremail.luo.liu.linux@163.com>
Hi Luo,
On Fri, Mar 13, 2026 at 07:21:42PM +0800, luo.liu.linux wrote:
>
> Hi Sakari，
>
> Thank you very much for your reply.
>
> When building a pipeline in the camera subsystem via Media Entities
>
> (e.g., Sensor -> DPHY -> MIPI-CSI2 -> ISP), it is crucial to verify that the registration
>
> and unregistration processes for each sub-device (subdev) driver within the pipeline
>
> are functioning correctly.
You don't need a debugfs interface for that, do you? We have a large number
of things that can go wrong that are much more complicated than this (and
there's no debugfs interface to verify those either, no, largely because it
wouldn't be meaningful).
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-03-13 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 7:58 [PATCH] media:v4l2-async:debugfs for registered subdevices luo.liu
2026-03-13 10:28 ` Sakari Ailus
2026-03-13 11:21 ` luo.liu.linux
2026-03-13 11:42 ` Sakari Ailus [this message]
2026-03-13 13:50 ` Re:Re: " luo.liu.linux
2026-03-16 16:48 ` Sakari Ailus
2026-03-17 3:37 ` luo.liu.linux
2026-03-17 8:21 ` Sakari Ailus
2026-03-17 11:14 ` luo.liu.linux
2026-03-19 20:30 ` Laurent Pinchart
2026-03-20 6:52 ` luo.liu.linux
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=abP4Mr_s8JRpQH0B@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luo.liu.linux@163.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