From: "luo.liu.linux" <luo.liu.linux@163.com>
To: "Sakari Ailus" <sakari.ailus@linux.intel.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 19:21:42 +0800 (CST) [thread overview]
Message-ID: <5e63e8aa.943f.19ce6ee4ad5.Coremail.luo.liu.linux@163.com> (raw)
In-Reply-To: <abPm3VGGRAIsY1eQ@kekkonen.localdomain>
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.
Specifically, taking a sensor as an example of a subdev:
Registration Verification: Upon successfully loading the driver using insmod xxx_sensor.ko,
the corresponding sensor subdev should appear in the subdev_list.
Unregistration Verification: Upon successfully unloading the driver using rmmod xxx_sensor.ko,
the corresponding subdev entry should be removed from the subdev_list.
The following test log in my board:
root@cix-localhost:~/upload# cat /sys/kernel/debug/v4l2-async/registered_subdevices
root@cix-localhost:~/upload#
root@cix-localhost:~/upload# insmod lt7911uxc.ko
root@cix-localhost:~/upload#
root@cix-localhost:~/upload# cat /sys/kernel/debug/v4l2-async/registered_subdevices
LT7911UXC 0-0043 (dev: 0-0043)
root@cix-localhost:~/upload#
root@cix-localhost:~/upload# rmmod lt7911uxc.ko
root@cix-localhost:~/upload#
root@cix-localhost:~/upload# cat /sys/kernel/debug/v4l2-async/registered_subdevices
root@cix-localhost:~/upload#
root@cix-localhost:~/upload#
Regards,
Luo Liu
At 2026-03-13 18:28:45, "Sakari Ailus" <sakari.ailus@linux.intel.com> wrote:
>Hi Luo,
>
>On Fri, Mar 13, 2026 at 03:58:24PM +0800, luo.liu wrote:
>> Add a new debugfs file "registered_subdevices" under the "v4l2-async"
>> directory to display all registered subdevices in the subdev_list. This
>> helps with debugging by providing a clear view of all currently registered
>> V4L2 subdevices.
>
>Could you elaborate a little how has providing this information over
>debugfs helped you?
>
>--
>Regards,
>
>Sakari Ailus
next prev parent reply other threads:[~2026-03-13 11:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 7:58 luo.liu
2026-03-13 10:28 ` Sakari Ailus
2026-03-13 11:21 ` luo.liu.linux [this message]
2026-03-13 11:42 ` Sakari Ailus
2026-03-13 13:50 ` 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=5e63e8aa.943f.19ce6ee4ad5.Coremail.luo.liu.linux@163.com \
--to=luo.liu.linux@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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
Powered by JetHome