linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [URGENT] Re: bit errors on spitz + voipac
Date: Thu, 3 Jun 2010 10:30:06 +0800	[thread overview]
Message-ID: <AANLkTikSotOdWIKqPpNi100rsVraIxZp6yZplIvaSo9m@mail.gmail.com> (raw)
In-Reply-To: <201006030201.13341.marek.vasut@gmail.com>

On Thu, Jun 3, 2010 at 8:01 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
> Dne Po 8. b?ezna 2010 13:16:35 Cyril Hrubis napsal(a):
>> Hi!
>>
>> > - And I see display noise while CF Wi-Fi card is active.
>>
>> Forgotten about this one. See for yourself, notice short black vertical
>> lines flashing randomly.
>>
>> http://atrey.karlin.mff.cuni.cz/~metan/outgoing/zaurus_sickness.mpg
>
> This is not only case of spitz. I've seen LCD image falling apart on pxafb on
> Voipac PXA270 board. The image was like "torn in half and part of it was moved
> to right, the hole between staying white".
>
> This happened exactly when I started doing a DMA transfer from a harddrive
> attached through pata_pxa. It's perfectly replicable. If I disabled DMA and let
> it run only in PIO, the image was fine.
>
> I assume the corruption Pavel was seeing is related. My guess is the problems
> are caused when DMA between the CPU and a companion chip happens. I dunno if the
> DMA controller doesn't have enough power to supply LCD and the companion chip
> with data, but that's one of my guesses.
>
> btw. Adjusting the DMA descriptor length in pata_pxa didn't help.
>

If there is a FIFO attached, may need the FIFO status when the error happens.
And a dump of the DMA registers would also be helpful.

  reply	other threads:[~2010-06-03  2:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 21:27 bit errors on spitz Pavel Machek
2010-03-08  5:37 ` Eric Miao
2010-03-08  7:28   ` Pavel Machek
2010-03-08  8:25     ` Cyril Hrubis
2010-03-08 11:48       ` Stanislav Brabec
2010-03-08 12:16         ` Cyril Hrubis
2010-03-08 12:42           ` Russell King - ARM Linux
2010-03-08 13:32             ` Cyril Hrubis
2010-06-03  0:01           ` [URGENT] Re: bit errors on spitz + voipac Marek Vasut
2010-06-03  2:30             ` Eric Miao [this message]
2010-03-21 20:40         ` bit errors on spitz Pavel Machek
2010-03-11 13:25       ` Andy Green
2010-03-11 15:42         ` Stanislav Brabec
2010-03-11 21:21           ` Andy Green
2010-03-12  9:07             ` Stanislav Brabec
2010-03-12  9:33               ` Andy Green
2010-03-12 10:43                 ` Stanislav Brabec
2010-03-12 11:13                   ` Andy Green
2010-03-21 20:43               ` Pavel Machek
2010-03-21 21:42                 ` Stanislav Brabec
2010-03-29 18:27                   ` Pavel Machek
2010-03-29 18:52                     ` Stanislav Brabec

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=AANLkTikSotOdWIKqPpNi100rsVraIxZp6yZplIvaSo9m@mail.gmail.com \
    --to=eric.y.miao@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).