Serial driver problem from 2.6.12 kernel

Serial driver problem from 2.6.12 kernel

[goog long]

Hi all,

I backported MPSC driver from 2.6.12 to my kernel
2.6.10. However, the driver can send characters, but
cannot receive any characters. Have anyone seen this
before?

Please also send your feedback to cecolong@yahoo.com

Thanks and best regards,
cecolong

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Serial driver problem from 2.6.12 kernel

[Mark A. Greer]

On Fri, Sep 09, 2005 at 08:17:14AM -0700, goog long wrote:
> Hi all,
> 
> I backported MPSC driver from 2.6.12 to my kernel
> 2.6.10. However, the driver can send characters, but
> cannot receive any characters. Have anyone seen this
> before?
> 
> Please also send your feedback to cecolong@yahoo.com

Hmm, a little sparse on info here so its hard to guess.

The mpsc driver is very much influenced by the platform_data that you
pass to it (since there are so many options).  One possibility
is that you have the max_idle platform_data field set to 0 which means
that the mpsc reciever will not timeout and therefore the mpsc will not
pass to the driver whatever you've typed until your receive buffer fills up
(which you may not have done in your testing).  Try a max_idle value of 40
which seems to work fine for me.  Another possibility, of course, is that
you passed in the wrong irq in the platform_data and therefore are not
getting recieving interrupts.

Mark

Re: Serial driver problem from 2.6.12 kernel

[goog long]

I cat /proc/interrupt and see the receiving interrupts
number increases, but the driver can only receive big
messages. Therefore, you first option is right. The
mpsc reciever will not timeout. I changed max_idle to
40 and it works perfect. Thanks a lot Mark.

cecolong

--- "Mark A. Greer" <mgreer@mvista.com> wrote:

> On Fri, Sep 09, 2005 at 08:17:14AM -0700, goog long
> wrote:
> > Hi all,
> > 
> > I backported MPSC driver from 2.6.12 to my kernel
> > 2.6.10. However, the driver can send characters,
> but
> > cannot receive any characters. Have anyone seen
> this
> > before?
> > 
> > Please also send your feedback to
> cecolong@yahoo.com
> 
> Hmm, a little sparse on info here so its hard to
> guess.
> 
> The mpsc driver is very much influenced by the
> platform_data that you
> pass to it (since there are so many options).  One
> possibility
> is that you have the max_idle platform_data field
> set to 0 which means
> that the mpsc reciever will not timeout and
> therefore the mpsc will not
> pass to the driver whatever you've typed until your
> receive buffer fills up
> (which you may not have done in your testing).  Try
> a max_idle value of 40
> which seems to work fine for me.  Another
> possibility, of course, is that
> you passed in the wrong irq in the platform_data and
> therefore are not
> getting recieving interrupts.
> 
> Mark
> 



	
		
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/