From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] ARM: tegra: Tegra114 needs CPU_FREQ_TABLE
Date: Fri, 03 May 2013 13:20:07 +0200 [thread overview]
Message-ID: <2416484.HHc7d0zNGR@wuerfel> (raw)
In-Reply-To: <CAOh2x==i-_+30mmMp=WkcCQn4qm1-nGfWpPuQnScvRQVd=h+LA@mail.gmail.com>
On Friday 03 May 2013 10:27:17 Viresh Kumar wrote:
> > diff --git a/arch/arm/mach-tegra/Kconfig b/arch/arm/mach-tegra/Kconfig
> > index 597e76b..9878503 100644
> > --- a/arch/arm/mach-tegra/Kconfig
> > +++ b/arch/arm/mach-tegra/Kconfig
> > @@ -63,6 +63,7 @@ config ARCH_TEGRA_114_SOC
> > select ARM_ARCH_TIMER
> > select ARM_GIC
> > select ARM_L1_CACHE_SHIFT_6
> > + select CPU_FREQ_TABLE if CPU_FREQ
> > select CPU_V7
> > select PINCTRL
> > select PINCTRL_TEGRA114
>
> I doubt which is the best place for doing this? This one or
> cpufreq/Kconfig.arm with select CPU_FREQ_TABLE for
> tegra?
It would be much better IMHO to have an entry for TEGRA_CPUFREQ
in drivers/cpufreq/Kcofnig.arm and move the select there. However,
creating that entry has some (small) regression potential and I
didn't want to do that now but instead just made sure that all
three Tegra SoCs do the same thing for now.
Arnd
next prev parent reply other threads:[~2013-05-03 11:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 21:02 [PATCH 0/9] arm-soc: randconfig fixes Arnd Bergmann
2013-05-02 21:02 ` [PATCH 1/9] ARM: tegra: Tegra114 needs CPU_FREQ_TABLE Arnd Bergmann
2013-05-03 4:57 ` Viresh Kumar
2013-05-03 11:20 ` Arnd Bergmann [this message]
2013-05-03 12:06 ` Viresh Kumar
2013-05-02 21:02 ` [PATCH 2/9] ARM: OMAP: build SMP code only for OMAP4/5 Arnd Bergmann
2013-05-02 23:30 ` Tony Lindgren
2013-05-02 21:02 ` [PATCH 3/9] ARM: imx: build CPU suspend code only when needed Arnd Bergmann
2013-05-02 21:02 ` [PATCH 4/9] ARM: SPEAr: conditionalize l2x0 support Arnd Bergmann
2013-05-02 21:02 ` [PATCH 5/9] ARM: imx: reset_controller may be disabled Arnd Bergmann
2013-05-02 21:02 ` [PATCH 6/9] ARM: SPEAr: conditionalize SMP code Arnd Bergmann
2013-05-02 21:02 ` [PATCH 7/9] ARM: OMAP: don't select SERIAL_OMAP unconditionally Arnd Bergmann
2013-05-02 23:32 ` Tony Lindgren
2013-05-03 20:34 ` Arnd Bergmann
2013-05-03 21:04 ` Tony Lindgren
2013-05-02 21:02 ` [PATCH 8/9] ARM: SIRF: select SMP_ON_UP only on SMP builds Arnd Bergmann
2013-05-02 21:02 ` [PATCH 9/9] ARM: ux500: always select ABX500_CORE Arnd Bergmann
2013-05-03 8:14 ` Linus Walleij
2013-05-03 11:28 ` Arnd Bergmann
2013-05-03 12:13 ` Linus Walleij
2013-05-03 12:48 ` Arnd Bergmann
2013-05-03 13:33 ` Linus Walleij
2013-05-03 13:56 ` Arnd Bergmann
2013-05-03 14:06 ` Linus Walleij
2013-05-03 14:20 ` Arnd Bergmann
2013-05-03 18:43 ` Linus Walleij
2013-05-03 19:38 ` Arnd Bergmann
2013-05-03 4:55 ` [PATCH 0/9] arm-soc: randconfig fixes Viresh Kumar
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=2416484.HHc7d0zNGR@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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