From: Oliver Neukum <oliver@neukum.org>
To: "Alfred E. Heggestad" <aeh@db.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: driver for USB VoIP phones with CM109 chipset #2
Date: Mon, 30 Jun 2008 13:06:27 +0200 [thread overview]
Message-ID: <200806301306.27933.oliver@neukum.org> (raw)
In-Reply-To: <486652D1.4010008@db.org>
Am Samstag 28 Juni 2008 17:03:45 schrieb Alfred E. Heggestad:
Hello,
> many many thanks for your patch and your suggested code improvements.
> I have tested your patch and I have some comments:
>
> * The first version of your patch was tested, and it applied cleanly
> and compiled with out any errors. The module was loaded OK, but when
> I inserted the CM109-device into the USB-port, the machine crashed.
> I fixed that issue by adding this to the usb_probe() function:
>
> init_waitqueue_head(&dev->wait);
Sorry about that.
> * The second version of your patch was applied with some local mods.
> This is now working as expected.
Good.
> * I have tested suspend/resume with 2.6.25.9 and TuxOnIce 3.0-rc7
> and it works fine (cm109 device was plugged in during suspend).
> During suspend I get this in syslog:
>
> drivers/input/misc/cm109.c: cm109: usb_suspend (event=1)
> drivers/input/misc/cm109.c: urb_irq_callback: urb status -2
That is normal. It indicates that usb_kill_urb() had terminated the URB.
Which logging level did you use?
> * The flag "char disconnecting:1" is no longer used in your second
> patch, and has been removed from the struct.
Sorry again.
> * When the buzzer is triggered by SND_TONE/SND_BELL, I get these
> warnings in syslog:
>
> drivers/input/misc/cm109.c: urb_ctl_callback: usb_submit_urb failed -22
> drivers/input/misc/cm109.c: buzz: usb_submit_urb failed -22
> drivers/input/misc/cm109.c: urb_ctl_callback: usb_submit_urb failed -22
> drivers/input/misc/cm109.c: buzz: usb_submit_urb failed -22
>
> It seems that the ctl URB is shared between buzzer and keypress
> handling. I am thinking about adding a new URB just for the buzzer,
> but I am not sure if that really is necesary. Any suggestions?
Under which conditions did you get this? Was the device opened or not?
Regards
Oliver
next prev parent reply other threads:[~2008-06-30 11:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 12:24 [PATCH] input: driver for USB VoIP phones with CM109 chipset #2 Oliver Neukum
2008-06-28 15:03 ` Alfred E. Heggestad
2008-06-30 11:06 ` Oliver Neukum [this message]
2008-07-25 14:14 ` Dmitry Torokhov
2008-07-26 15:55 ` Alfred E. Heggestad
2008-07-26 18:45 ` Oliver Neukum
2008-08-03 22:04 ` Alfred E. Heggestad
2008-08-04 11:56 ` Oliver Neukum
2008-08-04 20:34 ` Alfred E. Heggestad
2008-08-04 22:08 ` Oliver Neukum
2008-08-05 19:23 ` Alfred E. Heggestad
2008-08-05 20:14 ` Dmitry Torokhov
2008-08-05 21:19 ` Alfred E. Heggestad
2008-08-18 17:47 ` Dmitry Torokhov
2008-07-29 5:47 ` 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=200806301306.27933.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=aeh@db.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).