linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jason77.wang@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jason Wang <jason77.wang@gmail.com>,
	notasas@gmail.com, vapier@gentoo.org,
	linux-input@vger.kernel.org
Subject: Re: [PATCH 4/4] Input: ads7846 - modificatons of _stop()/_disable() conditions
Date: Wed, 13 Oct 2010 11:12:55 +0800	[thread overview]
Message-ID: <4CB523B7.8010209@gmail.com> (raw)
In-Reply-To: <20101012160055.GA6355@core.coreip.homeip.net>

Hi Dmitry,

I have validated the new patch based off the 2.6.36-rc7 on
the ti_omap3530evm, it works fine.

Thanks,
Jason.

Dmitry Torokhov wrote:
> Hi Jason.
>
> On Tue, Oct 12, 2010 at 05:58:36PM +0800, Jason Wang wrote:
>   
>> Hi Dmitry,
>>
>> Still remember the thread irq modificition for the ads7846.c? I sent
>> 4 patches,
>> you pointed out that the last patch(the 4th one) seems not right, i think it
>> over and find i was wrong because i mingled two independent flags(
>> disabled/suspended). Then i gave my understanding and two plans to
>> be chosen 3 weeks ago, but by now don't get feedback.
>>     
>
> Sorry about that.
>
>   
>> @@ -253,9 +253,10 @@ static void ads7846_enable(struct ads7846 *ts)
>> {
>> mutex_lock(&ts->lock);
>>
>> - if (ts->disabled && !ts->suspended)
>> + if (ts->disabled && !ts->suspended) {
>> + ts->disabled = false;
>> __ads7846_enable(ts);
>>     
>
> If the device was both disabled and suspended then enable will never
> succeed.
>
> I actually was looking over the patches yesterday and I believe I
> corrected the problem you mentioned. I rolled all patches together (no
> reason to keep them separate - they have not been yet applied to
> non-rebasing branch and they are simple fix-ups to the issues introduced
> by the fisrt patch). Could you please try the patch below and if it
> still works I'll queue for .37.
>
> Thanks!
>
>   


  reply	other threads:[~2010-10-13  3:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 10:51 [PATCH 0/4] Switch ads7846 driver to use soft irq Jason Wang
2010-09-16 10:51 ` [PATCH 1/4] Input: ads7846 - switch to using threaded IRQ Jason Wang
2010-09-16 10:51   ` [PATCH 2/4] Input: ads7846 - add a include header to prevent building fails Jason Wang
2010-09-16 10:51     ` [PATCH 3/4] Input: ads7846 - restore ADC to powerdown mode if no messgaes needed Jason Wang
2010-09-16 10:51       ` [PATCH 4/4] Input: ads7846 - modificatons of _stop()/_disable() conditions Jason Wang
2010-09-17  6:39         ` Dmitry Torokhov
2010-09-17  9:20           ` Jason Wang
2010-09-17 16:07             ` Dmitry Torokhov
2010-09-20  8:18               ` Jason Wang
2010-10-12  9:58                 ` Jason Wang
2010-10-12 16:00                   ` Dmitry Torokhov
2010-10-13  3:12                     ` Jason Wang [this message]
2010-10-13 22:17                       ` Grazvydas Ignotas
2010-10-14  2:14                         ` Jason Wang
2010-10-14 21:40                           ` Grazvydas Ignotas
2010-10-15  2:29                             ` Jason Wang
2010-10-18 23:19                               ` Tony Lindgren
2010-10-19  1:25                                 ` Jason Wang
2010-09-17  1:48 ` [PATCH 0/4] Switch ads7846 driver to use soft irq Jason Wang

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=4CB523B7.8010209@gmail.com \
    --to=jason77.wang@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=notasas@gmail.com \
    --cc=vapier@gentoo.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).