From: Sasha Levin <sashal@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Ulf Hansson <ulfh@kernel.org>,
Guangshuo Li <lgs201920130244@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-pm@vger.kernel.org, imx@lists.linux.dev,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the pmdomain-fixes tree
Date: Tue, 10 Nov 2026 12:02:53 -0500 [thread overview]
Message-ID: <20261110170253.2694265-1-sashal@kernel.org> (raw)
In-Reply-To: <avNHazNbGtMQJ5pV@sirena.org.uk>
On Tue, Nov 10, 2026 at 04:33:47PM +0000, Mark Brown wrote:
>AFAICT this is caused by commit
>
> d7262971a2acc (pmdomain: imx: gpc: remove all initialized power domains)
>
>though I don't really see how. I have used the tree from next-20261109
>instead.
The while loop that commit adds to imx_gpc_remove() is never closed, so
the function is still open at the end of the file:
while (num_domains--) {
ret = pm_genpd_remove(&imx_gpc_domains[num_domains].base);
if (ret) {
...
return;
}
if (num_domains == GPC_PGC_DOMAIN_PU)
imx_pgc_put_clocks(&imx_gpc_domains[num_domains]);
}
The patch was posted that way [1]. gpc.c is only built with
HAVE_IMX_GPC, which only SOC_IMX6 on 32-bit ARM selects, so x86 and
arm64 builds do not see it.
With the brace added, gpc.o builds with imx_v6_v7_defconfig:
--- a/drivers/pmdomain/imx/gpc.c
+++ b/drivers/pmdomain/imx/gpc.c
@@ -536,8 +536,9 @@
return;
}
- if (num_domains == GPC_PGC_DOMAIN_PU)
- imx_pgc_put_clocks(&imx_gpc_domains[num_domains]);
+ if (num_domains == GPC_PGC_DOMAIN_PU)
+ imx_pgc_put_clocks(&imx_gpc_domains[num_domains]);
+ }
}
of_node_put(pgc_node);
[1] https://lore.kernel.org/all/20260924142520.1594149-1-lgs201920130244@gmail.com/
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-10 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 16:33 Mark Brown
2026-11-10 17:02 ` Sasha Levin [this message]
2026-11-10 17:07 ` Mark Brown
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=20261110170253.2694265-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=imx@lists.linux.dev \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=ulfh@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®