public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: mark gross <mgross@linux.intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	linux-rt-users@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Real time USB2Serial devices and behaivor
Date: Wed, 26 Mar 2008 09:27:28 -0700	[thread overview]
Message-ID: <20080326162728.GC6020@kroah.com> (raw)
In-Reply-To: <20080326152559.GA17164@linux.intel.com>

On Wed, Mar 26, 2008 at 08:25:59AM -0700, mark gross wrote:
> At home I'm playing with a real time amateur robotics application with a
> micro controller talking over its serial port to a Linux box running an RT
> kernel and some RT user mode software to suck in the serial port data
> and do some processing in real time.  One example of what I want to do
> with this type of configuration is to create a type of IMU thing and run
> the data through a kalman filter to see how good I can do with my
> hardware.
> 
> I'll be sending data regularly at data rates between 50 and 500 HZ from
> the MCU (depending on mode)
> 
> Anyway, I have the RT code and the system prototyped using the hardware
> serial port on my desktop and I'm getting rock solid RT delivery times
> of the data +/- 30usec.  While stressing the system in CPU and disk. (I
> still need to do the test while flood pinging the box)  However; when I
> use my USB dongle instead of the hardware serial port the system falls
> over WRT real time behavior.
> 
> I'm just starting to look into the behavior now but has anyone looked at
> the RT'ness of USB2Serial + USB stack yet?  I would like to see what
> other folks have done.  My googleing last night didn't get any useful
> hits.

I have, and others have in the past, and it's something that you can not
really do.  USB is not "deterministic", and these cheap usb to serial
devices introduce a very big lag that also is not deterministic.

I wouldn't recommend using USB for anything that you need to be able to
accuratly control the latency of, it's just not going to work as that is
not what it was designed for at all.

> BTW Why does the PL2303 have a 1KB buffer for incoming data?

The device or the driver?

> I'm a bit green at RT work at this level.  What are the best ways for
> drilling down to figure out what the problems are so I can make a patch?

Give up and use a "real" serial port, you'll have better luck :)

thanks,

greg k-h

  reply	other threads:[~2008-03-26 16:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 15:25 Real time USB2Serial devices and behaivor mark gross
2008-03-26 16:27 ` Greg KH [this message]
2008-03-26 16:49   ` mark gross
2008-03-26 23:24     ` Greg KH
2008-03-27  2:58       ` Alan Stern
2008-03-27  4:13         ` Greg KH
2008-03-27 19:48     ` David Brownell
2008-03-27 21:00       ` Lennart Sorensen
2008-03-27 21:08         ` David Brownell
2008-03-28 13:38           ` Lennart Sorensen
2008-04-03 14:26   ` Ming Lei
2008-04-03 14:45     ` Peter Zijlstra
2008-04-03 15:52     ` Greg KH
2008-04-03  6:24 ` Jon Masters

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=20080326162728.GC6020@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mgross@linux.intel.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