From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: OMAP* Latest build failures
Date: Wed, 14 Nov 2012 08:59:48 -0800 [thread overview]
Message-ID: <20121114165947.GR6801@atomide.com> (raw)
In-Reply-To: <20121114164801.GQ6801@atomide.com>
* Tony Lindgren <tony@atomide.com> [121114 08:50]:
> * Tomi Valkeinen <tomi.valkeinen@ti.com> [121114 03:47]:
> > On 2012-11-14 11:26, Russell King - ARM Linux wrote:
> > > OMAP* allnoconfig fails:
> > >
> > > arch/arm/mach-omap2/built-in.o: In function `omap_dss_set_min_bus_tput':
> > > twl-common.c:(.text+0x1e08): undefined reference to `omap_pm_set_min_bus_tput'
> > > arch/arm/mach-omap2/built-in.o: In function `omap_hwmod_init_postsetup':
> > > twl-common.c:(.init.text+0x8f8): undefined reference to `omap_pm_if_early_init'
> > > arch/arm/mach-omap2/built-in.o: In function `omap_serial_init_port':
> > > twl-common.c:(.init.text+0x1284): undefined reference to `omap_pm_get_dev_context_loss_count'
> > > arch/arm/mach-omap2/built-in.o: In function `omap_timer_init':
> > > twl-common.c:(.init.text+0x1544): undefined reference to `omap_pm_get_dev_context_loss_count'
> > > arch/arm/mach-omap2/built-in.o: In function `omap2_common_pm_init':
> > > twl-common.c:(.init.text+0x1af0): undefined reference to `omap_pm_if_init'
> > > arch/arm/mach-omap2/built-in.o: In function `omap2_gpio_dev_init':
> > > twl-common.c:(.init.text+0x2168): undefined reference to `omap_pm_get_dev_context_loss_count'
> > > arch/arm/mach-omap2/built-in.o: In function `omap_display_init':
> > > twl-common.c:(.init.text+0x25cc): undefined reference to `omap_pm_get_dev_context_loss_count'
> >
> > I'm not able to reproduce this. I took v3.7-rc5, and the omap4430-sdp
> > noconfig
> > (http://www.arm.linux.org.uk/developer/build/file.php?type=config&idx=2711),
> > and it builds fine for me.
>
> It happens if in arm-soc/for-next and rmk/for-next. Looks like the
> CONFIG_OMAP_PM_NOOP can't be under CONFIG_PM in the makefile where I moved it
> in commit 6e740f9a8.
This should say just "It happens in arm-soc/for-next".
> Looks like in my test configs I run make oldnoconfig on Russell's seed
> config, and I do get CONFIG_PM=y set while Russell's generated config
> does not have that. No ideas yet why oldnoconfig add CONFIG_PM=y..
>
> Anyways, patch below to make it behave like earlier.
>
> Regards,
>
> Tony
>
>
> From: Tony Lindgren <tony@atomide.com>
> Date: Wed, 14 Nov 2012 08:40:00 -0800
> Subject: [PATCH] ARM: OMAP: Fix compile for OMAP_PM_NOOP if PM is not selected
>
> Commit 6e740f9a8 (ARM: OMAP: Move omap-pm-noop.c local to mach-omap2)
> moved omap-pm-noop to be local to mach-omap2. However, the makefile
> entry got placed within ifeq ($(CONFIG_PM),y) which was not the
> case earlier.
>
> Fix the issue by moving it out of the ifeq ($(CONFIG_PM),y) in
> the makefile as these stubs are needed also when PM is not set.
>
> Reported-by: Russell King <rmk+kernel@arm.linux.org.uk>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> --- a/arch/arm/mach-omap2/Makefile
> +++ b/arch/arm/mach-omap2/Makefile
> @@ -68,6 +68,8 @@ obj-$(CONFIG_ARCH_OMAP4) += opp4xxx_data.o
> endif
>
> # Power Management
> +obj-$(CONFIG_OMAP_PM_NOOP) += omap-pm-noop.o
> +
> ifeq ($(CONFIG_PM),y)
> obj-$(CONFIG_ARCH_OMAP2) += pm24xx.o
> obj-$(CONFIG_ARCH_OMAP2) += sleep24xx.o
> @@ -75,7 +77,6 @@ obj-$(CONFIG_ARCH_OMAP3) += pm34xx.o sleep34xx.o
> obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o omap-mpuss-lowpower.o
> obj-$(CONFIG_SOC_OMAP5) += omap-mpuss-lowpower.o
> obj-$(CONFIG_PM_DEBUG) += pm-debug.o
> -obj-$(CONFIG_OMAP_PM_NOOP) += omap-pm-noop.o
>
> obj-$(CONFIG_POWER_AVS_OMAP) += sr_device.o
> obj-$(CONFIG_POWER_AVS_OMAP_CLASS3) += smartreflex-class3.o
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP* Latest build failures
Date: Wed, 14 Nov 2012 08:59:48 -0800 [thread overview]
Message-ID: <20121114165947.GR6801@atomide.com> (raw)
In-Reply-To: <20121114164801.GQ6801@atomide.com>
* Tony Lindgren <tony@atomide.com> [121114 08:50]:
> * Tomi Valkeinen <tomi.valkeinen@ti.com> [121114 03:47]:
> > On 2012-11-14 11:26, Russell King - ARM Linux wrote:
> > > OMAP* allnoconfig fails:
> > >
> > > arch/arm/mach-omap2/built-in.o: In function `omap_dss_set_min_bus_tput':
> > > twl-common.c:(.text+0x1e08): undefined reference to `omap_pm_set_min_bus_tput'
> > > arch/arm/mach-omap2/built-in.o: In function `omap_hwmod_init_postsetup':
> > > twl-common.c:(.init.text+0x8f8): undefined reference to `omap_pm_if_early_init'
> > > arch/arm/mach-omap2/built-in.o: In function `omap_serial_init_port':
> > > twl-common.c:(.init.text+0x1284): undefined reference to `omap_pm_get_dev_context_loss_count'
> > > arch/arm/mach-omap2/built-in.o: In function `omap_timer_init':
> > > twl-common.c:(.init.text+0x1544): undefined reference to `omap_pm_get_dev_context_loss_count'
> > > arch/arm/mach-omap2/built-in.o: In function `omap2_common_pm_init':
> > > twl-common.c:(.init.text+0x1af0): undefined reference to `omap_pm_if_init'
> > > arch/arm/mach-omap2/built-in.o: In function `omap2_gpio_dev_init':
> > > twl-common.c:(.init.text+0x2168): undefined reference to `omap_pm_get_dev_context_loss_count'
> > > arch/arm/mach-omap2/built-in.o: In function `omap_display_init':
> > > twl-common.c:(.init.text+0x25cc): undefined reference to `omap_pm_get_dev_context_loss_count'
> >
> > I'm not able to reproduce this. I took v3.7-rc5, and the omap4430-sdp
> > noconfig
> > (http://www.arm.linux.org.uk/developer/build/file.php?type=config&idx=2711),
> > and it builds fine for me.
>
> It happens if in arm-soc/for-next and rmk/for-next. Looks like the
> CONFIG_OMAP_PM_NOOP can't be under CONFIG_PM in the makefile where I moved it
> in commit 6e740f9a8.
This should say just "It happens in arm-soc/for-next".
> Looks like in my test configs I run make oldnoconfig on Russell's seed
> config, and I do get CONFIG_PM=y set while Russell's generated config
> does not have that. No ideas yet why oldnoconfig add CONFIG_PM=y..
>
> Anyways, patch below to make it behave like earlier.
>
> Regards,
>
> Tony
>
>
> From: Tony Lindgren <tony@atomide.com>
> Date: Wed, 14 Nov 2012 08:40:00 -0800
> Subject: [PATCH] ARM: OMAP: Fix compile for OMAP_PM_NOOP if PM is not selected
>
> Commit 6e740f9a8 (ARM: OMAP: Move omap-pm-noop.c local to mach-omap2)
> moved omap-pm-noop to be local to mach-omap2. However, the makefile
> entry got placed within ifeq ($(CONFIG_PM),y) which was not the
> case earlier.
>
> Fix the issue by moving it out of the ifeq ($(CONFIG_PM),y) in
> the makefile as these stubs are needed also when PM is not set.
>
> Reported-by: Russell King <rmk+kernel@arm.linux.org.uk>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> --- a/arch/arm/mach-omap2/Makefile
> +++ b/arch/arm/mach-omap2/Makefile
> @@ -68,6 +68,8 @@ obj-$(CONFIG_ARCH_OMAP4) += opp4xxx_data.o
> endif
>
> # Power Management
> +obj-$(CONFIG_OMAP_PM_NOOP) += omap-pm-noop.o
> +
> ifeq ($(CONFIG_PM),y)
> obj-$(CONFIG_ARCH_OMAP2) += pm24xx.o
> obj-$(CONFIG_ARCH_OMAP2) += sleep24xx.o
> @@ -75,7 +77,6 @@ obj-$(CONFIG_ARCH_OMAP3) += pm34xx.o sleep34xx.o
> obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o omap-mpuss-lowpower.o
> obj-$(CONFIG_SOC_OMAP5) += omap-mpuss-lowpower.o
> obj-$(CONFIG_PM_DEBUG) += pm-debug.o
> -obj-$(CONFIG_OMAP_PM_NOOP) += omap-pm-noop.o
>
> obj-$(CONFIG_POWER_AVS_OMAP) += sr_device.o
> obj-$(CONFIG_POWER_AVS_OMAP_CLASS3) += smartreflex-class3.o
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-11-14 16:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 9:26 OMAP* Latest build failures Russell King - ARM Linux
2012-11-14 9:26 ` Russell King - ARM Linux
2012-11-14 10:08 ` Peter Ujfalusi
2012-11-14 10:08 ` Peter Ujfalusi
2012-11-14 10:35 ` Russell King - ARM Linux
2012-11-14 10:35 ` Russell King - ARM Linux
2012-11-14 11:45 ` Tomi Valkeinen
2012-11-14 11:45 ` Tomi Valkeinen
2012-11-14 16:48 ` Tony Lindgren
2012-11-14 16:48 ` Tony Lindgren
2012-11-14 16:59 ` Tony Lindgren [this message]
2012-11-14 16:59 ` Tony Lindgren
2012-11-14 17:17 ` Tony Lindgren
2012-11-14 17:17 ` Tony Lindgren
2012-11-14 17:44 ` Russell King - ARM Linux
2012-11-14 17:44 ` Russell King - ARM Linux
2012-11-14 17:42 ` Russell King - ARM Linux
2012-11-14 17:42 ` Russell King - ARM Linux
2012-11-17 9:33 ` Russell King - ARM Linux
2012-11-17 9:33 ` Russell King - ARM Linux
2012-11-20 17:57 ` Tony Lindgren
2012-11-20 17:57 ` Tony Lindgren
2012-11-20 23:00 ` Jon Hunter
2012-11-20 23:00 ` Jon Hunter
2012-11-28 15:18 ` Russell King - ARM Linux
2012-11-28 15:18 ` Russell King - ARM Linux
2012-11-28 21:43 ` Jon Hunter
2012-11-28 21:43 ` Jon Hunter
2012-11-28 14:04 ` Eduardo Valentin
2012-11-28 14:04 ` Eduardo Valentin
2012-11-28 15:16 ` Russell King - ARM Linux
2012-11-28 15:16 ` Russell King - ARM Linux
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=20121114165947.GR6801@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tomi.valkeinen@ti.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.