From: Greg KH <greg@kroah.com>
To: bart.hartgers@gmail.com
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] ark3116: (3rd try) Setup some basic infrastructure for new ark3116 driver.
Date: Tue, 27 Oct 2009 10:46:03 -0700 [thread overview]
Message-ID: <20091027174603.GD23368@kroah.com> (raw)
In-Reply-To: <20091025175316.391430732@gmail.com>
On Sun, Oct 25, 2009 at 06:50:58PM +0100, bart.hartgers@gmail.com wrote:
> Signed-off-by: Bart Hartgers <bart.hartgers@gmail.com>
> ---
> Index: linux-2.6.32-rc4/drivers/usb/serial/ark3116.c
> ===================================================================
> --- linux-2.6.32-rc4.orig/drivers/usb/serial/ark3116.c 2009-10-18 14:25:02.000000000 +0200
> +++ linux-2.6.32-rc4/drivers/usb/serial/ark3116.c 2009-10-18 14:25:14.000000000 +0200
> @@ -1,4 +1,6 @@
> /*
> + * Copyright (C) 2009 by Bart Hartgers (bart.hartgers+ark3116@gmail.com)
> + * Original version:
> * Copyright (C) 2006
> * Simon Schulz (ark3116_driver <at> auctionant.de)
> *
> @@ -6,10 +8,13 @@
> * - implements a driver for the arkmicro ark3116 chipset (vendor=0x6547,
> * productid=0x0232) (used in a datacable called KQ-U8A)
> *
> - * - based on code by krisfx -> thanks !!
> - * (see http://www.linuxquestions.org/questions/showthread.php?p=2184457#post2184457)
> + * Supports full modem status lines, break, hardware flow control. Does not
> + * support software flow control, since I do not know how to enable it in hw.
> *
> - * - based on logs created by usbsnoopy
> + * This driver is a essentially new implementation. I initially dug
> + * into the old ark3116.c driver and suddenly realized the ark3116 is
> + * a 16450 with a USB interface glued to it. See comments at the
> + * bottom of this file.
> *
> * This program is free software; you can redistribute it and/or modify it
> * under the terms of the GNU General Public License as published by the
> @@ -19,15 +24,31 @@
>
> #include <linux/kernel.h>
> #include <linux/init.h>
> +#include <asm/atomic.h>
> +#include <linux/ioctl.h>
> #include <linux/tty.h>
> +#include <linux/tty_flip.h>
> #include <linux/module.h>
> #include <linux/usb.h>
> #include <linux/usb/serial.h>
> #include <linux/serial.h>
> +#include <linux/serial_reg.h>
> #include <linux/uaccess.h>
> -
> +#include <linux/mutex.h>
>
> static int debug;
> +/*
> + * Version information
> + */
> +
> +#define DRIVER_VERSION "v0.3"
> +#define DRIVER_AUTHOR "Bart Hartgers <bart.hartgers+ark3116@gmail.com>"
> +#define DRIVER_DESC "USB ARK3116 serial/IrDA driver"
> +#define DRIVER_DEV_DESC "ARK3116 RS232/IrDA"
> +#define DRIVER_NAME "ark3116"
> +
> +/* usb timeout of 1 second */
> +#define ARK_TIMEOUT (1*HZ)
>
> static struct usb_device_id id_table [] = {
> { USB_DEVICE(0x6547, 0x0232) },
> @@ -45,6 +66,52 @@ static int is_irda(struct usb_serial *se
> return 0;
> }
>
> +struct ark3116_private {
> + wait_queue_head_t delta_msr_wait;
> + struct async_icount icount;
> + int irda; /* 1 for irda device */
> +
> + /* protects hw register updates */
> + struct mutex lock;
> +
> + int quot; /* baudrate divisor */
> + __u8 lcr; /* line control register value */
> + __u8 hcr; /* handshake control register (0x8)
> + * value
> + */
> + /* register values - updated asynchronously */
> + atomic_t mcr;
> + atomic_t msr;
> + atomic_t lsr;
These don't need to be atomic, please don't use them if they are not
needed. Just use the lock to protect updating them if needed.
Care to respin this series based on the review so far?
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-27 17:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 17:50 [PATCH 0/7] ark3116: (3rd try) driver rework bart.hartgers
2009-10-25 17:50 ` [PATCH 1/7] ark3116: (3rd try) Setup some basic infrastructure for new ark3116 driver bart.hartgers
2009-10-27 17:46 ` Greg KH [this message]
2009-10-27 21:35 ` Bart Hartgers
2009-10-27 22:11 ` Greg KH
2009-10-25 17:50 ` [PATCH 2/7] ark3116: (3rd try) Make existing functions 16450-aware and add close and release functions bart.hartgers
2009-10-25 19:56 ` Oliver Neukum
2009-10-25 17:51 ` [PATCH 3/7] ark3116: (3rd try) Replace cmget bart.hartgers
2009-10-25 19:52 ` Oliver Neukum
2009-10-25 19:56 ` Bart Hartgers
2009-10-25 22:08 ` Oliver Neukum
2009-10-25 17:51 ` [PATCH 4/7] ark3116: (3rd try) Add atomic set-and-clear function bart.hartgers
2009-10-25 17:51 ` [PATCH 5/7] ark3116: (3rd try) Add cmset and break bart.hartgers
2009-10-25 17:51 ` [PATCH 6/7] ark3116: (3rd try) Callbacks for interrupt and bulk read bart.hartgers
2009-10-25 17:51 ` [PATCH 7/7] ark3116: (3rd try) Cleanup of now unneeded functions bart.hartgers
2009-10-25 17:53 ` [PATCH 0/7] ark3116: (3rd try) driver rework 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=20091027174603.GD23368@kroah.com \
--to=greg@kroah.com \
--cc=bart.hartgers@gmail.com \
--cc=gregkh@suse.de \
--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