All of lore.kernel.org
 help / color / mirror / Atom feed
From: zsadecki@itwatchdogs.com (Zach Sadecki)
To: linux-arm-kernel@lists.infradead.org
Subject: mxs auart driver problems
Date: Sat, 3 Mar 2012 10:00:25 -0600	[thread overview]
Message-ID: <4F524019.5070306@itwatchdogs.com> (raw)

I am having some problems with the mxs-auart driver in the mainline 
kernel on my mx28 board.  If I use minicom to access the port 
(/dev/ttyAPP1) it seems to behave.  If I just send it some characters 
using 'echo -n " " > /dev/ttyAPP1'  it appears to work the first time, 
then if I repeat the same command it hangs until I kill it with ^C.

After some experimentation it seems that it only works if I'm actively 
reading characters out of it 'cat /dev/ttyAPP1' (in background or a 2nd 
terminal) and if I have turned off 'echo' using 'stty -F /dev/ttyAPP1 
-echo'.  Without the '-echo' option the serial port spews random 
characters after sending it something.

Also, when it's in the hanging state, other ttys don't behave either 
(the AMBA serial console can't respawn the login process and I can't ssh 
into the system either).  Once I ^C the hanging 'echo' command 
immediately the console login respawns and ssh login works again.

Anybody else have this problem?  The Freescale kernel (driver with DMA) 
doesn't seem to have this issue (but it still suffers from the '-echo' 
problem described above).  Any ideas on what may be going on here?

Thanks,
   Zach

             reply	other threads:[~2012-03-03 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 16:00 Zach Sadecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-02 21:04 mxs auart driver problems Zach Sadecki

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=4F524019.5070306@itwatchdogs.com \
    --to=zsadecki@itwatchdogs.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.