From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Javier Martinez Canillas <javier@dowhile0.org>,
Henrik Rydberg <rydberg@euromail.se>,
Kevin McNeely <kev@cypress.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH 1/1][INCREMENTAL] Input: cyttsp - Fixes to clean-up patch
Date: Tue, 31 Jan 2012 00:21:52 -0800 [thread overview]
Message-ID: <20120131082152.GA4064@core.coreip.homeip.net> (raw)
In-Reply-To: <CAAwP0s16iO_w9cTLY_ps-X5uBCks4p15XBs2Ea69Gu7Qm7Xe_Q@mail.gmail.com>
On Sun, Jan 29, 2012 at 04:28:12PM +0100, Javier Martinez Canillas wrote:
> On Sun, Jan 29, 2012 at 7:18 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > On Sun, Jan 29, 2012 at 06:53:50AM +0100, Javier Martinez Canillas wrote:
> >> This is patch fixes two bugs in Dmitry's last cleanup patch.
> >>
> >> 1- The hardware tracking ids are stored in the ids array and the information for
> >> each contact is obtained calling cyttsp_get_tch() with an index. In the clean-up
> >> patch the value of the tracking id was used instead of the contact index.
> >>
> >
> > Oops, thank you for fixing that.
> >
> >> 2- i2c_set_clientdata() is called after the generic cyttsp_probe() function and
> >> this function calls cyttsp_power_on() that sends an ttsp command to the device
> >> and needs the client data before is set. The fix is to execute cyttsp_power_on
> >> inside the transport specific probe function (I2C, SPI) after the generic probe
> >> function is executed and the client data is set.
> >>
> >
> > Not quite happy about this one, how about we pass cyttsp directly to bus
> > methods instead of relying on drvdata (as in the patch below)?
> >
> > Thanks.
> >
> > --
> > Dmitry
>
> Hi Dmitry,
>
> Yes, you are right that is a much more clever solution to the issue.
> Thank you for suggesting that.
>
> I just sent an v2 of the incremental patch to be applied on top of
> your last clean-up.
>
> This fixes the index bug stated before and the dev->i2c_client->cyttsp
> reference being NULL issue changing the read/write methods signature
> as you suggested.
>
> It also fixes an unbalanced IRQ warning since soft_reset() now is
> called inside the probe function and removes the wake_up platform
> function in enable() as with the incremental v1.
>
> Thanks a lot for your help and best regards,
Folded everything up and applied to my 3.4 queue.
Thank you Javier.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-31 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 5:53 [PATCH 1/1][INCREMENTAL] Input: cyttsp - Fixes to clean-up patch Javier Martinez Canillas
2012-01-29 6:18 ` Dmitry Torokhov
2012-01-29 15:28 ` Javier Martinez Canillas
2012-01-31 8:21 ` Dmitry Torokhov [this message]
2012-01-31 16:52 ` Javier Martinez Canillas
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=20120131082152.GA4064@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=javier@dowhile0.org \
--cc=kev@cypress.com \
--cc=linux-input@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--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).