linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Khiem Nguyen <khiem.nguyen.xt@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH RFC 0/7] ARM: shmobile: Support L2 shutdown mode in Suspend-to-RAM
Date: Fri, 26 Sep 2014 10:20:29 +0000	[thread overview]
Message-ID: <54253DED.2030209@renesas.com> (raw)
In-Reply-To: <5424D1ED.6070309@renesas.com>

Hi Geert-san,

On 9/26/2014 7:04 PM, Geert Uytterhoeven wrote:
> Hi Khiem-san,
> 
> On Fri, Sep 26, 2014 at 4:39 AM, Khiem Nguyen
> <khiem.nguyen.xt@renesas.com> wrote:
>> These patches implement L2 shutdown mode in RCar Gen2 SoC and change
>> Suspend-to-RAM from Core Standby mode to L2 shutdown mode.
>> The impact to CPUIdle operation was also put into consideration during
>> implementation.
>>
>> I have confirmed Suspend-to-RAM in Lager board and Koelsch board.
>> So far, there is no regression detected during my testing.
>> There might be further patches to support Alt board. But it would be
>> after upstream kernel can boot up in Alt board.
>>
>> I hope to receive some comments for this patch series whether it's
>> right direction or not. Therefore, I marked it with RFC.
>> Any comments are appreciated.
> 
> While testing with various combinations of CONFIG_PM options, I noticed
> the build fails if CONFIG_ARM_CPU_SUSPEND is not set:
> 
> arch/arm/mach-shmobile/built-in.o: In function
> `shmobile_smp_apmu_enter_cpuidle':
> :(.text+0x27c): undefined reference to `cpu_suspend'
> arch/arm/mach-shmobile/built-in.o: In function `shmobile_cpuidle_notifier_call':
> :(.text+0x305c): undefined reference to `cpu_resume'
> arch/arm/mach-shmobile/built-in.o: In function `shmobile_smp_apmu_prepare_cpus':
> :(.init.text+0xddc): undefined reference to `cpu_resume'
> arch/arm/mach-shmobile/built-in.o: In function `shmobile_cpuidle_init':
> :(.init.text+0xe9c): undefined reference to `cpu_resume'
> make[3]: *** [vmlinux] Error 1
> make[2]: *** [sub-make] Error 2
> make[1]: *** [__sub-make] Error 2
> make: *** [all] Error 2
> 
That is interesting build error.
To make it clearer and able to fix it, please kindly confirm below points:
1. This only occurred after merging my patch ?
(The part related to shmobile_cpuidle_init seems out of my scope.)
2. What kind of 'various combinations of CONFIG_PM options' were you select ?

Thanks.

> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds
> 

-- 
Best regards,
KHIEM Nguyen

  parent reply	other threads:[~2014-09-26 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26  2:39 [PATCH RFC 0/7] ARM: shmobile: Support L2 shutdown mode in Suspend-to-RAM Khiem Nguyen
2014-09-26 10:04 ` Geert Uytterhoeven
2014-09-26 10:20 ` Khiem Nguyen [this message]
2014-09-26 11:12 ` Khiem Nguyen

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=54253DED.2030209@renesas.com \
    --to=khiem.nguyen.xt@renesas.com \
    --cc=linux-sh@vger.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;
as well as URLs for NNTP newsgroup(s).