[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160620151954.0c9094db@lxorguk.ukuu.org.uk>
Date: Mon, 20 Jun 2016 15:19:54 +0100
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Jiri Kosina <jikos@...nel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
jic23@...nel.org, benjamin.tissoires@...hat.com,
linux-input@...r.kernel.org, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, chaya.golan@...el.com,
daniel.drubin@...el.com, A.Bhattacharya@....ac.be
Subject: Re: [PATCH 2/6] hid: intel_ish-hid: ISH Transport layer
On Mon, 20 Jun 2016 11:29:28 +0200 (CEST)
Jiri Kosina <jikos@...nel.org> wrote:
> On Fri, 17 Jun 2016, Srinivas Pandruvada wrote:
>
> > > > +config INTEL_ISH_HID_TRANSPORT
> > > > + bool
> > > > + default n
> > > > +
> > > > +config INTEL_ISH_HID
> > > > + bool "Intel Integrated Sensor Hub"
> > >
> > > Why can't the transport driver be built as a module?
> > In current use case for PM, we don't want anyone to unload and
> > complain.
>
> Sorry, I don't understand this explanation, could you please elaborate?
If the driver isn't loaded your machine doesn't do power management.
There are a small set of drivers that need to be loaded to get pm even if
not using that device. ISH is one of them, and unlike the others not
sucked into a standard configuration.
If it's going to get loaded due to the presence of the PCI identifiers on
any normal distribution then it's in the same category as graphics and
ADSP based audio, both of which can be modules and the only real world
impact is they get loaded a second or two later during boot.
Alan
Powered by blists - more mailing lists