From: Simon Kruse <simon0x+git@proton.me>
To: Daniel Scally <dan.scally@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Fernando Rimoli <fernandorimoli11@gmail.com>,
Marco Ziliani <rylos78@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: i2c: ov5693: Use sub-device active state
Date: Wed, 28 Oct 2026 08:30:43 +0000 [thread overview]
Message-ID: <20261028083033.64922-1-simon0x+git@proton.me> (raw)
In-Reply-To: <ff527b5c-b1cb-42a5-9b8d-f039b7a7f7f6@ideasonboard.com>
Hi Dan,
Thanks for the review.
On 27/10/2026 15:49, Dan Scally wrote:
> This patch does quite a lot in one go, it would be better if it could be broken down into a number
> of smaller logical changes. You're removing here the lock from the driver and instead using the
> default one from v4l2_ctrl_handler. That might be a fine idea, but I don't think it's necessary to
> switch the driver to use the subdev active state right? Could it be broken out?
Agreed, it is not needed. v2 keeps the driver mutex and uses it as the
state lock, so ov5693_sensor_resume() stays as it is.
> Why did this function call move to here from ov5693_sensor_init()?
With the 1 s autosuspend delay, pm_runtime_resume_and_get() in
s_stream() skips the resume callback if the sensor is still powered from
the previous stream, so a set_fmt or set_selection made in that window
never reaches the sensor. Marco Ziliani has since posted that fix on
its own, with measurements on several Surface models [1], so v2 drops
it from my patch and is based on his series.
> There's a FIXME in this function that now no longer applies and can be removed.
Will do.
> Descending order of line length please.
Will fix.
[1] https://lore.kernel.org/linux-media/20261027-ov5693-fixes-v1-0-3c8ab1ae104d@gmail.com/
Regards,
Simon
prev parent reply other threads:[~2026-10-28 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 7:50 Simon Kruse
2026-10-27 15:49 ` Dan Scally
2026-10-28 8:30 ` Simon Kruse [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=20261028083033.64922-1-simon0x+git@proton.me \
--to=simon0x+git@proton.me \
--cc=dan.scally@ideasonboard.com \
--cc=fernandorimoli11@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rylos78@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®