mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: johannes.goede@oss.qualcomm.com
To: Arun T <arun.t@intel.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] platform/x86: int3472: Add board data for Intel nvl
Date: Mon, 2 Feb 2026 16:10:35 +0100	[thread overview]
Message-ID: <f44ec888-a2b1-4ade-b4ad-1cc3ff82903a@oss.qualcomm.com> (raw)
In-Reply-To: <20260130092431.2335363-1-arun.t@intel.com>

Hi Arun,

Thank you for your patch.

On 30-Jan-26 10:24, Arun T wrote:
> The Intel Nvl O13b10 sensor with the Intel IPU8 ISP.
> The sensor is powered by a TPS68470 PMIC, and so we
> need some board data to describe how to configure the GPIOs and
> regulators to run the sensor.
> 
> Signed-off-by: Arun T <arun.t@intel.com>
> ---
>  .../x86/intel/int3472/tps68470_board_data.c   | 150 ++++++++++++++++++
>  1 file changed, 150 insertions(+)
> 
> diff --git a/drivers/platform/x86/intel/int3472/tps68470_board_data.c b/drivers/platform/x86/intel/int3472/tps68470_board_data.c
> index 71357a036292..7820ff811df8 100644
> --- a/drivers/platform/x86/intel/int3472/tps68470_board_data.c
> +++ b/drivers/platform/x86/intel/int3472/tps68470_board_data.c
> @@ -143,6 +143,34 @@ static struct regulator_consumer_supply int3479_aux2_consumer_supplies[] = {
>  	REGULATOR_SUPPLY("dovdd", "i2c-INT3479:00"),
>  };
>  
> +/* Settings for Intel NVL platform */
> +
> +static struct regulator_consumer_supply int347_ov13b_core_consumer_supplies[] = {
> +	REGULATOR_SUPPLY("dvdd", "i2c-OVTI13B1:00"),
> +};
> +
> +static struct regulator_consumer_supply int347_ov13b_ana_consumer_supplies[] = {
> +	REGULATOR_SUPPLY("ana", "i2c-OVTI13B1:00"),
> +};
> +
> +static struct regulator_consumer_supply int347_ov13b_vcm_consumer_supplies[] = {
> +	REGULATOR_SUPPLY("vdd", "i2c-OVTI13B1:00"),
> +};
> +
> +static struct regulator_consumer_supply int347_ov13b_vsio_consumer_supplies[] = {
> +	REGULATOR_SUPPLY("dovdd", "i2c-OVTI13B1:00"),
> +	REGULATOR_SUPPLY("vsio", "i2c-OVTI13B1:00"),
> +	REGULATOR_SUPPLY("vddd", "i2c-OVTI13B1:00"),
> +};
> +
> +static struct regulator_consumer_supply int347_ov13b_aux1_consumer_supplies[] = {
> +	REGULATOR_SUPPLY("vdda", "i2c-OVTI13B1:00"),
> +};
> +
> +static struct regulator_consumer_supply int347_ov13b_aux2_consumer_supplies[] = {
> +	REGULATOR_SUPPLY("vdddo", "i2c-OVTI13B1:00"),
> +};
> +

You're defining many regulator supplies here, but in your ov13b10
patch you only consume:

        "avdd",         /* Analog power */
        "dovdd",        /* Digital I/O power */
        "dvdd",         /* Digital core power */

So you should only define those as supplies here.

Regards,

Hans


  parent reply	other threads:[~2026-02-02 15:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  9:24 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   ` [PATCH v3 0/2] Add TPS68470 power supply support for ov13b10 sensor Arun T
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 ` johannes.goede [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-30  9:19 [PATCH 1/2] platform/x86: int3472: Add board data for Intel nvl Arun T

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=f44ec888-a2b1-4ade-b4ad-1cc3ff82903a@oss.qualcomm.com \
    --to=johannes.goede@oss.qualcomm.com \
    --cc=arun.t@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    /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®