From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Donald" <donald@asix.com.tw>
Cc: "'Greg KH'" <gregkh@linuxfoundation.org>,
"'open list:USB SUBSYSTEM'" <linux-usb@vger.kernel.org>,
"'open list'" <linux-kernel@vger.kernel.org>
Subject: Re: Patch "USB: serial: mos7840: Supported MCS7810 device"
Date: Thu, 29 Mar 2012 16:04:14 +0100 [thread overview]
Message-ID: <20120329160414.1e70d4c5@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <005a01cd0db0$8ec89e50$ac59daf0$@com.tw>
> +static void mos7810_control_callback(struct urb *urb)
> +{
> + if (!urb)
> + return;
How can this ever occur. If its not theoretically possible then this
check is just going to hide bugs in future.
> +static void mos7810_led_off(unsigned long arg)
> +{
> + struct moschip_port *mcs = (struct moschip_port *) arg;
> +
> + if (!mcs)
> + return;
Ditto
> + /* Turn on MCS7810 LED */
> + if (serial->num_ports == 1 && mos7840_port->mos7810_led_flag == 0) {
> + mos7840_port->mos7810_led_flag = 1;
> + mos7810_set_reg(mos7840_port, 0x0301,
> MODEM_CONTROL_REGISTER);
> + mod_timer(&mos7840_port->mos7810_led_timer1, jiffies + 500);
> + }
The assumption that serial->num_ports = 1 means "has LED" is going to
cause problems later if another deivce appears with 1 port and no LED. I
think it would be much clearer to have something like
if (mos7840_port->has_led)
for these tests of the driver
> +static int mos7810_check(struct usb_serial *serial)
> +{
> + int i, pass_count = 0;
> + __u16 Data = 0, MCR_Data = 0;
> + __u16 test_pattern = 0x55AA, write_pattern;
generally linux style is all lower case for egister names. Not a big deal
> + /* If this a MCS7810 device, both test patterns must match
> */
> + if (((test_pattern >> i) & 0x0001) != ((~(Data >> 1)) &
> 0x0001))
if (((test_pattern >> i) ^ (~Data >> 1)) & 0x0001) ?
again trivia...
> + mos7840_port->mos7810_led_timer1.expires =
> + jiffies + 500;
This 500 value depends upon the HZ value of the kernel which won't always
be 1000 on all platforms. You probably want
jiffies + msecs_to_jiffies(500);
(or indeed HZ/2)
> + /* Turn off MCS7810 LED */
> + usb_control_msg(serial->dev,
> + usb_sndctrlpipe(serial->dev, 0),
> + MCS_WRREQ, MCS_WR_RTYPE, 0x0300,
> + MODEM_CONTROL_REGISTER, NULL, 0,
> + MOS_WDR_TIMEOUT);
> +
Might be clearer if these occurences were a separate small function - gcc
will inline them if it makes sense, and it will be clearer.
Alan
next prev parent reply other threads:[~2012-03-29 15:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 7:54 [PATCH 1/1] x86: Fixed MCS7820 device attach problem Donald
2012-03-13 16:09 ` 'Greg KH'
2012-03-29 13:33 ` Patch "USB: serial: mos7840: Supported MCS7810 device" Donald
2012-03-29 15:04 ` Alan Cox [this message]
2012-03-30 2:16 ` Donald
2012-03-29 15:13 ` 'Greg KH'
2012-03-30 2:21 ` Donald
2012-04-11 9:32 ` Donald
2012-04-11 11:08 ` Johan Hovold
2012-04-11 11:43 ` Donald
2012-04-11 14:03 ` 'Greg KH'
2012-04-12 6:00 Donald
2012-04-12 9:49 ` Alan Cox
2012-04-13 2:20 ` Donald
2012-04-13 12:57 ` Alan Cox
2012-04-14 6:48 ` Donald
2012-04-13 14:24 ` 'Greg KH'
2012-04-19 7:00 Donald
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=20120329160414.1e70d4c5@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=donald@asix.com.tw \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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
all inboxes | Powered by JetHome®