public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: arief_mulya <arief_m_utama@telkomsel.co.id>
To: Andrew Morton <akpm@osdl.org>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH?] psmouse-base.c
Date: Mon, 10 Nov 2003 14:08:11 +0700	[thread overview]
Message-ID: <3FAF395B.8080302@telkomsel.co.id> (raw)
In-Reply-To: <20031109225643.2a0383ef.akpm@osdl.org>

Andrew Morton wrote:

>Dmitry Torokhov <dtor_core@ameritech.net> wrote:
>  
>
>>On Sunday 09 November 2003 11:12 pm, Andrew Morton wrote:
>>    
>>
>>>arief_mulya <arief_m_utama@telkomsel.co.id> wrote:
>>>      
>>>
>>>>static int psmouse_pm_callback(struct pm_dev *dev, pm_request_t
>>>>request, void *data)
>>>> {
>>>>         struct psmouse *psmouse = dev->data;
>>>>         struct serio_dev *ser_dev = psmouse->serio->dev;
>>>>
>>>>
>>>>         switch (request) {
>>>>         case PM_RESUME:
>>>>                 psmouse->state = PSMOUSE_IGNORE;
>>>>                 serio_rescan(psmouse->serio);
>>>>         default:
>>>>                 return 0;
>>>>         }
>>>> }
>>>>        
>>>>
>>>What does the driver do without this change?  ie: what problem is this
>>>fixing?
>>>
>>>Why is it calling serio_rescan() rather than serio_reconnect()?
>>>
>>>      
>>>
>>serio_reconnect() is only in your tree (-mm), it has not been pushed to
>>Linus yet... Unfortunately using rescan can cause input devices be shifted
>>if some program has them open while suspending.
>>    
>>
>
>  
>
Well, I don't know about this.
I was just trying to get my synaptics mouse working nicely through 
suspend-resume. And I haven't learn about linux kernel structure before, 
so I just spend all my sunshiny Sunday, researching everywhere with my 
lazy brain.

And finally, those (ugly?) patch come out ;-)

>Ah, I see.  So would you say that reconnect is the correct thing to use
>here?
>
>That would mean that the appropriate patch against -mm is
>
>--- 25/drivers/input/mouse/psmouse-base.c~serio-pm-fix	2003-11-09 20:12:27.000000000 -0800
>+++ 25-akpm/drivers/input/mouse/psmouse-base.c	2003-11-09 20:12:27.000000000 -0800
>@@ -533,9 +533,10 @@ static int psmouse_pm_callback(struct pm
> {
> 	struct psmouse *psmouse = dev->data;
> 
>-	psmouse->state = PSMOUSE_IGNORE;
>-	serio_reconnect(psmouse->serio);
>-
>+	if (request == PM_RESUME) {
>+		psmouse->state = PSMOUSE_IGNORE;
>+		serio_reconnect(psmouse->serio);
>+	}
> 	return 0;
> }
> 
>
>_
>
>  
>
I guess I gotta try your tree now.

>Those serio patches have been in -mm for six weeks btw.  Was there some
>problem with them?
>  
>
I don't know. Has anybody tested it using an IBM T30 with Synaptics inside?

Best Regards.
-- 
arief_mulya


  reply	other threads:[~2003-11-10  7:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10  2:28 [PATCH?] psmouse-base.c arief_mulya
2003-11-10  4:12 ` Andrew Morton
2003-11-10  6:43   ` Dmitry Torokhov
2003-11-10  6:56     ` Andrew Morton
2003-11-10  7:08       ` arief_mulya [this message]
2003-11-11  5:20       ` Dmitry Torokhov
2003-11-11  6:54         ` arief_mulya
2003-11-11 23:29           ` Dmitry Torokhov
2003-11-12  2:28             ` arief_mulya
2003-11-12  3:42               ` Dmitry Torokhov

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=3FAF395B.8080302@telkomsel.co.id \
    --to=arief_m_utama@telkomsel.co.id \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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