From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: tin.posavec04@gmail.com
Cc: Bingbu Cao <bingbu.cao@amd.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Dan Scally <dan.scally@ideasonboard.com>,
Hans de Goede <hansg@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] media: i2c: ov9734: Add power on/off sequencing support
Date: Mon, 9 Nov 2026 14:28:22 +0200 [thread overview]
Message-ID: <avG8ZgDPVWCr1pja@kekkonen.localdomain> (raw)
In-Reply-To: <20261017-ov9734-ipu6-v1-2-86eab22ae258@gmail.com>
Hi Tin,
On Sat, Oct 17, 2026 at 10:31:58AM +0200, Tin Posavec via B4 Relay wrote:
> From: Tin Posavec <tin.posavec04@gmail.com>
>
> So far the driver has relied on ACPI to power the sensor on and off. On
> the Intel NUC M15 (LAPRC710), however, the sensor's ACPI device has
> neither _PS0 nor _PR0. Its avdd supply and clock are provided by an
> INT3472 discrete device instead, and as the driver does not enable
> them, reading the chip ID in probe fails with -EREMOTEIO.
>
> Get the dovdd, avdd and dvdd supplies and the optional reset and
> powerdown GPIOs, and power the sensor on and off in the runtime PM
> callbacks. Also power it on in probe before identifying it, and off on
> probe errors and in remove() if it is still powered on. The 2 ms reset
> assertion time and the 20 ms start-up delay are taken from ov01a10.
>
> Move pm_runtime_idle() after the sub-device registration, so that the
> sensor is not powered off twice if the registration fails, and drop the
> comment saying that the I2C core has already powered the device on.
>
> Assisted-by: LLM
> Signed-off-by: Tin Posavec <tin.posavec04@gmail.com>
> ---
> drivers/media/i2c/ov9734.c | 125 ++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 118 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/media/i2c/ov9734.c b/drivers/media/i2c/ov9734.c
> index f9280ef0e..feb15de2c 100644
> --- a/drivers/media/i2c/ov9734.c
> +++ b/drivers/media/i2c/ov9734.c
> @@ -4,9 +4,12 @@
> #include <linux/acpi.h>
> #include <linux/clk.h>
> #include <linux/delay.h>
> +#include <linux/gpio/consumer.h>
> #include <linux/i2c.h>
> #include <linux/module.h>
> #include <linux/pm_runtime.h>
> +#include <linux/regulator/consumer.h>
> +#include <linux/time.h>
> #include <linux/unaligned.h>
>
> #include <media/v4l2-ctrls.h>
> @@ -322,9 +325,18 @@ static const struct ov9734_mode supported_modes[] = {
> },
> };
>
> +static const char * const ov9734_supply_names[] = {
> + "dovdd", /* Digital I/O power */
> + "avdd", /* Analog power */
> + "dvdd", /* Digital core power */
> +};
> +
> struct ov9734 {
> struct device *dev;
> struct clk *clk;
> + struct gpio_desc *reset;
> + struct gpio_desc *powerdown;
> + struct regulator_bulk_data supplies[ARRAY_SIZE(ov9734_supply_names)];
>
> struct v4l2_subdev sd;
> struct media_pad pad;
> @@ -878,6 +890,88 @@ static int ov9734_check_hwcfg(struct device *dev)
> return ret;
> }
>
> +static int ov9734_get_pm_resources(struct ov9734 *ov9734)
> +{
> + int ret;
> +
> + ov9734->reset = devm_gpiod_get_optional(ov9734->dev, "reset",
> + GPIOD_OUT_HIGH);
> + if (IS_ERR(ov9734->reset))
> + return dev_err_probe(ov9734->dev, PTR_ERR(ov9734->reset),
> + "failed to get reset gpio\n");
> +
> + ov9734->powerdown = devm_gpiod_get_optional(ov9734->dev, "powerdown",
> + GPIOD_OUT_HIGH);
> + if (IS_ERR(ov9734->powerdown))
> + return dev_err_probe(ov9734->dev, PTR_ERR(ov9734->powerdown),
> + "failed to get powerdown gpio\n");
> +
> + for (unsigned int i = 0; i < ARRAY_SIZE(ov9734_supply_names); i++)
> + ov9734->supplies[i].supply = ov9734_supply_names[i];
> +
> + ret = devm_regulator_bulk_get(ov9734->dev,
> + ARRAY_SIZE(ov9734_supply_names),
> + ov9734->supplies);
> + if (ret)
> + return dev_err_probe(ov9734->dev, ret,
> + "failed to get regulators\n");
> +
> + return 0;
> +}
> +
> +static int ov9734_power_on(struct device *dev)
> +{
> + struct v4l2_subdev *sd = dev_get_drvdata(dev);
> + struct ov9734 *ov9734 = to_ov9734(sd);
> + int ret;
> +
> + ret = regulator_bulk_enable(ARRAY_SIZE(ov9734_supply_names),
> + ov9734->supplies);
> + if (ret) {
> + dev_err(dev, "failed to enable regulators: %d\n", ret);
> + return ret;
> + }
> +
> + ret = clk_prepare_enable(ov9734->clk);
> + if (ret) {
> + dev_err(dev, "failed to enable clock: %d\n", ret);
> + regulator_bulk_disable(ARRAY_SIZE(ov9734_supply_names),
> + ov9734->supplies);
> + return ret;
> + }
> +
> + if (ov9734->reset || ov9734->powerdown) {
> + /*
> + * Keep reset/powerdown asserted for at least 2 ms on a
> + * back-to-back off-on cycle.
> + */
The comment isn't useful. Please drop it.
> + fsleep(2 * USEC_PER_MSEC);
> + gpiod_set_value_cansleep(ov9734->powerdown, 0);
> + gpiod_set_value_cansleep(ov9734->reset, 0);
The sensor appears to need a single GPIO (xshutdown). I wonder what's the
other one.
> + }
> +
> + /* Give the sensor time to start up before accessing it */
Ditto.
> + fsleep(20 * USEC_PER_MSEC);
8192 external clock cycles are required for this.
> +
> + return 0;
> +}
> +
> +static int ov9734_power_off(struct device *dev)
> +{
> + struct v4l2_subdev *sd = dev_get_drvdata(dev);
> + struct ov9734 *ov9734 = to_ov9734(sd);
> +
> + gpiod_set_value_cansleep(ov9734->reset, 1);
> + gpiod_set_value_cansleep(ov9734->powerdown, 1);
> +
> + clk_disable_unprepare(ov9734->clk);
> +
> + regulator_bulk_disable(ARRAY_SIZE(ov9734_supply_names),
> + ov9734->supplies);
> +
> + return 0;
> +}
> +
> static void ov9734_remove(struct i2c_client *client)
> {
> struct v4l2_subdev *sd = i2c_get_clientdata(client);
> @@ -887,7 +981,10 @@ static void ov9734_remove(struct i2c_client *client)
> media_entity_cleanup(&sd->entity);
> v4l2_ctrl_handler_free(sd->ctrl_handler);
> pm_runtime_disable(ov9734->dev);
> - pm_runtime_set_suspended(ov9734->dev);
> + if (!pm_runtime_status_suspended(ov9734->dev)) {
> + ov9734_power_off(ov9734->dev);
> + pm_runtime_set_suspended(ov9734->dev);
> + }
> mutex_destroy(&ov9734->mutex);
> }
>
> @@ -918,11 +1015,20 @@ static int ov9734_probe(struct i2c_client *client)
> "external clock %lu is not supported",
> freq);
>
> + ret = ov9734_get_pm_resources(ov9734);
> + if (ret)
> + return ret;
> +
> v4l2_i2c_subdev_init(&ov9734->sd, client, &ov9734_subdev_ops);
> +
> + ret = ov9734_power_on(ov9734->dev);
> + if (ret)
> + return ret;
> +
> ret = ov9734_identify_module(ov9734);
> if (ret) {
> dev_err(ov9734->dev, "failed to find sensor: %d", ret);
> - return ret;
> + goto probe_error_power_off;
> }
>
> mutex_init(&ov9734->mutex);
> @@ -944,13 +1050,8 @@ static int ov9734_probe(struct i2c_client *client)
> goto probe_error_v4l2_ctrl_handler_free;
> }
>
> - /*
> - * Device is already turned on by i2c-core with ACPI domain PM.
> - * Enable runtime PM and turn off the device.
> - */
> pm_runtime_set_active(ov9734->dev);
> pm_runtime_enable(ov9734->dev);
> - pm_runtime_idle(ov9734->dev);
>
> ret = v4l2_async_register_subdev_sensor(&ov9734->sd);
> if (ret < 0) {
> @@ -959,6 +1060,8 @@ static int ov9734_probe(struct i2c_client *client)
> goto probe_error_media_entity_cleanup_pm;
> }
>
> + pm_runtime_idle(ov9734->dev);
> +
> return 0;
>
> probe_error_media_entity_cleanup_pm:
> @@ -970,9 +1073,16 @@ static int ov9734_probe(struct i2c_client *client)
> v4l2_ctrl_handler_free(ov9734->sd.ctrl_handler);
> mutex_destroy(&ov9734->mutex);
>
> +probe_error_power_off:
> + ov9734_power_off(ov9734->dev);
> +
> return ret;
> }
>
> +static const struct dev_pm_ops ov9734_pm_ops = {
> + RUNTIME_PM_OPS(ov9734_power_off, ov9734_power_on, NULL)
> +};
> +
> static const struct acpi_device_id ov9734_acpi_ids[] = {
> { "OVTI9734", },
> {}
> @@ -983,6 +1093,7 @@ MODULE_DEVICE_TABLE(acpi, ov9734_acpi_ids);
> static struct i2c_driver ov9734_i2c_driver = {
> .driver = {
> .name = "ov9734",
> + .pm = pm_ptr(&ov9734_pm_ops),
> .acpi_match_table = ov9734_acpi_ids,
> },
> .probe = ov9734_probe,
>
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-11-09 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 8:31 [PATCH 0/3] media: ov9734, ipu-bridge: Enable the camera on the Intel NUC M15 Tin Posavec via B4 Relay
2026-10-17 8:31 ` [PATCH 1/3] media: i2c: ov9734: Return -EPROBE_DEFER if no endpoint is found Tin Posavec via B4 Relay
2026-11-09 11:58 ` Sakari Ailus
2026-10-17 8:31 ` [PATCH 2/3] media: i2c: ov9734: Add power on/off sequencing support Tin Posavec via B4 Relay
2026-11-09 12:28 ` Sakari Ailus [this message]
2026-10-17 8:31 ` [PATCH 3/3] media: ipu-bridge: Add OV9734 sensor config Tin Posavec via B4 Relay
2026-11-06 21:33 ` [PATCH 0/3] media: ov9734, ipu-bridge: Enable the camera on the Intel NUC M15 Afonso Figuinha
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=avG8ZgDPVWCr1pja@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=bingbu.cao@amd.com \
--cc=dan.scally@ideasonboard.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tin.posavec04@gmail.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®