From: Jarno Manninen <jarno.manninen@tut.fi>
To: linuxppc-embedded@ozlabs.org
Cc: Linux IDE <linux-ide@vger.kernel.org>, Sven Luther <sl@bplan-gmbh.de>
Subject: Re: [PATCH/RFC] ata: Add support for the MPC52xx ATA controller using libata
Date: Fri, 17 Nov 2006 20:49:48 +0200 [thread overview]
Message-ID: <200611172049.49260.jarno.manninen@tut.fi> (raw)
In-Reply-To: <11637151391017-git-send-email-tnt@246tNt.com>
On Friday 17 November 2006 00:12, Sylvain Munaut wrote:
> * The manual states we should check for the TIP bit before all
> PIO transaction. That's not really supported by libata and requires
> reimplementing almost all the hooks. But after talking to Freescale,
> it turnsout it's not really necessary. So this driver doesn't implement
> that check. I noticed no problem so far ...
I've had some bad experiences with 2.4 line kernel when using BAPI 2.2 on Rev.
A 5200 while imposing heavy I/O load. Problems manifested as hanging XLB-bus
and so on. Funny thing is that combinations like Rev.A + BAPI 2.1 and Rev.B +
BAPI 2.[12] seem to be immune while doing similar stress tests.
Problems went away after wrapping PIO access like this:
1. Stop XLB-pipelining
2. Wait for TIP bit to go down.
3. Do the access
4. Restore XLB-pipelining.
Just polling for the TIP bit is not enough due to errata on Rev. A if the
pipelining is enabled.
Just in case if someone else is having mysterious hangs on Rev.A:s with newer
microcode. :)
- Jarno
next prev parent reply other threads:[~2006-11-17 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 22:12 [PATCH/RFC] ata: Add support for the MPC52xx ATA controller using libata Sylvain Munaut
2006-11-16 23:46 ` Alan
2006-11-17 19:12 ` Sylvain Munaut
2006-11-17 18:49 ` Jarno Manninen [this message]
2006-11-17 19:09 ` Sylvain Munaut
2006-11-17 22:41 ` Jeff Garzik
2006-11-17 23:21 ` Sylvain Munaut
2006-11-19 19:14 ` Nicolas DET
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=200611172049.49260.jarno.manninen@tut.fi \
--to=jarno.manninen@tut.fi \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sl@bplan-gmbh.de \
/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).