From: Arun T <arun.t@intel.com>
To: arun.t@intel.com
Cc: sakari.ailus@iki.fi, sakari.ailus@intel.com,
sakari.ailus@linux.intel.com, arec.kao@intel.com,
ilpo.jarvinen@linux.intel.com, dan.scally@ideasonboard.com,
platform-driver-x86@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, mehdi.djait@intel.com
Subject: [PATCH v3 0/2] Add TPS68470 power supply support for ov13b10 sensor
Date: Mon, 2 Mar 2026 23:16:42 +0530 [thread overview]
Message-ID: <20260302174644.1258718-1-arun.t@intel.com> (raw)
In-Reply-To: <20260130092431.2335363-2-arun.t@intel.com>
This patch series adds power supply management support for the OV13B10 camera sensor when used with TPS68470 PMIC, commonly used on Intel-based camera platforms.
The OV13B10 sensor requires three power supplies (DOVDD, AVDD, DVDD) which are provided by the TPS68470 PMIC.
This series implements proper regulator framework integration to manage these power supplies during sensor power on/off sequences.
Changes in v3:
- Fixed check patch errors as updated by sakari
- Enabled VCM regulator for ov13b10 sensor to enable autofocus to work
Suggested by Sakari:
- Add include header file in alphabetical order
- Remove extra space
- Asked to check vcm instance
Changes in v2:
- Added power supply names array for the three required regulators
- Implement regulator handling with devm_regulator_bulk_get()
- Add regulator_bulk_enable() and regulator_bulk_disable() for sensor power on/off sequence
Suggested by Hans:
- Add multiple regulators you should use the bulk regulator API
- Use use "reset" instead of "s_resetn" for parse gpio name.
- Add diffent regulator power supplies in single array
Arun T (2):
platform/x86: int3472: Add TPS68470 board data for Intel nvl
media: i2c: ov13b10: support tps68470 regulator and gpio
drivers/media/i2c/ov13b10.c | 48 +++---
.../x86/intel/int3472/tps68470_board_data.c | 150 ++++++++++++++++++
2 files changed, 177 insertions(+), 21 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2026-03-02 17:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 9:24 [PATCH 1/2] platform/x86: int3472: Add board data for Intel nvl Arun T
2026-01-30 9:24 ` [PATCH 2/2] media: i2c: ov13b10: Support tps68470 regulator and gpio Arun T
2026-02-02 15:11 ` johannes.goede
2026-02-17 6:11 ` T, Arun
2026-02-24 18:21 ` T, Arun
2026-02-11 15:39 ` [PATCH 1/2] platform/x86: int3472: Add board data for Intel nvl Arun T
2026-02-11 15:39 ` [PATCH 2/2] media: i2c: ov13b10: Support tps68470 regulator and gpio Arun T
2026-02-11 16:16 ` [PATCH 1/2] platform/x86: int3472: Add board data for Intel nvl Arun T
2026-02-11 16:16 ` [PATCH 2/2] media: i2c: ov13b10: Support tps68470 regulator and gpio Arun T
2026-02-26 1:12 ` [PATCH 1/2] platform/x86: int3472: Add board data for Intel nvl Arun T
2026-02-26 1:12 ` [PATCH 2/2] media: i2c: ov13b10: Support tps68470 regulator and gpio Arun T
2026-02-26 11:15 ` [PATCH 1/2] platform/x86: int3472: Add board data for Intel nvl Kieran Bingham
2026-02-27 13:35 ` [PATCH v2 0/2] Add TPS68470 power supply support for ov13b10 sensor Arun T
2026-02-27 13:35 ` [PATCH v2 1/2] platform/x86: int3472: Add board data for Intel nvl Arun T
2026-03-01 14:37 ` Sakari Ailus
2026-03-04 9:29 ` johannes.goede
2026-03-06 8:47 ` T, Arun
2026-03-06 9:22 ` johannes.goede
2026-03-12 9:46 ` T, Arun
2026-03-16 17:57 ` T, Arun
2026-02-27 13:35 ` [PATCH v2 2/2] media: i2c: ov13b10: Support tps68470 regulator and gpio Arun T
2026-03-01 14:40 ` Sakari Ailus
2026-03-02 17:46 ` Arun T [this message]
2026-03-02 17:46 ` [PATCH v3 1/2] platform/x86: int3472: Add TPS68470 board data for Intel nvl Arun T
2026-03-04 9:32 ` johannes.goede
2026-03-02 17:46 ` [PATCH v3 2/2] media: i2c: ov13b10: support tps68470 regulator and gpio Arun T
2026-02-02 15:10 ` [PATCH 1/2] platform/x86: int3472: Add board data for Intel nvl johannes.goede
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=20260302174644.1258718-1-arun.t@intel.com \
--to=arun.t@intel.com \
--cc=arec.kao@intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mehdi.djait@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@intel.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
Powered by JetHome