[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170126100506.5edf26e3@endymion>
Date: Thu, 26 Jan 2017 10:05:06 +0100
From: Jean Delvare <jdelvare@...e.de>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: linux-gpio@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Linus Walleij <linus.walleij@...aro.org>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Takashi Iwai <tiwai@...e.de>,
Paul Gortmaker <paul.gortmaker@...driver.com>
Subject: Re: [PATCH RESEND] pinctrl: intel: Turn Baytrail support to
tristate
Hi Mika and all,
On Wed, 25 Jan 2017 18:16:51 +0200, Mika Westerberg wrote:
> On Wed, Jan 25, 2017 at 04:26:08PM +0100, Jean Delvare wrote:
> > The pinctrl-baytrail driver builds just fine as a module so give
> > users this option.
> >
> > Signed-off-by: Jean Delvare <jdelvare@...e.de>
> > Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>
>
> Assuming you have checked that nothing breaks in Baytrail, I'm fine with
> this change,
I have not, as I do not have access to any Baytrail hardware. This is
the very reason why I'd like this code to be buildable as a module: I'm
not happy with a useless 50 kB driver being loaded on all my systems. I
was hopping someone at Intel would have access to the hardware to
perform the test.
Meanwhile I have found that my patch is not good, because since I wrote
it, Paul Gortmaker remove the module glue code from the driver itself:
commit 360943a8d26265825025b88da32961bd9ad4f7c6
Author: Paul Gortmaker <paul.gortmaker@...driver.com>
Date: Mon Jun 6 22:43:01 2016 -0400
pinctrl: baytrail: make it explicitly non-modular
This would have to be reverted first. Paul, do I understand it
correctly that the commit above was generated automatically and was not
specific to the pinctrl-baytrail driver?
--
Jean Delvare
SUSE L3 Support
Powered by blists - more mailing lists