[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ada63f5a6815410d8227d1369c37a796@ausx13mpc120.AMER.DELL.COM>
Date: Mon, 5 Jun 2017 15:50:24 +0000
From: <Mario.Limonciello@...l.com>
To: <mika.westerberg@...ux.intel.com>, <gregkh@...uxfoundation.org>
Cc: <andriy.shevchenko@...ux.intel.com>, <lukas@...ner.de>,
<andreas.noever@...il.com>, <michael.jamet@...el.com>,
<yehezkel.bernat@...el.com>, <amir.jer.levy@...el.com>,
<luto@...nel.org>, <Jared.Dominguez@...l.com>,
<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v3 19/27] thunderbolt: Add new Thunderbolt PCI IDs
> -----Original Message-----
> From: Mika Westerberg [mailto:mika.westerberg@...ux.intel.com]
> Sent: Monday, June 5, 2017 10:41 AM
> To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>; Lukas Wunner
> <lukas@...ner.de>; Andreas Noever <andreas.noever@...il.com>; Michael
> Jamet <michael.jamet@...el.com>; Yehezkel Bernat <yehezkel.bernat@...el.com>;
> Amir Levy <amir.jer.levy@...el.com>; Andy Lutomirski <luto@...nel.org>;
> Limonciello, Mario <Mario_Limonciello@...l.com>; Dominguez, Jared
> <Jared_Dominguez@...L.com>; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH v3 19/27] thunderbolt: Add new Thunderbolt PCI IDs
>
> On Mon, Jun 05, 2017 at 05:20:36PM +0200, Greg Kroah-Hartman wrote:
> > On Mon, Jun 05, 2017 at 05:21:34PM +0300, Andy Shevchenko wrote:
> > > On Mon, 2017-06-05 at 16:33 +0300, Mika Westerberg wrote:
> > > > On Mon, Jun 05, 2017 at 03:55:07PM +0300, Mika Westerberg wrote:
> > > > > >
> > >
> > > > It turns out that this is not too big change after all so I think it
> > > > can
> > > > be included in the ICM patch if you want.
> > > >
> > > > Basically we would have module parameter:
> > > >
> > > > cm=auto|native|icm
> > > >
> > > > where auto is the default.
> > > >
> > > > Does that work?
> > >
> > >
> > > I remember Greg is opposite to being fan of module parameters in new
> > > code, so, please, if you are still going to do that, do it a separate
> > > patch which will be last in the series and can be discussed separately
> > > w.o. preventing everything else being applied.
> >
> > Yes, you should never need module parameters in "modern" code. As no
> > one will ever set them, or know what to do here. Make it "automatic"
> > please.
>
> Well in current series it is already automatic :-)
>
> What Lukas wants here is a way to force a certain connection manager
> implementation to be used instead.
And presumably that's mostly for debugging purposes and will lead
to additional quirks to get "automatic" to do the right thing on those
machines that's it's found to be needed or more beneficial.
Powered by blists - more mailing lists