All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco <koansoftware@gmail.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: tslib not working with daisy
Date: Mon, 16 Jun 2014 10:10:09 +0200	[thread overview]
Message-ID: <539EA661.2020008@gmail.com> (raw)
In-Reply-To: <5399BAAF.4040200@gmail.com>

Il 12/06/2014 16:35, Marco ha scritto:
> Note: This thread was "[meta-freescale] tslib calibration issue"
>
> Hi
> I am building minimal-image for imx6dlsabresd.
>
> Build Configuration:
> BB_VERSION        = "1.22.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-12.04"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "imx6dlsabresd"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.6"
> TUNE_FEATURES     = "armv7a vfp neon callconvention-hard cortexa9"
> TARGET_FPU        = "vfp-neon"
> meta
> meta-yocto
> meta-yocto-bsp    = "daisy:62b1fef7875a6f9c55344fa6bcc7d4b6672eac1f"
> meta-oe           = "daisy:dca466c074c9a35bc0133e7e0d65cca0731e2acf"
> meta-fsl-arm      = "daisy:f5bf277a5a5fba2c3b64ed7d2dbec1903d96386b"
> meta-fsl-demos    = "daisy:27fdb2f2642ecd55d5633bde880dd4c37acd0d42"
>
> When I used branch dora the tslib and ts_calibrate worked.
> Now using daisy ts_calibrate doesn't work, ts_print doesn't work, only
> ts_print_raw is working.
> It has set by default TSLIB_TSDEVICE=/dev/input/touchscreen0
>
> I added some debug information into tslib and discovered that the
> pressure signal is missing so probably the problem is the kernel
> settings (maybe a misconfiguration in DT).
>
> root@imx6dlsabresd:~# ts_print_raw
> 1402072658.126525:  20368  15584      0
> 1402072658.137927:  20368  15584      0
> 1402072658.149310:  20368  15584      0
>
>
> root@imx6dlsabresd:~# ts_print
> LINEAR ts_input_read
> RAW ts_input_read
> RAW---------------------> 21360 22528 0 1402072702.766665
> LINEAR ts_input_read
> RAW ts_input_read
> RAW---------------------> 21360 22528 0 1402072702.778067
> LINEAR ts_input_read
> RAW ts_input_read
> RAW---------------------> 21360 22528 0 1402072702.789462
>
>
> What have you changed in daisy or linux-3.10.17 that broke the touchscreen?
> Anybody tested the new image with a imx6dlsabresd?
> What do you think?
>
> TIA


More details

root@imx6dlsabresd# evtest /dev/input/touchscreen0
Input driver version is 1.0.1
Input device ID: bus 0x18 vendor 0xeef product 0x20 version 0x1
Input device name: "eGalax Touch Screen"
Supported events:
   Event type 0 (Sync)
   Event type 1 (Key)
     Event code 330 (Touch)
   Event type 3 (Absolute)
     Event code 0 (X)
       Value      0
       Min        0
       Max    32767
     Event code 1 (Y)
       Value      0
       Min        0
       Max    32767
     Event code 24 (Pressure)
       Value      0
       Min        0
       Max        1
     Event code 48 (Touch Major)
       Value      0
       Min        0
       Max      255
     Event code 50 (Width Major)
       Value      0
       Min        0
       Max      255
     Event code 53 (Position X)
       Value      0
       Min        0
       Max    32767
     Event code 54 (Position Y)
       Value      0
       Min        0
       Max    32767
     Event code 57 (Tracking ID)
       Value      0
       Min        0
       Max        5
Testing ... (interrupt to exit)

Event: time 1402822407.489433, type 3 (Absolute), code 57 (Tracking ID), 
value 0
Event: time 1402822407.489433, type 3 (Absolute), code 48 (Touch Major), 
value 1
Event: time 1402822407.489433, type 3 (Absolute), code 53 (Position X), 
value 20704
Event: time 1402822407.489433, type 3 (Absolute), code 54 (Position Y), 
value 19408
Event: time 1402822407.489433, -------------- Config Sync ------------
Event: time 1402822407.489433, -------------- Report Sync ------------
Event: time 1402822407.500802, type 3 (Absolute), code 57 (Tracking ID), 
value 0
Event: time 1402822407.500802, type 3 (Absolute), code 48 (Touch Major), 
value 1
Event: time 1402822407.500802, type 3 (Absolute), code 53 (Position X), 
value 20704
Event: time 1402822407.500802, type 3 (Absolute), code 54 (Position Y), 
value 19408
Event: time 1402822407.500802, -------------- Config Sync ------------
Event: time 1402822407.500802, -------------- Report Sync ------------
Event: time 1402822407.512211, type 3 (Absolute), code 57 (Tracking ID), 
value 0
Event: time 1402822407.512211, type 3 (Absolute), code 48 (Touch Major), 
value 1
Event: time 1402822407.512211, type 3 (Absolute), code 53 (Position X), 
value 20704
Event: time 1402822407.512211, type 3 (Absolute), code 54 (Position Y), 
value 19408
Event: time 1402822407.512211, -------------- Config Sync ------------
Event: time 1402822407.512211, -------------- Report Sync ------------
Event: time 1402822407.539138, type 3 (Absolute), code 57 (Tracking ID), 
value 0
Event: time 1402822407.539138, type 3 (Absolute), code 48 (Touch Major), 
value 1
Event: time 1402822407.539138, type 3 (Absolute), code 53 (Position X), 
value 20672
Event: time 1402822407.539138, type 3 (Absolute), code 54 (Position Y), 
value 19520
Event: time 1402822407.539138, -------------- Config Sync ------------
Event: time 1402822407.539138, -------------- Report Sync ------------
Event: time 1402822407.540674, type 3 (Absolute), code 57 (Tracking ID), 
value 0
Event: time 1402822407.540674, type 3 (Absolute), code 48 (Touch Major), 
value 0
Event: time 1402822407.540674, -------------- Config Sync ------------
Event: time 1402822407.540674, -------------- Report Sync ------------


Any clue?
--
Marco


      reply	other threads:[~2014-06-16  8:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 14:35 tslib not working with daisy Marco
2014-06-16  8:10 ` Marco [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=539EA661.2020008@gmail.com \
    --to=koansoftware@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.