From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Dmitry Torokhov
<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Fabio Estevam
<fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 3/4] iio: mxs: Implement support for touchscreen
Date: Thu, 13 Dec 2012 17:48:14 +0100 [thread overview]
Message-ID: <201212131748.14778.marex@denx.de> (raw)
In-Reply-To: <20121210222437.GA19008-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
Dear Dmitry Torokhov,
[...]
> > > +#define CHAN_MASK_TOUCHBUTTON (0x3 << 0)
> > > +#define CHAN_MASK_TOUCHSCREEN_4WIRE (0xf << 2)
> > > +#define CHAN_MASK_TOUCHSCREEN_5WIRE (0x1f << 2)
> > > + int use_touchbutton:1;
>
> Why would someone not want to use it?
The touchbutton is not present on many devices using the MX28. I'd like to
implement it in subsequent patch for completeleness though.
Jonathan, just a quick thought, but we're getting close to have MX233 Olinuxino
device supported as well (not my work, another guy is working on that I guess).
The device is very cheap, maybe you can get one? It also has this insane
touchscreen controller and all these cool insane parts ;-)
> > > + int use_touchscreen_4wire:1;
> > > + int use_touchscreen_5wire:1;
>
> This is weird. Can it be both 4 and 5 wires? I assume not, so using
> bits is not the best idea.
What do you say to "use_touchscreen" and "use_touchscreen_5wire" ? 5wire
touchscreen is special case, but it's easy to support it, so I dropped it in.
Or maybe make it enum?
TOUCHSCREEN_NONE = 0,
TOUCHSCREEN_4WIRE,
TOUCHSCREEN_5WIRE,
I like enum :)
[...]
Rest will be fixed in V2. Thanks for the review!
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-12-13 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1354893893-26338-1-git-send-email-marex@denx.de>
[not found] ` <1354893893-26338-3-git-send-email-marex@denx.de>
[not found] ` <1354893893-26338-3-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2012-12-08 10:13 ` [PATCH 3/4] iio: mxs: Implement support for touchscreen Jonathan Cameron
[not found] ` <50C312D8.4050405-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2012-12-08 21:18 ` Marek Vasut
[not found] ` <201212082218.19338.marex-ynQEQJNshbs@public.gmane.org>
2012-12-10 21:56 ` Jonathan Cameron
2012-12-13 16:56 ` Marek Vasut
2012-12-10 22:24 ` Dmitry Torokhov
2012-12-10 23:22 ` Marek Vasut
2012-12-11 8:18 ` Lothar Waßmann
[not found] ` <20121210222437.GA19008-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2012-12-13 16:48 ` Marek Vasut [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=201212131748.14778.marex@denx.de \
--to=marex-ynqeqjnshbs@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).