From: "Mark A. Greer" <mgreer@mvista.com>
To: Suresh Chandra Mannava <msuresh@gamebox.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Marvell 64360, MPSC Serial Console Problem
Date: Wed, 20 Apr 2005 12:41:54 -0700 [thread overview]
Message-ID: <4266B082.10705@mvista.com> (raw)
In-Reply-To: <4266A320.20102@gamebox.net>
Suresh Chandra Mannava wrote:
> <snip>
>
> We faced a problem in MPSC serial console part. The problem is, in
> Serial console data is received once after 32 characters are typed.
>
> Any thing less than 32 characters is not echoed or not transmitted
> till the 32 character count is reached.
>
> After carefully reviewing the code. We found that the receive buffer
> size is initialised to 32 bytes.
> We made a small correction in the code by making the receive buffer
> size to 1
> rxre->bufsize = 1;
<snip>
Suresh,
I think you fixed a symptom but not the problem. By default, the rx
buffers are indeed 32 bytes long (i.e., a cacheline in size). When
receiving, the mpsc will generate an interrupt when there is an error,
when the buffer is full (32 bytes--unlikely if you're typing), or after
a timeout. I suspect your timeout value is bogus so you don't get the
interrupt until you fill the buffer with 32 bytes. Please compare the
platform_data that you pass to the mpsc driver to other, working systems
that use the mpsc (e.g., katana and cpci690). In particular, look at
your 'max_idle' value.
Mark
next prev parent reply other threads:[~2005-04-20 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 9:17 kernel with marvell 64360 support Suresh Chandra Mannava
2005-02-22 17:05 ` Mark A. Greer
2005-02-22 21:04 ` Mark A. Greer
2005-04-20 18:44 ` Marvell 64360, MPSC Serial Console Problem Suresh Chandra Mannava
2005-04-20 19:41 ` Mark A. Greer [this message]
2005-04-22 5:07 ` Suresh Chandra Mannava
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=4266B082.10705@mvista.com \
--to=mgreer@mvista.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=msuresh@gamebox.net \
/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).