From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Kevin McNeely <kev@cypress.com>,
Henrik Rydberg <rydberg@euromail.se>,
Srikar <ext-srikar.1.bhavanarayana@nokia.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Input: cyttsp - add support for Cypress TTSP touchscreen SPI bus interface
Date: Sat, 03 Sep 2011 07:31:58 +0200 [thread overview]
Message-ID: <1315027918.11839.10.camel@sauron> (raw)
In-Reply-To: <20110822024412.GC17891@core.coreip.homeip.net>
Hello Dmitry,
On Sun, 2011-08-21 at 19:44 -0700, Dmitry Torokhov wrote:
> Hi Javier,
>
> > +
> > + memset((void *)xfer, 0, sizeof(xfer));
> > + spi_message_init(&msg);
> > + xfer[0].tx_buf = wr_buf;
> > + xfer[0].rx_buf = rd_buf;
>
> Since we are setting both TX and RX buffer here does this mean that the
> device will not work with controllers in half-duplex mode? What is the
> amount of data that will be placed in rd_buf?
>
Both TX and RX buffers are set because Cypress requires full duplex
operation always.
> > + retval = spi_sync_tmo(ts, &msg);
> > + if (retval < 0) {
> > + dev_dbg(ts->ops.dev, "%s: spi sync error %d, len=%d, op=%d\n",
> > + __func__, retval, xfer[1].len, op);
> > + retval = 0;
>
> Why do we ignore the error?
>
Fixed: In next version a following ACK check code return the status to
the cyttsp core so it can retry after waiting with an msleep() call.
> > + }
> > +
> > + if (op == CY_SPI_RD_OP) {
> > + if ((rd_buf[CY_SPI_SYNC_BYTE] == CY_SPI_SYNC_ACK1) &&
> > + (rd_buf[CY_SPI_SYNC_BYTE+1] == CY_SPI_SYNC_ACK2))
> > + retval = 0;
>
> What about write operation? Does the device send anything in rd_buf for
> write command?
>
Fixed: Both read and write operations check the ACK bytes now.
> > +
> > + if (op == CY_SPI_RD_OP) {
> > + for (tries = CY_NUM_RETRY; tries; tries--) {
> > + retval = cyttsp_spi_xfer_(op, ts, reg, buf, length);
> > + if (retval == 0)
> > + break;
> > + else
> > + msleep(20);
>
> Why do we need retry in SPI case but do not need it when device is
> connected via I2C? And not on writes?
>
Fixed: The retries now are made in the cyttsp core so it works both for
SPI and I2C.
> > +
> > + if (retval == -EIO)
> > + return 0;
>
> Why is -EIO special?
>
Fixed: Now special EIO has been fixed to show meaning.
> > + else
> > + return retval;
> > +}
> > +
>
> Thanks.
>
> --
> Dmitry
Best regards,
Javier Martinez Canillas
prev parent reply other threads:[~2011-09-03 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 4:01 Input: Cypress TTSP device driver Javier Martinez Canillas
2011-08-20 4:01 ` [PATCH 1/3] Input: cyttsp - Cypress TTSP capacitive multi-touch screen support Javier Martinez Canillas
2011-08-22 4:31 ` Dmitry Torokhov
2011-08-22 13:06 ` Javier Martinez Canillas
2011-09-03 5:34 ` Javier Martinez Canillas
2011-08-20 4:01 ` [PATCH 2/3] Input: cyttsp - add support for Cypress TTSP touchscreen I2C bus interface Javier Martinez Canillas
2011-08-20 4:01 ` [PATCH 3/3] Input: cyttsp - add support for Cypress TTSP touchscreen SPI " Javier Martinez Canillas
2011-08-22 2:44 ` Dmitry Torokhov
2011-09-03 5:31 ` Javier Martinez Canillas [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=1315027918.11839.10.camel@sauron \
--to=martinez.javier@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ext-srikar.1.bhavanarayana@nokia.com \
--cc=gregkh@suse.de \
--cc=kev@cypress.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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).