X86 platform drivers
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Darren Hart <dvhart@infradead.org>, Andy Shevchenko <andy@infradead.org>
Cc: platform-driver-x86@vger.kernel.org,
	Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: intel_turbo_max_3 non-modularity
Date: Mon, 24 Apr 2017 11:31:03 +0200	[thread overview]
Message-ID: <20170424113103.0de3ea31@endymion> (raw)

Hi all,

I see that the intel_turbo_max_3 driver was originally supposed to be
modular, and then support for that possibility was removed. Is there
any fundamental reason why this driver can't be built as a module?

I am asking because the description of the driver says:

"This driver is only required when the system is not using Hardware
P-States (HWP). In HWP mode, priority can be read from ACPI tables."

This pretty much implies that this driver will be useless on a wide
range (maybe even the majority?) of systems. Given this, not being
forced to build the driver into the kernel would seem preferable.

Thanks,
-- 
Jean Delvare
SUSE L3 Support

             reply	other threads:[~2017-04-24  9:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24  9:31 Jean Delvare [this message]
2017-04-24 14:02 ` intel_turbo_max_3 non-modularity Paul Gortmaker
2017-04-27 21:48   ` Darren Hart
2017-04-27 23:18     ` Srinivas Pandruvada
2017-04-28  7:55       ` Peter Zijlstra
2017-04-28 13:20         ` Jean Delvare
2017-04-28 13:46           ` Peter Zijlstra
2017-04-28 15:49             ` Darren Hart
2017-04-28 16:34               ` Peter Zijlstra
2017-04-28 20:58                 ` Darren Hart
2017-04-28 21:39                   ` Peter Zijlstra
2017-04-28  8:40       ` Jean Delvare
2017-04-28 20:35         ` Srinivas Pandruvada
2017-04-28  7:49   ` Jean Delvare
2017-04-28 17:44     ` Paul Gortmaker
2017-04-28 20:49       ` Darren Hart
2017-04-28 21:34         ` Peter Zijlstra
2017-04-28 22:51           ` Darren Hart

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=20170424113103.0de3ea31@endymion \
    --to=jdelvare@suse.de \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=platform-driver-x86@vger.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