From: Matthew Lear <matt@bubblegen.co.uk>
To: Lanttor <lanttor.guo@freescale.com>
Cc: linux-m68k@vger.kernel.org
Subject: Re: uart issues on coldfire platform
Date: Wed, 01 Jul 2009 14:44:00 +0100 [thread overview]
Message-ID: <4A4B6820.2050103@bubblegen.co.uk> (raw)
In-Reply-To: <4A4AC800.3070901@freescale.com>
Lanttor wrote:
> Hi,
>
> I find one issue of UART on my coldfire platforms (mcf54451evb board).
> I use the linux-2.6.29, and use drivers/serial/mcf.c and
> drivers/serial/serial_core.c as my uart driver source.
>
> Following is my test steps -- run command: cat /proc/interrupts two
> times contiguously.
>
> [root@freescale /]# cat /proc/interrupts
> M5445X *90: 5099 UART*
> M5445X 96: 3130 timer0
> M5445X 99: 0 timer3
> M5445X 100: 1569 fec(TXF)
> M5445X 101: 0 fec(TXB)
> M5445X 102: 0 fec(TXFIFO)
> M5445X 103: 0 fec(TXCR)
> M5445X 104: 3098 fec(RXF)
> M5445X 105: 0 fec(RXB)
> M5445X 106: 41 fec(MII)
> M5445X 107: 0 fec(LC)
> M5445X 108: 0 fec(HBERR)
> M5445X 109: 0 fec(GRA)
> M5445X 110: 0 fec(EBERR)
> M5445X 111: 0 fec(BABT)
> M5445X 112: 0 fec(BABR)
> [root@freescale /]# cat /proc/interrupts
> M5445X *90: 5714 UART*
> M5445X 96: 3700 timer0
> M5445X 99: 1 timer3
> M5445X 100: 1574 fec(TXF)
> M5445X 101: 0 fec(TXB)
> M5445X 102: 0 fec(TXFIFO)
> M5445X 103: 0 fec(TXCR)
> M5445X 104: 3108 fec(RXF)
> M5445X 105: 0 fec(RXB)
> M5445X 106: 47 fec(MII)
> M5445X 107: 0 fec(LC)
> M5445X 108: 0 fec(HBERR)
> M5445X 109: 0 fec(GRA)
> M5445X 110: 0 fec(EBERR)
> M5445X 111: 0 fec(BABT)
> M5445X 112: 0 fec(BABR)
>
> I find that the interrupts for above operation is 5714 - 5099 = 605
> Is it normal? (my opinion it's too much)
>
> I test it on the mcf5329 board, it has the same-like result (even more 605).
> Actually I don't modify any code of mcf.c and serial_core.c, but I don't
> know why so much interrupts are occurred through one operation?
By the looks of it, the driver is interrupting per character (ie per
byte). If you copy half your output above into a text editor, and count
the characters, including one byte per line end, you get 605. I can't
speak for the driver implementation, but it sounds fair enough to me.
Cheers,
-- Matt
prev parent reply other threads:[~2009-07-01 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 2:20 uart issues on coldfire platform Lanttor
2009-07-01 6:30 ` Lanttor
2009-07-02 0:40 ` [uClinux-dev] " Greg Ungerer
2009-07-02 2:21 ` Lanttor
2009-07-01 13:44 ` Matthew Lear [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=4A4B6820.2050103@bubblegen.co.uk \
--to=matt@bubblegen.co.uk \
--cc=lanttor.guo@freescale.com \
--cc=linux-m68k@vger.kernel.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