* Re: next-20150402 build: 3 failures 18 warnings (next-20150402)
2015-04-02 11:22 ` next-20150402 build: 3 failures 18 warnings (next-20150402) Mark Brown
@ 2015-04-02 13:50 ` Thierry Reding
2015-04-02 22:11 ` Thierry Reding
1 sibling, 0 replies; 4+ messages in thread
From: Thierry Reding @ 2015-04-02 13:50 UTC (permalink / raw)
To: Mark Brown
Cc: Paul Walmsley, Mike Turquette, Catalin Marinas, Will Deacon,
kernel-build-reports, linaro-kernel, linux-next, linux-arm-kernel
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
On Thu, Apr 02, 2015 at 12:22:31PM +0100, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Thu, Apr 02, 2015 at 09:33:03AM +0100, Build bot for Mark Brown wrote:
>
> > Failed defconfigs:
> > arm64-allmodconfig
>
> For the past few days -next has been failing to build an arm64
> allmodconfig due to:
>
> | drivers/built-in.o: In function `tegra124_132_clock_init_post':
> | :(.init.text+0x285d8): undefined reference to `tegra_emc_init'
>
> This is triggered by d035fdfa27ac124bc8 (arm64: Add Tegra132 support)
> which enables ARCH_TEGRA and ARCH_TEGRA_132_SOC for arm64 which in turn
> causes clk-tegra124 to be built on arm64. That driver relies on
> TEGRA124_EMC but that depends on ARCH_TEGRA_124_SOC which is 32 bit
> only.
It's actually triggered by a newer patch (f8fd257fabf0 "clk: tegra: Add
EMC clock driver") which adds this new dependency.
> We either need the EMC driver for Tegra132, a stub or some ifdefs.
Tegra132 uses the same memory controller as Tegra124, so clk-emc should
work on both. I likely overlooked this when applying the patches. I also
have a local patch for this that I haven't pushed yet. Will do it right
away.
> It also looks like there's an issue if the memory controller driver is
> not enabled (which looks to be something that can be controlled by the
> user) but I've not checked properly.
I'll do some testing to see if I can break it by permutating some of the
Kconfig symbol combinations.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: next-20150402 build: 3 failures 18 warnings (next-20150402)
2015-04-02 11:22 ` next-20150402 build: 3 failures 18 warnings (next-20150402) Mark Brown
2015-04-02 13:50 ` Thierry Reding
@ 2015-04-02 22:11 ` Thierry Reding
1 sibling, 0 replies; 4+ messages in thread
From: Thierry Reding @ 2015-04-02 22:11 UTC (permalink / raw)
To: Mark Brown
Cc: Paul Walmsley, Mike Turquette, Catalin Marinas, Will Deacon,
kernel-build-reports, linaro-kernel, linux-next, linux-arm-kernel
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
On Thu, Apr 02, 2015 at 12:22:31PM +0100, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Thu, Apr 02, 2015 at 09:33:03AM +0100, Build bot for Mark Brown wrote:
>
> > Failed defconfigs:
> > arm64-allmodconfig
>
> For the past few days -next has been failing to build an arm64
> allmodconfig due to:
>
> | drivers/built-in.o: In function `tegra124_132_clock_init_post':
> | :(.init.text+0x285d8): undefined reference to `tegra_emc_init'
>
> This is triggered by d035fdfa27ac124bc8 (arm64: Add Tegra132 support)
> which enables ARCH_TEGRA and ARCH_TEGRA_132_SOC for arm64 which in turn
> causes clk-tegra124 to be built on arm64. That driver relies on
> TEGRA124_EMC but that depends on ARCH_TEGRA_124_SOC which is 32 bit
> only.
>
> We either need the EMC driver for Tegra132, a stub or some ifdefs.
>
> It also looks like there's an issue if the memory controller driver is
> not enabled (which looks to be something that can be controlled by the
> user) but I've not checked properly.
The ARM64 allmodconfig finally finished building and I've pushed
something that should hopefully fix things.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread