On Wed, Feb 01, 2017 at 11:25:31AM -0600, Rob Herring wrote:
> On Tue, Jan 31, 2017 at 08:55:19AM +0100, Hans Holmberg wrote:
> > +
> > + gpio-joystick: {
>
> Why do we need a whole new example?
I found it motivated to describe a use case with the new property, since
it is very different from
On Wed, Feb 01, 2017 at 11:25:31AM -0600, Rob Herring wrote:
> On Tue, Jan 31, 2017 at 08:55:19AM +0100, Hans Holmberg wrote:
> > +
> > + gpio-joystick: {
>
> Why do we need a whole new example?
I found it motivated to describe a use case with the new property, since
it is very different from
On Tue, Jan 31, 2017 at 08:55:19AM +0100, Hans Holmberg wrote:
> This change adds support for specifying device tree buttons emitting
> abs/rel events.
>
> ABS events were previously supported, but only via platform data, so add
> the missing device tree property to allow axis values to be
On Tue, Jan 31, 2017 at 08:55:19AM +0100, Hans Holmberg wrote:
> This change adds support for specifying device tree buttons emitting
> abs/rel events.
>
> ABS events were previously supported, but only via platform data, so add
> the missing device tree property to allow axis values to be
This change adds support for specifying device tree buttons emitting
abs/rel events.
ABS events were previously supported, but only via platform data, so add
the missing device tree property to allow axis values to be emitted with
abs/rel events.
Also emit 0 on button releases for REL and ABS
This change adds support for specifying device tree buttons emitting
abs/rel events.
ABS events were previously supported, but only via platform data, so add
the missing device tree property to allow axis values to be emitted with
abs/rel events.
Also emit 0 on button releases for REL and ABS
6 matches
Mail list logo
