From: Dave Jones <davej@redhat.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
x86@kernel.org, aubrey.li@linux.intel.com
Subject: Re: x86: Make Atom PMC driver configurable.
Date: Wed, 15 Oct 2014 10:59:24 -0400 [thread overview]
Message-ID: <20141015145924.GA21199@redhat.com> (raw)
In-Reply-To: <20141015145245.GB11511@saruman>
On Wed, Oct 15, 2014 at 09:52:45AM -0500, Felipe Balbi wrote:
> Hi,
>
> On Wed, Oct 15, 2014 at 10:46:03AM -0400, Dave Jones wrote:
> > The Atom PMC driver is always built-in, regardless of whether
> > the kernel being built is going to be run on an Atom (or even Intel) CPU.
> >
> > Signed-off-by: Dave Jones <davej@redhat.com>
> >
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index f2327e88e07c..04280177c1e2 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -2485,7 +2485,7 @@ config X86_DMA_REMAP
> > depends on STA2X11
> >
> > config PMC_ATOM
> > - def_bool y
> > + tristate "Intel Atom SOC power management controller driver"
>
> looks like you should still have this as default y just to make sure you
> a simple defconfig still enables this as it did before.
I could, but why should this be default y ? There's no real
justification to inflict this on everyone, given atom is at best
a niche area of x86.
Dave
next prev parent reply other threads:[~2014-10-15 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 14:46 x86: Make Atom PMC driver configurable Dave Jones
2014-10-15 14:52 ` Felipe Balbi
2014-10-15 14:59 ` Dave Jones [this message]
2014-10-15 15:04 ` Felipe Balbi
2014-10-15 16:20 ` One Thousand Gnomes
2014-10-16 2:18 ` [Patch v2] " Dave Jones
2014-10-16 3:00 ` Li, Aubrey
2014-10-16 3:04 ` Dave Jones
2014-10-16 5:24 ` Ingo Molnar
2014-10-16 5:35 ` Li, Aubrey
2014-10-16 21:54 ` Guenter Roeck
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=20141015145924.GA21199@redhat.com \
--to=davej@redhat.com \
--cc=aubrey.li@linux.intel.com \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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 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.