From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: linux-next ARM multi-platform randconfig errors
Date: Fri, 19 Apr 2013 12:51:01 -0700 [thread overview]
Message-ID: <20130419195100.GR10155@atomide.com> (raw)
In-Reply-To: <20130419194323.GP10155@atomide.com>
* Tony Lindgren <tony@atomide•com> [130419 12:49]:
> * Tomi Valkeinen <tomi.valkeinen@ti•com> [130419 09:46]:
> > On 2013-04-19 19:12, Tony Lindgren wrote:
> > > * Rob Herring <robherring2@gmail•com> [130418 20:11]:
> >
> > >> dss-common.c:(.cpuinit.text+0x38): undefined reference to `omap_get_wakeupgen_base'
> > >> dss-common.c:(.cpuinit.text+0x48): undefined reference to `omap_secure_apis_support'
> > >> dss-common.c:(.init.text+0x3db0): undefined reference to `omap_get_wakeupgen_base'
> > >> dss-common.c:(.init.text+0x3dcc): undefined reference to `omap_secure_apis_support'
> > >> dss-common.c:(.init.text+0x61b8): undefined reference to `usb_bind_phy'
> > >> dss-common.c:(.init.text+0x6314): undefined reference to `usb_bind_phy'
> > >> dss-common.c:(.init.text+0x6488): undefined reference to `usb_bind_phy'
> > >> dss-common.c:(.init.text+0x65ac): undefined reference to `usb_bind_phy'
> > >> dss-common.c:(.ref.text+0x10): undefined reference to `omap_get_wakeupgen_base'
> > >> dss-common.c:(.ref.text+0x18): undefined reference to `omap_secure_apis_support'
> > >> dss-common.c:(.ref.text+0x54): undefined reference to `omap4_hotplug_cpu'
> > >> dss-common.c:(.ref.text+0x58): undefined reference to `omap_secure_apis_support'
> > >> dss-common.c:(.text+0x11b5c): undefined reference to `usb_bind_phy'
> > >
> > > Tomi, can you take a look at the dss-common.c one? That should be
> > > reproducable with omap2plus_defconfig and modifying some options
> > > there.
> >
> > None of those functions are used by dss-common.c, so I don't really know
> > what that is about. Doesn't look correct errors to me... I can try to
> > reproduce.
>
> This might happen when no SoC selected. There was a patch posted
> by Arnd to always select 2420 if nothing else is selected as it's the
> most minimal one. But Russell did not like that, so probably the way
> to fix that would be to have bool OMAP_SOC and if not selected, don't
> even try to build anything. I'll take a look at that.
>
> > Btw, there's also this:
> >
> > >> drivers/video/omap2/dss/dpi.c:181:2: error: implicit declaration of function 'dsi_hsdiv_calc' [-Werror=implicit-function-declaration]
> > >> drivers/video/omap2/dss/dpi.c:201:2: error: implicit declaration of function 'dsi_get_pll_clkin' [-Werror=implicit-function-declaration]
> > >> drivers/video/omap2/dss/dpi.c:212:2: error: implicit declaration of function 'dsi_pll_calc' [-Werror=implicit-function-declaration]
> >
> > I have a patch for that, not yet applied.
>
> OK thanks.
Sorry forgot to leave out my .config in the previous mail. No need for
the .config I posted as you already have those errors fixed.
Regards,
Tony
next prev parent reply other threads:[~2013-04-19 19:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 3:06 linux-next ARM multi-platform randconfig errors Rob Herring
2013-04-19 16:12 ` Tony Lindgren
2013-04-19 16:41 ` Tomi Valkeinen
2013-04-19 19:43 ` Tony Lindgren
2013-04-19 19:51 ` Tony Lindgren [this message]
2013-04-19 20:11 ` Arnd Bergmann
2013-04-19 20:40 ` Tony Lindgren
2013-04-19 20:58 ` Arnd Bergmann
[not found] ` <20130419215134.GY10155@atomide.com>
2013-04-19 22:08 ` Arnd Bergmann
2013-04-19 22:53 ` Paul Walmsley
2013-04-19 21:02 ` Tony Lindgren
2013-04-19 21:09 ` Tony Lindgren
2013-04-19 19:52 ` Jon Hunter
2013-04-19 20:42 ` Tony Lindgren
2013-04-19 17:23 ` Tony Lindgren
2013-04-22 7:23 ` Roger Quadros
2013-04-22 8:21 ` Felipe Balbi
2013-04-22 11:52 ` Felipe Balbi
2013-04-22 12:45 ` Kishon Vijay Abraham I
2013-04-22 13:04 ` Felipe Balbi
2013-04-22 17:32 ` Mikulas Patocka
2013-04-22 22:57 ` Rob Herring
2013-05-13 22:37 ` [PATCH] bcache: Fix link errors on ARM Mikulas Patocka
2013-04-22 18:59 ` linux-next ARM multi-platform randconfig errors Mike Turquette
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=20130419195100.GR10155@atomide.com \
--to=tony@atomide$(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