From: Ruslan Koreev <koreev.r@gmail.com>
To: Fernando Rimoli <fernandorimoli11@gmail.com>,
"D. Manresa" <dmanresa@gmail.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Dan Scally <dan.scally@ideasonboard.com>,
Hans de Goede <hansg@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rillian Grant <rillian.grant@gmail.com>,
Sergey Lebedev <lsa.uz@pm.me>,
linux-media@vger.kernel.org
Subject: Re: media: ipu-bridge: lifetime of retained software-node properties
Date: Tue, 27 Oct 2026 17:30:23 +0300 [thread overview]
Message-ID: <20261027143023.3312353-1-koreev.r@gmail.com> (raw)
In-Reply-To: <179303518584.774397.17279190841735842653@gmail.com>
Hi Fernando, Dario,
I've incorporated v5 1/2 into the local flash integration.
With both v5 patches, QEMU tests passed 16 PCI remove/rescan cycles per
run, eight including bridge unload/reload, for both the original bridge
and our integration. Frequencies and lens references remained readable
while the bridge was unloaded. No KASAN or lockdep reports.
A synthetic X1 configuration also preserved the IR flash reference, LED
string property and limits through the same lifecycle tests.
Agreed on vcm_type: it is currently init-only, and I'd keep that cleanup
separate.
Could you confirm that capture works again on each previously working
sensor after module reload and repeated PCI remove/rescan with the full
v5 series? If you've already covered this, those results would be useful.
Regards,
Ruslan
next prev parent reply other threads:[~2026-10-27 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 9:12 media: ipu-bridge: lifetime of retained software-node properties Ruslan Koreev
2026-10-26 11:11 ` Fernando Rimoli
2026-10-26 17:19 ` D. Manresa
2026-10-27 14:30 ` Ruslan Koreev [this message]
2026-10-27 19:21 ` D. Manresa
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=20261027143023.3312353-1-koreev.r@gmail.com \
--to=koreev.r@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=dmanresa@gmail.com \
--cc=fernandorimoli11@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lsa.uz@pm.me \
--cc=rillian.grant@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.