From: Hans de Goede <hansg@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Antti Laakso <antti.laakso@linux.intel.com>,
linux-media@vger.kernel.org, linux-gpio@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linusw@kernel.org,
brgl@kernel.org, mchehab@kernel.org, dan.scally@ideasonboard.com,
ilpo.jarvinen@linux.intel.com, hverkuil+cisco@kernel.org,
sre@kernel.org, hao.yao@intel.com, jason.z.chen@intel.com,
jimmy.su@intel.com, miguel.vadillo@intel.com, kees@kernel.org,
ribalda@chromium.org
Subject: Re: [PATCH 5/5] platform: int3472: Add MSI prestige board data
Date: Tue, 10 Mar 2026 15:24:27 +0100 [thread overview]
Message-ID: <54ed9147-e5e8-4419-9bb5-63e77de34fda@kernel.org> (raw)
In-Reply-To: <abAZ3ZJk3jpoKG8m@kekkonen.localdomain>
Hi,
On 10-Mar-26 14:17, Sakari Ailus wrote:
> Hi Hans,
>
> On Tue, Mar 10, 2026 at 02:09:54PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> On 10-Mar-26 13:44, Antti Laakso wrote:
>>> Define regulators and gpios for MSI Prestige 14 AI EVO+ laptop.
>>>
>>> Signed-off-by: Antti Laakso <antti.laakso@linux.intel.com>
>>> ---
>>> .../x86/intel/int3472/tps68470_board_data.c | 97 +++++++++++++++++++
>>> 1 file changed, 97 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..fe7c23e72d66 100644
>>> --- a/drivers/platform/x86/intel/int3472/tps68470_board_data.c
>>> +++ b/drivers/platform/x86/intel/int3472/tps68470_board_data.c
>>> @@ -232,6 +232,73 @@ static const struct tps68470_regulator_platform_data dell_7212_tps68470_pdata =
>>> },
>>> };
>>>
>>> +/* Settings for MSI Prestige 14 laptop. */
>>> +
>>> +static struct regulator_consumer_supply ovti5675_avdd_consumer_supplies[] = {
>>> + REGULATOR_SUPPLY("avdd", "i2c-OVTI5675:00"),
>>> +};
>>> +
>>> +static struct regulator_consumer_supply ovti5675_dovdd_consumer_supplies[] = {
>>> + REGULATOR_SUPPLY("dovdd", "i2c-OVTI5675:00"),
>>> +};
>>> +
>>> +static struct regulator_consumer_supply ovti5675_dvdd_consumer_supplies[] = {
>>> + REGULATOR_SUPPLY("dvdd", "i2c-OVTI5675:00"),
>>> +};
>>> +
>>> +static const struct regulator_init_data msi_p14_ai_evo_tps68470_core_reg_init_data = {
>>> + .constraints = {
>>> + .min_uV = 1200000,
>>> + .max_uV = 1200000,
>>> + .apply_uV = 1,
>>> + .valid_ops_mask = REGULATOR_CHANGE_STATUS,
>>> + },
>>> + .num_consumer_supplies = ARRAY_SIZE(ovti5675_dvdd_consumer_supplies),
>>> + .consumer_supplies = ovti5675_dvdd_consumer_supplies,
>>> +};
>>> +
>>> +static const struct regulator_init_data msi_p14_ai_evo_tps68470_ana_reg_init_data = {
>>> + .constraints = {
>>> + .min_uV = 2815200,
>>> + .max_uV = 2815200,
>>> + .apply_uV = 1,
>>> + .valid_ops_mask = REGULATOR_CHANGE_STATUS,
>>> + },
>>> + .num_consumer_supplies = ARRAY_SIZE(ovti5675_avdd_consumer_supplies),
>>> + .consumer_supplies = ovti5675_avdd_consumer_supplies,
>>> +};
>>> +
>>> +static const struct regulator_init_data msi_p14_ai_evo_tps68470_vio_reg_init_data = {
>>> + .constraints = {
>>> + .min_uV = 1800600,
>>> + .max_uV = 1800600,
>>> + .apply_uV = 1,
>>> + .valid_ops_mask = REGULATOR_CHANGE_STATUS,
>>> + },
>>> + .num_consumer_supplies = 0,
>>> + .consumer_supplies = NULL,
>>> +};
>>> +
>>> +static const struct regulator_init_data msi_p14_ai_evo_tps68470_vsio_reg_init_data = {
>>> + .constraints = {
>>> + .min_uV = 1800600,
>>> + .max_uV = 1800600,
>>> + .apply_uV = 1,
>>> + .valid_ops_mask = REGULATOR_CHANGE_STATUS,
>>> + },
>>> + .num_consumer_supplies = ARRAY_SIZE(ovti5675_dovdd_consumer_supplies),
>>> + .consumer_supplies = ovti5675_dovdd_consumer_supplies,
>>> +};
>>> +
>>> +static const struct tps68470_regulator_platform_data msi_p14_ai_evo_tps68470_pdata = {
>>> + .reg_init_data = {
>>> + [TPS68470_CORE] = &msi_p14_ai_evo_tps68470_core_reg_init_data,
>>> + [TPS68470_ANA] = &msi_p14_ai_evo_tps68470_ana_reg_init_data,
>>> + [TPS68470_VIO] = &msi_p14_ai_evo_tps68470_vio_reg_init_data,
>>> + [TPS68470_VSIO] = &msi_p14_ai_evo_tps68470_vsio_reg_init_data,
>>> + },
>>> +};
>>> +
>>> static struct gpiod_lookup_table surface_go_int347a_gpios = {
>>> .dev_id = "i2c-INT347A:00",
>>> .table = {
>>> @@ -258,6 +325,19 @@ static struct gpiod_lookup_table dell_7212_int3479_gpios = {
>>> }
>>> };
>>>
>>> +static struct gpiod_lookup_table msi_p14_ai_evo_ovti5675_gpios = {
>>> + .dev_id = "i2c-OVTI5675:00",
>>> + .table = {
>>> + GPIO_LOOKUP_IDX("tps68470-gpio", 9, "reset", 0, GPIO_ACTIVE_LOW),
>>> + GPIO_LOOKUP_IDX("tps68470-gpio", 7, "reset", 1, GPIO_ACTIVE_LOW),
>>> + { }
>>> + }
>>> +};
>>> +
>>> +static const struct tps68470_gpio_platform_data msi_p14_ai_evo_tps68470_gpio_pdata = {
>>> + .daisy_chain_enable = true,
>>> +};
>>> +
>>> static const struct int3472_tps68470_board_data surface_go_tps68470_board_data = {
>>> .dev_name = "i2c-INT3472:05",
>>> .tps68470_regulator_pdata = &surface_go_tps68470_pdata,
>>> @@ -287,6 +367,16 @@ static const struct int3472_tps68470_board_data dell_7212_tps68470_board_data =
>>> },
>>> };
>>>
>>> +static const struct int3472_tps68470_board_data msi_p14_ai_evo_tps68470_board_data = {
>>> + .dev_name = "i2c-INT3472:06",
>>> + .tps68470_regulator_pdata = &msi_p14_ai_evo_tps68470_pdata,
>>> + .tps68470_gpio_pdata = &msi_p14_ai_evo_tps68470_gpio_pdata,
>>> + .n_gpiod_lookups = 1,
>>> + .tps68470_gpio_lookup_tables = {
>>> + &msi_p14_ai_evo_ovti5675_gpios,
>>> + },
>>> +};
>>> +
>>> static const struct dmi_system_id int3472_tps68470_board_data_table[] = {
>>> {
>>> .matches = {
>>> @@ -316,6 +406,13 @@ static const struct dmi_system_id int3472_tps68470_board_data_table[] = {
>>> },
>>> .driver_data = (void *)&dell_7212_tps68470_board_data,
>>> },
>>> + {
>>> + .matches = {
>>> + DMI_EXACT_MATCH(DMI_SYS_VENDOR, "Micro-Star International Co., Ltd."),
>>> + DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "Prestige 14 AI+ Evo C2VMG"),
>>
>> I think this match might be a bit too specific, e.g. there also is a C1M model where
>> this might also apply? See:
>>
>> https://www.msi.com/Business-Productivity/Prestige-14-AI-Evo-C1MX
>>
>> or maybe these are really different ?
>>
>> If you can look into that somehow that would be great. If you cannot find
>> out if other models are compatible we should probably play it safe and
>> keep the specific match you've above for now.
>
> This one is MTL whereas Antti's patch adds support for an LNL laptop. It'd
> be great if we could get a confirmation from MSI the PMIC configuration in
> these models would match Presige 14 AI+ (or that it's different). There's
> also a very similar model with a 13" display... Without a confirmation I
> wouldn't relax the DMI check.
>
> That being said, the risk of smoke being released might be small on a wrong
> regulator (or GPIO) configuration but it can't be ruled out.
Ack, lets keep the match as is for now then.
Regards,
Hans
next prev parent reply other threads:[~2026-03-10 14:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 12:44 [PATCH 0/5] platform: int3472: Add MSI prestige 14 AI EVO data Antti Laakso
2026-03-10 12:44 ` [PATCH 1/5] media: i2c: ov5675: Wait for endpoint Antti Laakso
2026-03-10 13:03 ` Hans de Goede
2026-03-10 13:08 ` Sakari Ailus
2026-03-10 13:12 ` Hans de Goede
2026-03-10 12:44 ` [PATCH 2/5] media: ipu-bridge: Add ov5675 sensor Antti Laakso
2026-03-10 13:06 ` Hans de Goede
2026-03-10 13:25 ` Dan Scally
2026-03-10 12:44 ` [PATCH 3/5] platform: int3472: Add gpio platform data Antti Laakso
2026-03-10 13:06 ` Hans de Goede
2026-03-10 13:32 ` Bartosz Golaszewski
2026-03-11 11:17 ` Antti Laakso
2026-03-10 14:27 ` Dan Scally
2026-03-10 12:44 ` [PATCH 4/5] gpio: tps68470: Add i2c daisy chain support Antti Laakso
2026-03-10 13:07 ` Hans de Goede
2026-03-10 14:33 ` Dan Scally
2026-03-10 12:44 ` [PATCH 5/5] platform: int3472: Add MSI prestige board data Antti Laakso
2026-03-10 13:09 ` Hans de Goede
2026-03-10 13:17 ` Sakari Ailus
2026-03-10 14:24 ` Hans de Goede [this message]
2026-03-10 14:32 ` Dan Scally
2026-03-10 15:02 ` Hans de Goede
2026-03-11 11:20 ` Antti Laakso
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=54ed9147-e5e8-4419-9bb5-63e77de34fda@kernel.org \
--to=hansg@kernel.org \
--cc=antti.laakso@linux.intel.com \
--cc=brgl@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=hao.yao@intel.com \
--cc=hverkuil+cisco@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jason.z.chen@intel.com \
--cc=jimmy.su@intel.com \
--cc=kees@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=miguel.vadillo@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sre@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