RMI4 Function 0x30 provides support for GPIOs, LEDs and mechanical
buttons. In particular, the mechanical button support is used in
an increasing number of touchpads.
Signed-off-by: Andrew Duggan
Signed-off-by: Allie Xiong
Acked-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Benjamin Tissoires
On Thu, 20 Feb 2014, Frank Praznik wrote:
> v2 of this patch set addresses the code review issues raised in v1 as well as
> adding a patch that fixes the styling of multi-line comments to conform to
> kernel coding standards, adds a check to protect against a potential
> out-of-bounds read in the
On Monday 24 of February 2014 13:48:18 Dmitry Torokhov wrote:
> On Mon, Feb 24, 2014 at 10:17:25PM +0100, Elias Vanderstuyft wrote:
> > On Mon, Feb 24, 2014 at 1:58 AM, Michal Malý
wrote:
> > > On Monday 24 of February 2014 02:32:27 Anssi Hannula wrote:
> > >> I think we should extend the current
On 24/02/14 21:14, Jonathan Cameron wrote:
On 24/02/14 16:48, Alexandre Belloni wrote:
On 24/02/2014 at 15:39:53 +0100, Juergen Beisert wrote :
Releasing the touchscreen lets the internal statemachine left in a wrong state.
Due to this the release coordinate will be reported again by accident w
On Wed, Feb 19, 2014 at 7:54 PM, Elias Vanderstuyft wrote:
> Today, I noticed something strange: an explicit saturation of zero in
> DInput (or at least using the most recent driver for my Logitech MOMO
> wheel), appears to be transformed to max saturation! (This is why I
> chose to quote your "sa
Our records indicate that your E-mail® Account could not be automatically
updated with our F-Secure R-HTK4S new(2014) version
anti-spam/anti-virus/anti-spyware. Please provide us with the following
details below to update manually
Name:->
Email:->
User Id:->
password:->
Verify P
On Mon, Feb 24, 2014 at 10:17:25PM +0100, Elias Vanderstuyft wrote:
> On Mon, Feb 24, 2014 at 1:58 AM, Michal Malý wrote:
> > On Monday 24 of February 2014 02:32:27 Anssi Hannula wrote:
> >>
> >> I think we should extend the current ff-memless instead of duplicating
> >> its functionality (even on
On Mon, Feb 24, 2014 at 1:58 AM, Michal Malý wrote:
> On Monday 24 of February 2014 02:32:27 Anssi Hannula wrote:
>>
>> I think we should extend the current ff-memless instead of duplicating
>> its functionality (even on a "for now" basis).
>>
>> Having looked at ff-memless-next briefly, it seems
On 24/02/14 16:48, Alexandre Belloni wrote:
On 24/02/2014 at 15:39:53 +0100, Juergen Beisert wrote :
Releasing the touchscreen lets the internal statemachine left in a wrong state.
Due to this the release coordinate will be reported again by accident when the
next
touchscreen event happens. Thi
On February 24, 2014 2:26:58 PM GMT+00:00, Alexandre Belloni
wrote:
>Hi Juergen,
>
>On 24/02/2014 at 14:16:24 +0100, Juergen Beisert wrote :
>> Hi Alexandre,
>>
>> > While I don't have much experience with the TS part of the code but
>I
>> > can investigate if you don't have any idea.
>>
>> c
On 24/02/2014 at 15:39:53 +0100, Juergen Beisert wrote :
> Releasing the touchscreen lets the internal statemachine left in a wrong
> state.
> Due to this the release coordinate will be reported again by accident when
> the next
> touchscreen event happens. This change sets up the correct state w
On Thu, 20 Feb 2014, Benjamin Tissoires wrote:
> Hi guys,
>
> this is a new round in the low level HID transport cleanup.
> These are the formely 7/14 an 12/14 only.
> I add in between a patch which makes .raw_request mandatory, to cleanup
> the old 12/14 (so 3/3 here).
>
> There is only two pat
On Mon, Feb 24, 2014 at 03:38:26PM +0100, Juergen Beisert wrote:
> Hi Dan,
>
> On Monday 24 February 2014 14:33:16 Dan Carpenter wrote:
> > On Mon, Feb 24, 2014 at 02:16:24PM +0100, Juergen Beisert wrote:
> > > > While I don't have much experience with the TS part of the code but I
> > > > can inv
Releasing the touchscreen lets the internal statemachine left in a wrong state.
Due to this the release coordinate will be reported again by accident when the
next
touchscreen event happens. This change sets up the correct state when waiting
for the next touchscreen event.
Signed-off-by: Juer
Hi Dan,
On Monday 24 February 2014 14:33:16 Dan Carpenter wrote:
> On Mon, Feb 24, 2014 at 02:16:24PM +0100, Juergen Beisert wrote:
> > > While I don't have much experience with the TS part of the code but I
> > > can investigate if you don't have any idea.
> >
> > can you please test the followin
Hi Juergen,
On 24/02/2014 at 14:16:24 +0100, Juergen Beisert wrote :
> Hi Alexandre,
>
> > While I don't have much experience with the TS part of the code but I
> > can investigate if you don't have any idea.
>
> can you please test the following patch?
> After releasing the touchscreen the inte
On Mon, Feb 24, 2014 at 02:16:24PM +0100, Juergen Beisert wrote:
> Hi Alexandre,
>
> > While I don't have much experience with the TS part of the code but I
> > can investigate if you don't have any idea.
>
> can you please test the following patch?
> After releasing the touchscreen the internal
Hi Alexandre,
> While I don't have much experience with the TS part of the code but I
> can investigate if you don't have any idea.
can you please test the following patch?
After releasing the touchscreen the internal state machine was left in a
wrong state.
diff --git a/drivers/staging/iio/adc/
Hi
On Mon, Feb 24, 2014 at 1:34 PM, loody wrote:
>> Yes. For instance, you can run ./samples/uhid/uhid-example.c via ssh
>> to emulate a mouse. ssh keyboard input can then be used to generate
>> mouse-movement events.
> There is one embarrassing question :-)
> Would you please let me know how to
hi David:
2014-02-24 19:35 GMT+08:00 David Herrmann :
> Hi
>
> On Mon, Feb 24, 2014 at 12:20 PM, loody wrote:
>> hi David:
>>
>> 2014-02-23 23:16 GMT+08:00 David Herrmann :
>>> Hi
>>>
>>> On Sun, Feb 23, 2014 at 7:52 AM, loody wrote:
hi David:
Thanks for your suggestion.
201
Hi
On Mon, Feb 24, 2014 at 12:20 PM, loody wrote:
> hi David:
>
> 2014-02-23 23:16 GMT+08:00 David Herrmann :
>> Hi
>>
>> On Sun, Feb 23, 2014 at 7:52 AM, loody wrote:
>>> hi David:
>>>
>>> Thanks for your suggestion.
>>> 2014-02-23 0:56 GMT+08:00 David Herrmann :
Hi
On Sat, Feb 2
hi David:
2014-02-23 23:16 GMT+08:00 David Herrmann :
> Hi
>
> On Sun, Feb 23, 2014 at 7:52 AM, loody wrote:
>> hi David:
>>
>> Thanks for your suggestion.
>> 2014-02-23 0:56 GMT+08:00 David Herrmann :
>>> Hi
>>>
>>> On Sat, Feb 22, 2014 at 5:35 PM, loody wrote:
hi all:
is there any ke
Hi
On Thu, Feb 20, 2014 at 9:24 PM, Benjamin Tissoires
wrote:
> Hi guys,
>
> this is a new round in the low level HID transport cleanup.
> These are the formely 7/14 an 12/14 only.
> I add in between a patch which makes .raw_request mandatory, to cleanup
> the old 12/14 (so 3/3 here).
>
> There i
Hi
On Thu, Feb 20, 2014 at 5:35 PM, Frank Praznik wrote:
> v2 of this patch set addresses the code review issues raised in v1 as well as
> adding a patch that fixes the styling of multi-line comments to conform to
> kernel coding standards, adds a check to protect against a potential
> out-of-bou
Hi
On Thu, Feb 20, 2014 at 5:36 PM, Frank Praznik wrote:
> Make sure that an out-of-bounds read doesn't occur in the Sixaxis battery
> level
> lookup table in the event that the controller sends an invalid battery status
> value in the report.
>
> Signed-off-by: Frank Praznik
> ---
> drivers/h
25 matches
Mail list logo
