public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] : Fix annoying 'too much work for irq72' serial port watermark error.
Date: Thu, 23 Mar 2006 11:46:28 -0800	[thread overview]
Message-ID: <20060323194604.GH22325@atomide.com> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A504E6159F@dlee02.ent.ti.com>

* Woodruff, Richard <r-woodruff2@ti.com> [060323 11:30]:
> Perhaps this version is better.  It avoids a possible double entry to
> transmit_chars() and removes the need for an #ifdef OMAPxyz.

OK, let's test this on various boards.

> > I was just trying out a different PRCM set on 2420/2430 and the
> annoying
> > serial 'too much work' interrupt started up again even with an SCR=8.
> > I've attached a patch which fixes the problem.  At fastest PRCM sets
> > timing some issues have popped up which have been masked before.
> > 
> > Note: This patch is a consolidated on with the other patches I had
> > previously sent which have not been applied, as this is what I tested
> > with.  The timer version in this patch is good, and I validated
> outputs
> > using the emulator at function entry/exits.  Some of the earlier
> > versions had overflow issues with nano-seconds.
> > 
> > This patch now allows the OMAP_SCR to go back to 0, though it works
> > either way.  This issue was this:  A THR interrupt can be generated
> > which has status in the IIR, but without status in the LSR.  This is
> > because the TX watermark interrupt happens when the FIFO and SR are
> NOT
> > empty.  The previous logic assumed at least the FIFO was empty before
> > calling the TX routine.  For a watermark this is not the case.  The
> fix
> > I added to this code checks the SSR (supplementary status register) to
> > see if there is room in the FIFO.  Given we know how it was loaded
> there
> > will be room if this shows it is not empty.

Thanks, I'll take a look at the timer code soonish.

Tony

  reply	other threads:[~2006-03-23 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23 19:29 [PATCH] : Fix annoying 'too much work for irq72' serial port watermark error Woodruff, Richard
2006-03-23 19:46 ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-23 17:53 Woodruff, Richard

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=20060323194604.GH22325@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=r-woodruff2@ti.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