From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Daiane Angolini <daiane.list@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH v2] linux-imx_3.0.35: Support Single Pointer into the eGalax Touchscreen Driver
Date: Fri, 18 Jan 2013 07:27:31 -0700 [thread overview]
Message-ID: <50F95BD3.4020101@boundarydevices.com> (raw)
In-Reply-To: <CA+jg_OWEnZb32CR_KhCPiQ_uGPcj9V4_r9n2Z99ZO-7q50=a2A@mail.gmail.com>
On 01/18/2013 03:23 AM, Daiane Angolini wrote:
> On Thu, Jan 17, 2013 at 7:47 PM, Leonardo Sandoval
> <leonardo.sandoval@freescale.com> wrote:
>> This patch enables the touchscreen functionality on i.MX6 Sabre Platforms using the
>> eGalax Driver.
>>
>> [YOCTO #3573]
>>
>> Upstream-Status: Submitted [meta-freescale@yoctoproject.org]
>>
>> Changed since v1:
>> - Included Upstream-Status as Otavio suggestion
>>
>> Signed-off-by: Leonardo Sandoval <leonardo.sandoval@freescale.com>
>> ---
>
> Your V2 is very nice!
>
> Could you, please, share which board you tested?
>
I can confirm by inspection that this works. We've tested single-touch
support on all of our i.MX6 boards and Leonardo's patch just adds the
macro definition to enable it.
I would recommend to the Freescale team that this should really be a
Kconfig switch as done here:
https://github.com/boundarydevices/linux-imx6/commit/f6b560538edca833481c1d67ecf3cfe2d65c4018
Then the userspace can select based on the configuration file, so
a multi-touch enabled userspace can select that feature. I'm sure
that Yocto will contain support for multi-touch userspaces if it
doesn't already.
Regards,
Eric
next prev parent reply other threads:[~2013-01-18 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 21:47 [meta-fsl-arm][PATCH v2] linux-imx_3.0.35: Support Single Pointer into the eGalax Touchscreen Driver Leonardo Sandoval
2013-01-18 10:23 ` Daiane Angolini
2013-01-18 14:27 ` Eric Nelson [this message]
2013-01-18 19:42 ` Otavio Salvador
2013-01-18 11:03 ` Otavio Salvador
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=50F95BD3.4020101@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=daiane.list@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.