Re: [PATCH 3/6] mfd: intel_msic: Make it explicitly non-modular

From	Mika Westerberg <mika.westerberg@linux.intel.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH 3/6] mfd: intel_msic: Make it explicitly non-modular
Date	2016-07-07 12:40 +0200
Message-ID	<rSeSR-5H4-7@gated-at.bofh.it> (permalink)
References	(1 earlier) <rRnlw-4AT-19@gated-at.bofh.it> <rRvsJ-1qm-3@gated-at.bofh.it> <rRY1I-369-25@gated-at.bofh.it> <rScHp-4lY-45@gated-at.bofh.it> <rSeJc-5D9-25@gated-at.bofh.it>
Organization	Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo

Show all headers | View raw

On Thu, Jul 07, 2016 at 01:26:35PM +0300, Andy Shevchenko wrote:
> On Thu, 2016-07-07 at 11:11 +0300, Mika Westerberg wrote:
> > On Wed, Jul 06, 2016 at 12:38:00PM -0400, Paul Gortmaker wrote:
> > > [Re: [PATCH 3/6] mfd: intel_msic: Make it explicitly non-modular] On
> > > 05/07/2016 (Tue 13:08) Mika Westerberg wrote:
> > > 
> > > > On Mon, Jul 04, 2016 at 09:25:41PM -0400, Paul Gortmaker wrote:
> > > > > The Kconfig currently controlling compilation of this code is:
> > > > > 
> > > > > drivers/mfd/Kconfig:config MFD_INTEL_MSIC
> > > > > drivers/mfd/Kconfig:    bool "Intel MSIC"
> > > > 
> > > > I would prefer if it could be turned to tristate instead. I don't
> > > > see
> > > > any reasons why it should only be builtin.
> > > 
> > > If I change it to tristate, it is still impossible to choose =m for
> > > it
> > > unless I revert your earlier commit forcing it to be built in.
> > > 
> > > commit 15a713df4145ad2540f8d84c3f4de930806f6151
> > > Author: Mika Westerberg <mika.westerberg@linux.intel.com>
> > > Date:   Thu Jan 26 17:35:05 2012 +0000
> > > 
> > >     x86/config: Select MSIC MFD driver on Intel Medfield platform
> > >     
> > >     On Intel Medfield platform we use MSIC MFD driver to create
> > >     necessary platform devices so it is essential to have the driver
> > >     compiled into the kernel.
> > > 
> > > If I revert that, then it is possible to choose =m and it compiles.
> > > (haven't completed modpost yet.. so may be missing symbols...)
> > 
> > I think we can revert that and make it modular. Adding Andy just in
> > case
> > I'm missing something obvious.
> 
> I doubt we may do this. The MID platforms MSIC used for some voltage
> regulations and other stuff, moreover it exports an API which might be
> used by the code which can be (for now) only compiled in. I wouldn't
> take a headache to convert users and check all possible Kconfig
> variations (check this gpio-msic.c).

OK, thanks Andy.

So I withdraw my comment about tristating the driver. Let's make it
explictly non-modular then.

For the patch,

Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH 3/6] mfd: intel_msic: Make it explicitly non-modular Paul Gortmaker <paul.gortmaker@windriver.com> - 2016-07-05 03:30 +0200
  Re: [PATCH 3/6] mfd: intel_msic: Make it explicitly non-modular Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-07-05 12:10 +0200
    Re: [PATCH 3/6] mfd: intel_msic: Make it explicitly non-modular Paul Gortmaker <paul.gortmaker@windriver.com> - 2016-07-06 18:40 +0200
      Re: [PATCH 3/6] mfd: intel_msic: Make it explicitly non-modular Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-07-07 10:20 +0200
        Re: [PATCH 3/6] mfd: intel_msic: Make it explicitly non-modular Andy Shevchenko <andriy.shevchenko@linux.intel.com> - 2016-07-07 12:30 +0200
          Re: [PATCH 3/6] mfd: intel_msic: Make it explicitly non-modular Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-07-07 12:40 +0200

csiph-web