public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nathan Monson" <nmonson@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Woodruff, Richard" <r-woodruff2@ti.com>,
	"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>,
	"TK, Pratheesh Gangadhar" <pratheesh@ti.com>
Subject: Re: omapfb: help from userspace
Date: Thu, 9 Oct 2008 10:55:11 -0700	[thread overview]
Message-ID: <e5e6ade50810091055se7af4aasc404eb92f176dfeb@mail.gmail.com> (raw)
In-Reply-To: <20081009124357.GF26230@atomide.com>

On Thu, Oct 9, 2008 at 5:43 AM, Tony Lindgren <tony@atomide.com> wrote:
> Nathan, good to hear that the SO mode helps. But since you seem to
> have it easily reproducable..

Reproducing is as easy as applying the DSP Bridge kernel patches and
then running the 'ping.out' sample like this:  while true; do
ping.out; done

> Could you try the following patch based on RMK's earlier patch
> without the strongly ordered patch and see if that makes any
> difference?

Maybe it lasted a few seconds longer, or maybe it was luck, but in any
case it eventually went into an IRQ -33 loop even with this patch.

> If this patch alone does not do anything, maybe try reading back
> something from the dsp interrupt registers after write also
> in the dsp interrupt handler?

I will look into this and let you know.

> Also you might want to read through the thread linked in the
> patch description.
>
> And, if that still does not work, I'm suspecting that in some cases
> write-read is not enough, and only write-write ensures that it gets
> posted. Some ARM docs say that writes are only posted relative to
> other writes, but I don't know if it can be really that way.

Should I change the patch you sent me to do write write?

> At least we have at least one hack like that in the
> drivers/mmc/host/omap.c.
>
> Anyways, it would be nice to solve this issue for good. The problem
> has been making it easily reproducable.

At least I have a workaround for now.  It's good to be able to get DSP
work done.

- Nathan

  reply	other threads:[~2008-10-09 17:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 18:36 omapfb: help from userspace Nathan Monson
2008-10-08 20:21 ` Nathan Monson
2008-10-08 20:37   ` Woodruff, Richard
2008-10-09  6:20     ` TK, Pratheesh Gangadhar
2008-10-09 12:43       ` Tony Lindgren
2008-10-09 17:55         ` Nathan Monson [this message]
2008-10-15 11:57           ` Paul Walmsley
2008-10-15 12:04             ` Lauri Leukkunen
2008-10-16  6:49             ` Nathan Monson
2008-10-16 20:57               ` Tony Lindgren
2008-10-16 22:07                 ` Nathan Monson
2008-10-16 22:10                   ` Tony Lindgren
2008-10-16 22:15                     ` Nathan Monson
2008-10-16 22:52                       ` Tony Lindgren
2008-10-16 22:59                         ` Tony Lindgren
2008-10-16 23:02                           ` Tony Lindgren
2008-10-16 23:20                             ` Nathan Monson
2008-10-16 23:24                               ` Tony Lindgren
2008-10-17  0:17   ` Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2008-09-15 14:38 Felipe Contreras
2008-09-15 20:24 ` Felipe Contreras
2008-09-15 20:46   ` Måns Rullgård

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=e5e6ade50810091055se7af4aasc404eb92f176dfeb@mail.gmail.com \
    --to=nmonson@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=pratheesh@ti.com \
    --cc=r-woodruff2@ti.com \
    --cc=tony@atomide.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