From: Suresh Chandra Mannava <msuresh@gamebox.net>
To: "Mark A. Greer" <mgreer@mvista.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Marvell 64360, MPSC Serial Console Problem
Date: Fri, 22 Apr 2005 10:37:53 +0530 [thread overview]
Message-ID: <426886A9.6050809@gamebox.net> (raw)
In-Reply-To: <4266B082.10705@mvista.com>
>
>
> 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
>
>
Mr. Mark,
Thank you for your reply. You exactly pointed out the mistake I had done
with max_idle.
I didn't initialized the mpsc_pdata structure in platform dependent
file. Now I initialized max_idle =40.
And every thing is working fine.
Still facing some problems with mv64360 giga Ethernet driver. I will
come back after a little bit of investigation.
Regards,
Suresh Chandra Mannava
prev parent reply other threads:[~2005-04-22 5:00 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
2005-04-22 5:07 ` Suresh Chandra Mannava [this message]
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=426886A9.6050809@gamebox.net \
--to=msuresh@gamebox.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mgreer@mvista.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;
as well as URLs for NNTP newsgroup(s).