From: Tollef Fog Heen <tfheen@err.no>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, werner@cornelius-consult.de,
frank@kingswood-consulting.co.uk
Subject: Re: [PATCH] Winchiphead 340/1: full baud rate and status/control line support
Date: Sun, 04 Jan 2009 11:19:21 +0100 [thread overview]
Message-ID: <87sknzs79y.fsf@qurzaw.linpro.no> (raw)
In-Reply-To: <20080921151407.10c89452@lxorguk.ukuu.org.uk> (Alan Cox's message of "Sun, 21 Sep 2008 15:14:07 +0100")
]] Alan Cox
| Some niggles but this is a big improvement to the code.
Thanks. New patch incoming RSN.
| > static int ch341_set_baudrate(struct usb_device *dev,
| > + struct tty_struct *tty,
| > struct ch341_private *priv)
| > + baud = CH341_BAUDBASE_FACTOR / t1;
| > +
| > + if (baud && tty)
| > + tty_encode_baud_rate(tty, baud, baud);
|
| Can you really get a speed below 1 baud ?
Unsure what you mean here? Why would you ever end up with baudrates
below 1?
| > + control = priv->line_control;
| > + spin_unlock_irqrestore(&priv->lock, flags);
| > +
| > + return ch341_set_handshake(port->serial->dev, control);
| > +}
|
| This could race another set_handshake ? I'm not sure it matters and I'd
| suggest that stuff gets fixed after this is submitted separately
What's the easiest way to fix this?
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
next prev parent reply other threads:[~2009-01-04 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200807290254.m6T2sIBG010575@imap1.linux-foundation.org>
[not found] ` <20080729104331.367fde6b@lxorguk.ukuu.org.uk>
2008-09-21 9:22 ` Tollef Fog Heen
2008-09-21 14:14 ` Alan Cox
2009-01-04 10:19 ` Tollef Fog Heen [this message]
2009-01-04 12:19 ` Alan Cox
2009-01-04 10:22 Tollef Fog Heen
2009-01-04 12:16 ` Alan Cox
2009-01-04 21:15 ` Tollef Fog Heen
2009-01-04 21:18 ` Tollef Fog Heen
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=87sknzs79y.fsf@qurzaw.linpro.no \
--to=tfheen@err.no \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=frank@kingswood-consulting.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=werner@cornelius-consult.de \
/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
all inboxes | Powered by JetHome®