From: Peng Fan <peng.fan@oss.nxp.com>
To: Tom Rini <trini@konsulko.com>
Cc: Julien Stephan <jstephan@baylibre.com>,
u-boot@lists.denx.de, Jaehoon Chung <jh80.chung@samsung.com>,
Peng Fan <peng.fan@nxp.com>,
Tanmay Kathpalia <tanmay.kathpalia@altera.com>,
Ye Li <ye.li@nxp.com>, Dragan Simic <dsimic@manjaro.org>,
Jonas Karlman <jonas@kwiboo.se>,
David Lechner <dlechner@baylibre.com>,
GSS_MTK_Uboot_upstream <GSS_MTK_Uboot_upstream@mediatek.com>
Subject: Re: [PATCH 0/3] Fix compilation issue on regulator_common file
Date: Thu, 11 Dec 2025 16:39:04 +0800 [thread overview]
Message-ID: <aTqDKJajdSbhChr8@shlinux89> (raw)
In-Reply-To: <20251210213826.GK303283@bill-the-cat>
Hi Tom,
On Wed, Dec 10, 2025 at 03:38:26PM -0600, Tom Rini wrote:
>On Wed, Dec 10, 2025 at 10:24:21PM +0100, Julien Stephan wrote:
>
>> Hello,
>>
>> If CONFIG_DM_GPIO is not enabled, compilation of
>> drivers/power/regulator/regulator_common.c fails with the following
>> errors:
>
>How did you get this condition exactly? I'm inclined to say DM_REGULATOR
>&& !DM_GPIO shouldn't be allowed today, and I see what looks like a
DM_GPIO is not a must for DM_REGULATOR. Only DM_REGULATOR_GPIO needs DM_GPIO.
>Kconfig bug where SPL_DM_REGULATOR depends on SPL_GPIO and not
>SPL_DM_GPIO.
I think you are saying SPL_DM_REGULATOR_GPIO, not SPL_DM_REGULATOR.
Regards
Peng
>
>--
>Tom
prev parent reply other threads:[~2025-12-11 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 21:24 [PATCH 0/3] Fix compilation issue on regulator_common file Julien Stephan
2025-12-10 21:24 ` [PATCH 1/3] power: regulator: common: remove unnecessary debug trace Julien Stephan
2025-12-11 8:27 ` Peng Fan
2025-12-10 21:24 ` [PATCH 2/3] power: regulator: common: use dm_gpio_is_valid helper Julien Stephan
2025-12-11 8:29 ` Peng Fan
2025-12-10 21:24 ` [PATCH 3/3] power: regulator: common: fix compilation issue Julien Stephan
2025-12-11 8:33 ` Peng Fan
2025-12-10 21:38 ` [PATCH 0/3] Fix compilation issue on regulator_common file Tom Rini
2025-12-11 8:39 ` Peng Fan [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=aTqDKJajdSbhChr8@shlinux89 \
--to=peng.fan@oss.nxp.com \
--cc=GSS_MTK_Uboot_upstream@mediatek.com \
--cc=dlechner@baylibre.com \
--cc=dsimic@manjaro.org \
--cc=jh80.chung@samsung.com \
--cc=jonas@kwiboo.se \
--cc=jstephan@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=tanmay.kathpalia@altera.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ye.li@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.