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
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 internal
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 following patch?
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 investigate if
On February 24, 2014 2:26:58 PM GMT+00:00, Alexandre Belloni
alexandre.bell...@free-electrons.com 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
On Friday, January 10, 2014 at 09:55:45 AM, Jürgen Beisert wrote:
[...]
While this is not necessarily an issue with ts_calibrate (it is possible
to click longer so it collects more samples), I don't see that working
with xinput_calibrator.
While I don't have much experience with the
Hi,
Sorry to chime in only now but it seems that this series is breaking the
touchscreen calibration on 3.13 (and -rc7 is out so it might be too
late).
At first, I though I became a terrible clicker ;) but I found some
evidences:
xinput_calibrator is complaining about misclicks, debug output:
Dear Jonathan Cameron,
I'm looking for some Tested-by: or Acks on this before applying the series.
I got the impression from the comments on the previous version that the
series has now been reasonably thoroughly tested on both i.MX28 and i.MX23
boards. This is not yet reflected in the sign
The following series replaces the current busy loop touchscreen implementation
for i.MX28/i.MX23 SoCs by a fully interrupt driven implementation.
Since i.MX23 and i.MX28 silicon differs, the existing implementation can
be used for the i.MX28 SoC only.
The first patch adds proper clock handling.
Dear Juergen Beisert,
The following series replaces the current busy loop touchscreen
implementation for i.MX28/i.MX23 SoCs by a fully interrupt driven
implementation.
Since i.MX23 and i.MX28 silicon differs, the existing implementation can
be used for the i.MX28 SoC only.
The first
10 matches
Mail list logo