> > > Sent: Friday, September 29, 2017 3:37 PM
> > > To: Dmitry Torokhov
> > > Cc: Greg Kroah-Hartman ; Tejun Heo
> > > ; Linux Kernel Mailing List > > ker...@vger.kernel.org>; Guenter Roeck ; Ruhl,
> > > Michael J
> > >
ov
> > Cc: Greg Kroah-Hartman ; Tejun Heo
> > ; Linux Kernel Mailing List > ker...@vger.kernel.org>; Guenter Roeck ; Ruhl,
> > Michael J
> > Subject: Re: [PATCH v2 1/7] driver core: emit uevents when device is bound
> > to a driver
> >
> > On Wed, Jul
l.org>; Guenter Roeck ; Ruhl,
> Michael J
> Subject: Re: [PATCH v2 1/7] driver core: emit uevents when device is bound
> to a driver
>
> On Wed, Jul 19, 2017 at 5:24 PM, Dmitry Torokhov
> wrote:
> > There are certain touch controllers that may come up in either nor
On Wed, Jul 19, 2017 at 5:24 PM, Dmitry Torokhov
wrote:
> There are certain touch controllers that may come up in either normal
> (application) or boot mode, depending on whether firmware/configuration is
> corrupted when they are powered on. In boot mode the kernel does not create
> input device
There are certain touch controllers that may come up in either normal
(application) or boot mode, depending on whether firmware/configuration is
corrupted when they are powered on. In boot mode the kernel does not create
input device instance (because it does not necessarily know the
characteristic
5 matches
Mail list logo