From: "changgx" <changgx-9Onoh4P/yGk@public.gmane.org>
To: manuel.stahl-GeUHRtUQU7nSyEMIgutvibNAH6kLmebB@public.gmane.org
<manuel.stahl-GeUHRtUQU7nSyEMIgutvibNAH6kLmebB@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
hunterzhu-MjT5Q16qtnaZox4op4iWzw@public.gmane.org,
linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: for sc16is752 driver
Date: Wed, 22 Dec 2010 14:2:19 +0800 [thread overview]
Message-ID: <4D119475.0810A3.15889@m12-15.163.com> (raw)
Hello,manuel.stahl,
I read the message from Johannes Reif on the internet.
His email is as follows:
"I'm using the sc16is7x2 driver (SPI<-> 2x UART) written by Manuel Stahl.
While operating one UART channel everything seems fine. But if I use both channels the driver runs into an "unresponsive state" after some time. In this state I figured out that the /IRQ pin of the chip stays low (active) although the IIR of both channels indicates that there is no interrupt pending."
because there is not request_threaded_irq( ) function in 2.6.27 kernel version. So i use your old version sc16is7x2.c. It does not use the thread-irq, but with work queue. But i get the same results with Johannes Reif .
My test app program is described as follows:
In the application creates two threads, each operates a sc16is752 serial port. In every thread, first send 100 bytes,followed by waitting to receive about 200byte.
The test result is that the spi driver reports the error :ttySC0: 64 input overrun(s) or ttySC1: 1 input overrun(s) ,and app received part of the data.
Sometimes IRQ is held low.
Can you give some advice about this question?
I continue to follow this issue.
Thanks!
kathy chang
2010-12-22
------------------------------------------------
tel：+086 21 62545050-7910
fax：62578046
Email：changgx@163.com
------------------------------------------------
------------------------------------------------------------------------------
Forrester recently released a report on the Return on Investment (ROI) of
Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even
within 7 months. Over 3 million businesses have gone Google with Google Apps:
an online email calendar, and document program that's accessible from your
browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew
_______________________________________________
spi-devel-general mailing list
spi-devel-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spi-devel-general
reply other threads:[~2010-12-22 6:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D119475.0810A3.15889@m12-15.163.com \
--to=changgx-9onoh4p/ygk@public.gmane.org \
--cc=hunterzhu-MjT5Q16qtnaZox4op4iWzw@public.gmane.org \
--cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=manuel.stahl-GeUHRtUQU7nSyEMIgutvibNAH6kLmebB@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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;
as well as URLs for NNTP newsgroup(s).