public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Lin <shawn.lin@rock-chips.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Ulf Hansson <ulf.hansson@linaro.org>
Cc: shawn.lin@rock-chips.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Subject: Re: linux-next: build failure after merge of the pmdomain tree
Date: Thu, 20 Feb 2025 09:53:44 +0800	[thread overview]
Message-ID: <4e07e570-25ef-4d03-b1b8-5acf8bc8bc8a@rock-chips.com> (raw)
In-Reply-To: <20250220113338.60ba2290@canb.auug.org.au>

在 2025/2/20 8:33, Stephen Rothwell 写道:
> Hi all,
> 
> After merging the pmdomain tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> x86_64-linux-gnu-ld: vmlinux.o: in function `rockchip_do_pmu_set_power_domain':
> pm-domains.c:(.text+0x19aa103): undefined reference to `arm_smccc_1_1_get_conduit'
> 
> Caused by commit
> 
>    61eeb9678789 ("pmdomain: rockchip: Check if SMC could be handled by TA")
> 
> $ grep CONFIG_HAVE_ARM_SMCCC_DISCOVERY .config

It seems x86_64_defconfig did't enable  CONFIG_HAVE_ARM_SMCCC_DISCOVERY 
which apparently belongs to ARM stuff.

Selecting HAVE_ARM_SMCCC_DISCOVERY and ARM_PSCI_FW should pass the
x86_64 allmodconfig compile.

--- a/drivers/pmdomain/rockchip/Kconfig
+++ b/drivers/pmdomain/rockchip/Kconfig
@@ -5,6 +5,8 @@ config ROCKCHIP_PM_DOMAINS
         bool "Rockchip generic power domain"
         depends on PM
         select PM_GENERIC_DOMAINS
+       select ARM_PSCI_FW
+       select HAVE_ARM_SMCCC_DISCOVERY
         help
           Say y here to enable power domain support.
           In order to meet high performance and low power requirements, 
a power


> $
> 
> I have used the pmdomain tree from next-20250219 for today.
> 


  reply	other threads:[~2025-02-20  4:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20  0:33 linux-next: build failure after merge of the pmdomain tree Stephen Rothwell
2025-02-20  1:53 ` Shawn Lin [this message]
2025-02-24  1:23 ` Stephen Rothwell
2025-02-24  5:20   ` Stephen Rothwell
2025-02-24 12:16     ` Ulf Hansson
2025-02-25  0:34       ` Martin K. Petersen
2025-02-27 15:56       ` Geert Uytterhoeven
2025-02-27 16:16         ` Heiko Stübner
2025-02-27 17:05           ` Geert Uytterhoeven
2025-02-28  9:01             ` Heiko Stübner
2025-02-28  9:41               ` Geert Uytterhoeven
2025-02-28 12:59               ` Ulf Hansson
  -- strict thread matches above, loose matches on Subject: below --
2025-10-22 23:30 Stephen Rothwell

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=4e07e570-25ef-4d03-b1b8-5acf8bc8bc8a@rock-chips.com \
    --to=shawn.lin@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=ulf.hansson@linaro.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