From: sashiko-bot@kernel.org
To: "Ramshouriesh R" <rshouriesh@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v5 2/2] media: i2c: hm1092: add Himax HM1092 mono NIR sensor driver
Date: Thu, 09 Jul 2026 08:22:38 +0000 [thread overview]
Message-ID: <20260709082238.AF2261F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260709-hm1092-driver-v5-2-a1f5baa6fe08@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Unnecessary device power-on sequence in probe() introduces a ~22ms boot delay per camera with no functional benefit.
--
--- Patch [2]: [PATCH v5 2/2] media: i2c: hm1092: add Himax HM1092 mono NIR sensor driver ---
commit 4abd5da551efe32eec434d2e88b53c45de5fc3dc
Author: Ramshouriesh R <rshouriesh@gmail.com>
media: i2c: hm1092: add Himax HM1092 mono NIR sensor driver
Add a V4L2 subdev driver for the Himax HM1092 monochrome near-infrared
image sensor. The driver supports the sensor's native 560x360 10-bit mono
mode, test patterns, and standard fwnode properties.
> diff --git a/drivers/media/i2c/hm1092.c b/drivers/media/i2c/hm1092.c
> new file mode 100644
> index 0000000000000..c7cde6928bb91
> --- /dev/null
> +++ b/drivers/media/i2c/hm1092.c
[ ... ]
> +static int hm1092_probe(struct i2c_client *client)
> +{
> + struct hm1092 *hm1092;
> + unsigned long freq;
> + int ret;
[ ... ]
> + hm1092->regmap = devm_cci_regmap_init_i2c(client, 16);
> + if (IS_ERR(hm1092->regmap))
> + return PTR_ERR(hm1092->regmap);
> +
> + ret = hm1092_power_on(hm1092->dev);
> + if (ret)
> + return dev_err_probe(hm1092->dev, ret, "failed to power on\n");
[Severity: Medium]
Does this driver need to power on the sensor during probe?
Looking at hm1092_power_on(), the sequence introduces ~22ms of sleep delays
to bring up regulators and clocks. However, there doesn't appear to be any
I2C communication (such as reading a hardware ID register to verify the chip
is present) that follows in the hm1092_probe() function.
Since the device is just powered on and then immediately idled and suspended
shortly after via pm_runtime_idle(), could this power-on step be deferred
entirely to runtime PM or streaming initialization to avoid the boot delay?
> +
> + ret = hm1092_init_controls(hm1092);
> + if (ret)
> + goto err_power_off;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260709-hm1092-driver-v5-0-a1f5baa6fe08@gmail.com?part=2
prev parent reply other threads:[~2026-07-09 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 8:11 [PATCH v5 0/2] media: Add Himax HM1092 mono NIR sensor driver Ramshouriesh R
2026-07-09 8:11 ` [PATCH v5 1/2] media: dt-bindings: Add Himax HM1092 NIR sensor Ramshouriesh R
2026-07-09 8:18 ` sashiko-bot
2026-07-09 8:11 ` [PATCH v5 2/2] media: i2c: hm1092: add Himax HM1092 mono NIR sensor driver Ramshouriesh R
2026-07-09 8:22 ` sashiko-bot [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=20260709082238.AF2261F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rshouriesh@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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