From: Paul Fulghum <paulkf@microgate.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: greg@kroah.com, linux-usb-devel@lists.sourceforge.net,
rwhite@casabyte.com, linux-kernel@vger.kernel.org,
kingst@eecs.umich.edu, Oleksiy <Oleksiy@kharkiv.com.ua>,
reg@dwf.com, clemens@dwf.com
Subject: Re: Little rework of usbserial in 2.4
Date: Sun, 28 Nov 2004 12:14:24 -0600 [thread overview]
Message-ID: <1101665664.3562.3.camel@at2.pipehead.org> (raw)
In-Reply-To: <41A9DEB1.5000309@microgate.com>
On Sun, 2004-11-28 at 08:20 -0600, Paul Fulghum wrote:
> Pete Zaitcev wrote:
> > Not done #1: I asked Paul Fulghum to experiment with dropping a private
> > implementation of write callback from pl2303 and have Oleksy to test it.
Below is a patch that implements Pete's suggested fix for
the pl2303/ppp write problem.
Oleksiy, can you please test this to see if it works
as well as my first patch?
--
Paul Fulghum
paulkf@microgate.com
--- linux-2.4.28/drivers/usb/serial/pl2303.c 2004-08-07 18:26:05.000000000 -0500
+++ b/drivers/usb/serial/pl2303.c 2004-11-28 11:41:07.093134368 -0600
@@ -126,7 +126,6 @@ static int pl2303_ioctl (struct usb_seri
unsigned int cmd, unsigned long arg);
static void pl2303_read_int_callback (struct urb *urb);
static void pl2303_read_bulk_callback (struct urb *urb);
-static void pl2303_write_bulk_callback (struct urb *urb);
static int pl2303_write (struct usb_serial_port *port, int from_user,
const unsigned char *buf, int count);
static void pl2303_break_ctl(struct usb_serial_port *port,int break_state);
@@ -151,7 +150,6 @@ static struct usb_serial_device_type pl2
.set_termios = pl2303_set_termios,
.read_bulk_callback = pl2303_read_bulk_callback,
.read_int_callback = pl2303_read_int_callback,
- .write_bulk_callback = pl2303_write_bulk_callback,
.startup = pl2303_startup,
.shutdown = pl2303_shutdown,
};
@@ -814,41 +812,6 @@ static void pl2303_read_bulk_callback (s
return;
}
-
-
-static void pl2303_write_bulk_callback (struct urb *urb)
-{
- struct usb_serial_port *port = (struct usb_serial_port *) urb->context;
- int result;
-
- if (port_paranoia_check (port, __FUNCTION__))
- return;
-
- dbg("%s - port %d", __FUNCTION__, port->number);
-
- if (urb->status) {
- /* error in the urb, so we have to resubmit it */
- if (serial_paranoia_check (port->serial, __FUNCTION__)) {
- return;
- }
- dbg("%s - Overflow in write", __FUNCTION__);
- dbg("%s - nonzero write bulk status received: %d", __FUNCTION__, urb->status);
- port->write_urb->transfer_buffer_length = 1;
- port->write_urb->dev = port->serial->dev;
- result = usb_submit_urb (port->write_urb);
- if (result)
- err("%s - failed resubmitting write urb, error %d", __FUNCTION__, result);
-
- return;
- }
-
- queue_task(&port->tqueue, &tq_immediate);
- mark_bh(IMMEDIATE_BH);
-
- return;
-}
-
-
static int __init pl2303_init (void)
{
int retval;
next prev parent reply other threads:[~2004-11-28 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 1:35 Pete Zaitcev
2004-11-28 14:20 ` Paul Fulghum
2004-11-28 18:14 ` Paul Fulghum [this message]
2004-12-12 23:47 ` Nish Aravamudan
2004-12-21 20:52 ` Pete Zaitcev
2004-12-22 16:07 ` Nish Aravamudan
2004-12-22 17:24 ` Little rework of usbserial in 2.4\ Marcelo Tosatti
2004-12-18 0:57 ` Little rework of usbserial in 2.4 Greg KH
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=1101665664.3562.3.camel@at2.pipehead.org \
--to=paulkf@microgate.com \
--cc=Oleksiy@kharkiv.com.ua \
--cc=clemens@dwf.com \
--cc=greg@kroah.com \
--cc=kingst@eecs.umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=reg@dwf.com \
--cc=rwhite@casabyte.com \
--cc=zaitcev@redhat.com \
/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
Powered by JetHome