On Fri, May 01, 2015 at 04:13:55PM +0200, Bastien Nocera wrote:
> On Fri, 2015-05-01 at 14:40 +0200, Paul Cercueil wrote:
> > The MSB of the first byte read via I2C at the coordinates address
> > indicates whether the data is valid or ready (called "buffer status"
> > in
> > the datasheets) when
On Fri, May 01, 2015 at 04:13:55PM +0200, Bastien Nocera wrote:
On Fri, 2015-05-01 at 14:40 +0200, Paul Cercueil wrote:
The MSB of the first byte read via I2C at the coordinates address
indicates whether the data is valid or ready (called buffer status
in
the datasheets) when an
On Fri, 2015-05-01 at 14:40 +0200, Paul Cercueil wrote:
> The MSB of the first byte read via I2C at the coordinates address
> indicates whether the data is valid or ready (called "buffer status"
> in
> the datasheets) when an interrupt is raised. Previously, this bit was
> ignored, which resulted
The MSB of the first byte read via I2C at the coordinates address
indicates whether the data is valid or ready (called "buffer status" in
the datasheets) when an interrupt is raised. Previously, this bit was
ignored, which resulted in a lot of incorrect detections of "finger
removed" events.
On Fri, 2015-05-01 at 14:40 +0200, Paul Cercueil wrote:
The MSB of the first byte read via I2C at the coordinates address
indicates whether the data is valid or ready (called buffer status
in
the datasheets) when an interrupt is raised. Previously, this bit was
ignored, which resulted in a
The MSB of the first byte read via I2C at the coordinates address
indicates whether the data is valid or ready (called buffer status in
the datasheets) when an interrupt is raised. Previously, this bit was
ignored, which resulted in a lot of incorrect detections of finger
removed events.
6 matches
Mail list logo