public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: d-gerlach@ti•com (Dave Gerlach)
To: linux-arm-kernel@lists•infradead.org
Subject: Build error with !CONFIG_SMP in v4.2-rc1 on arm multi_v7_defconfig
Date: Fri, 10 Jul 2015 14:31:16 -0500	[thread overview]
Message-ID: <55A01D84.8070701@ti.com> (raw)

Hello,
I am seeing the following error when building v4.2-rc1 for arm with
multi_v7_defconfig with CONFIG_SMP=n:

 LINK    vmlinux
  LD      vmlinux.o
  MODPOST vmlinux.o
  GEN     .version
  CHK     include/generated/compile.h
  UPD     include/generated/compile.h
  CC      init/version.o
  LD      init/built-in.o
drivers/built-in.o: In function `qcom_pm_collapse':
:(.text+0xaf44c): undefined reference to `qcom_scm_cpu_power_down'
drivers/built-in.o: In function `qcom_cpuidle_init':
:(.init.text+0x9508): undefined reference to `qcom_scm_set_warm_boot_addr'
make: *** [vmlinux] Error 1


It appears the calling functions in drivers/soc/qcom/spm.c get included by
CONFIG_QCOM_PM which is part of multi_v7_defconfig but the missing functions
from drivers/firmware/qcom_scm.c only get included by CONFIG_QCOM_SCM if SMP is
selected. I am not sure if the correct approach is to remove CONFIG_QCOM_PM from
multi_v7_defconfig or to remove 'if SMP' from CONFIG_QCOM_SCM, or something else
entirely. Thoughts?

Regards,
Dave

             reply	other threads:[~2015-07-10 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 19:31 Dave Gerlach [this message]
2015-07-10 19:36 ` Build error with !CONFIG_SMP in v4.2-rc1 on arm multi_v7_defconfig Stephen Boyd
2015-07-10 20:29   ` Dave Gerlach
2015-07-10 20:39     ` Lina Iyer
2015-07-10 20:42       ` Dave Gerlach
2015-07-10 20:18 ` [PATCH] drivers: qcom: Select QCOM_SCM unconditionally for QCOM_PM Lina Iyer
2015-07-10 21:09   ` Stephen Boyd
2015-07-14 21:54   ` Andy Gross
2015-07-23 20:07     ` Andy Gross

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=55A01D84.8070701@ti.com \
    --to=d-gerlach@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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