Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1486207
| From | MyungJoo Ham <myungjoo.ham@samsung.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | RE: Re: linux-next: build failure after merge of the pm tree |
| Date | 2016-09-19 09:40 +0200 |
| Message-ID | <sj1lf-2uv-11@gated-at.bofh.it> (permalink) |
| References | <sh9ZE-3zW-9@gated-at.bofh.it> <sj1lf-2uv-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
> On Wednesday, September 14, 2016 02:27:47 PM Stephen Rothwell wrote:
> > Hi Rafael,
> >
> > After merging the pm tree, today's linux-next build (powerpc allyesconfig)
> > failed like this:
> >
> > drivers/devfreq/tegra-devfreq.c: In function 'tegra_devfreq_target':
> > drivers/devfreq/tegra-devfreq.c:500:2: error: implicit declaration of function 'clk_set_min_rate' [-Werror=implicit-function-declaration]
> > clk_set_min_rate(tegra->emc_clock, rate);
> > ^
> >
> > Caused by commit
> >
> > 797da5598f3a ("PM / devfreq: Add COMPILE_TEST for build coverage")
@Rafael: Thank you!
@Kozlowski:
It looks like COMMON_CLK is required to be "selected" for TEGRA.
Although COMMON_CLK is supposed to be widely used by most ARM platforms
especially if "Multiple platfrom selection" for ARMv7 is used,
COMPILE_TEST won't recognize it.
Adding COMMON_CLK for TEGRA will solve this instance of issue; however,
for COMPILE_TEST to be reasonably robust, each "COMPILE_TEST"ed item
should "select" every required item. How do you want to proceed with
COMPILE_TEST on SoC-specific device drivers?
Cheers,
MyungJoo.
> >
> > clk_set_min_rate() usage depends on CONFIG_HAVE_CLK.
> >
> > I added the following for today:
> >
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Wed, 14 Sep 2016 14:22:25 +1000
> > Subject: [PATCH] partial revert of 797da5598f3a ("PM / devfreq: Add
> > COMPILE_TEST for build coverage")
> >
> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > ---
> > drivers/devfreq/Kconfig | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/devfreq/Kconfig b/drivers/devfreq/Kconfig
> > index cadd56e50b2c..93b6ada06676 100644
> > --- a/drivers/devfreq/Kconfig
> > +++ b/drivers/devfreq/Kconfig
> > @@ -92,7 +92,7 @@ config ARM_EXYNOS_BUS_DEVFREQ
> >
> > config ARM_TEGRA_DEVFREQ
> > tristate "Tegra DEVFREQ Driver"
> > - depends on ARCH_TEGRA_124_SOC || COMPILE_TEST
> > + depends on ARCH_TEGRA_124_SOC
> > select DEVFREQ_GOV_SIMPLE_ONDEMAND
> > select PM_OPP
> > help
>
> I've just gone ahead and applied it.
>
> Thanks Stephen!
>
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
linux-next: build failure after merge of the pm tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-09-14 06:30 +0200
Re: linux-next: build failure after merge of the pm tree "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-09-14 23:40 +0200
RE: Re: linux-next: build failure after merge of the pm tree MyungJoo Ham <myungjoo.ham@samsung.com> - 2016-09-19 09:40 +0200
Re: Re: linux-next: build failure after merge of the pm tree Krzysztof Kozlowski <krzk@kernel.org> - 2016-09-19 18:20 +0200
csiph-web