mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	Felipe Balbi <balbi@ti.com>,
	x86@kernel.org, aubrey.li@linux.intel.com
Subject: Re: [Patch v2] x86: Make Atom PMC driver configurable.
Date: Thu, 16 Oct 2014 07:24:48 +0200	[thread overview]
Message-ID: <20141016052448.GB14796@gmail.com> (raw)
In-Reply-To: <20141016021859.GA12042@redhat.com>


* Dave Jones <davej@redhat.com> 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>
> Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
> Cc: aubrey.li@linux.intel.com
> 
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index f2327e88e07c..b4dfd96aeea8 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -2485,7 +2485,8 @@ config X86_DMA_REMAP
>  	depends on STA2X11
>  
>  config PMC_ATOM
> -	def_bool y
> +	tristate "Intel Atom SOC power management controller driver"
> +	default y
>          depends on PCI
>  

So what I think should happen is to decouple of the 'must work' 
features from the optional debug features in this 'driver': the 
Atom SoC power-off quirk should be made unconditional, as long as 
the .config is Atom-supported (CPU_SUP_INTEL I guess).

All the other bits, such as the debugfs interface, should be in a 
separately and appropriately named config option, 
CONFIG_X86_INTEL_ATOM_PMC_DEBUG=y or so, with 'default n'.

The file should probably be split up, the quirk moved into one of 
the generic quirk files, while pmc_atom.c should have the debugfs 
interface.

That way we don't break anyone and remove the unnecessary code as 
well. It's also a nice clean up.

Thanks,

	Ingo

  parent reply	other threads:[~2014-10-16  5:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 14:46 Dave Jones
2014-10-15 14:52 ` Felipe Balbi
2014-10-15 14:59   ` Dave Jones
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 [this message]
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=20141016052448.GB14796@gmail.com \
    --to=mingo@kernel.org \
    --cc=aubrey.li@linux.intel.com \
    --cc=balbi@ti.com \
    --cc=davej@redhat.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome