From: Henrik Rydberg <rydberg@euromail.se>
To: chinyeow.sim.xt@renesas.com
Cc: tsoni@codeaurora.org, dmitry.torokhov@gmail.com,
linux-input@vger.kernel.org
Subject: Re: [PATCH v2] Input: add ST1232 touchscreen controller driver.
Date: Tue, 14 Dec 2010 10:47:26 +0100 [thread overview]
Message-ID: <4D073D2E.5040107@euromail.se> (raw)
In-Reply-To: <1292301289-12931-1-git-send-email-chinyeow.sim.xt@renesas.com>
Hi Tony,
Thanks for the resubmission. Indeed, the driver looks a lot better now.
> +
> +static void st1232_ts_work_func(struct work_struct *work)
> +{
> + int i, ret;
> + struct i2c_msg msg[2];
> + uint8_t start_reg;
> + uint8_t buf[10];
> + struct st1232_ts_data *ts =
> + container_of(work, struct st1232_ts_data, work.work);
> + uint16_t x[MAX_FINGERS], y[MAX_FINGERS];
> + uint8_t t[MAX_FINGERS];
> + uint8_t is_valid[MAX_FINGERS];
A lot of stack variables here - maybe there is something more that can be broken
out of the main function?
> +
> + /* read touchscreen data from ST1232 */
> + msg[0].addr = ts->client->addr;
> + msg[0].flags = 0;
> + msg[0].len = 1;
> + msg[0].buf = &start_reg;
> + start_reg = 0x10;
> +
> + msg[1].addr = ts->client->addr;
> + msg[1].flags = I2C_M_RD;
> + msg[1].len = sizeof(buf);
> + msg[1].buf = buf;
> +
> + ret = i2c_transfer(ts->client->adapter, msg, 2);
> + if (ret < 0)
> + goto done;
> +
> + /* get valid bit */
> + is_valid[XY0] = buf[2] >> 7;
> + is_valid[XY1] = buf[5] >> 7;
> +
> + /* get xy coordinate */
> + if (is_valid[XY0]) {
> + x[XY0] = ((buf[2] & 0x0070) << 4) | buf[3];
> + y[XY0] = ((buf[2] & 0x0007) << 8) | buf[4];
> + t[XY0] = buf[8];
> + }
> +
> + if (is_valid[XY1]) {
> + x[XY1] = ((buf[5] & 0x0070) << 4) | buf[6];
> + y[XY1] = ((buf[5] & 0x0007) << 8) | buf[7];
> + t[XY1] = buf[9];
> + }
Populating the x, y, and t variables looks like a candidate for a separate function.
> +
> + /* multi touch protocol */
> + for (i = 0; i < MAX_FINGERS; i++) {
> + if (!is_valid[i]) {
> + input_report_abs(ts->input_dev, ABS_MT_TOUCH_MAJOR, 0);
The type A protocol carries no state, so the above actually means nothing
without a position (and without the input_mt_sync). Ensuring t[i] is zero in
this code path would let you drop the test altogether, and also ensure that the
input_mt_syncs are sent properly.
> + continue;
> + }
> +
> + input_report_abs(ts->input_dev, ABS_MT_TOUCH_MAJOR, t[i]);
> + input_report_abs(ts->input_dev, ABS_MT_POSITION_X, x[i]);
> + input_report_abs(ts->input_dev, ABS_MT_POSITION_Y, y[i]);
> + input_mt_sync(ts->input_dev);
> + }
> +
> + /* EV_SYN */
> + input_sync(ts->input_dev);
> +
> +done:
> + enable_irq(ts->client->irq);
> +
> + return;
> +}
> +
Thanks,
Henrik
prev parent reply other threads:[~2010-12-14 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 4:34 [PATCH v2] Input: add ST1232 touchscreen controller driver chinyeow.sim.xt
2010-12-14 6:52 ` Trilok Soni
2010-12-14 9:47 ` Henrik Rydberg [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=4D073D2E.5040107@euromail.se \
--to=rydberg@euromail.se \
--cc=chinyeow.sim.xt@renesas.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=tsoni@codeaurora.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).