linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] pdc202xx_old: fix resetproc() method
Date: Sun, 31 May 2009 16:58:45 +0200	[thread overview]
Message-ID: <200905311658.45703.bzolnier@gmail.com> (raw)
In-Reply-To: <200905300007.13113.sshtylyov@ru.mvista.com>


On Friday 29 May 2009 22:07:12 Sergei Shtylyov wrote:
> pdc202xx_reset() calls pdc202xx_reset_host() twice, for both channels, while
> that function actually twiddles the single, shared software reset bit -- the
> net effect is a duplicated reset and horrendous 4 second delay happening not
> only on a channel reset but also when dma_lost_irq() and dma_clear() methods
> are called.  Fold pdc202xx_reset_host() into pdc202xx_reset(), fix printk(),
> and move it before the actual reset...
> 
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> 
> ---
> The patch is against the ide-2.6.git master branch...
> 
> Bart, I know you have the docs... from the now removed source code I was able
> to figure out that the bit in question most probably drives RST- signal on both
> channels (it seems to require re-tuning drives on both channels which we are
> currently not doing). If I'm right, why the hell we're twiddling it on a normal
> SRST reset, and what's worse on an interrupt timeout conditions? Anyway, it's

Unfortunately the documentation doesn't say anything more than that the changing
of the bit value results in SRST on both channels...

IIRC from some old discussions this is required by the chipset sometimes..

> hardly a good idea to reset both channels when you only have problem with only
> one of them, and I don't see any justification to doing that... So maybe this
> patch should've actually wiped out that whole reset insanity for good?..

I'm pretty sure that there are valid reasons behind some of this insanity,
OTOH (per mail from Alan) it completely ignores the fact that the other port
may be active.. 

We may try removing it in incremental patch so it is easier to track/revert
it if things go wrong..

  parent reply	other threads:[~2009-05-31 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 20:07 [PATCH] pdc202xx_old: fix resetproc() method Sergei Shtylyov
2009-05-29 21:41 ` Alan Cox
2009-05-31 14:58 ` Bartlomiej Zolnierkiewicz [this message]
2009-06-03 17:58   ` Sergei Shtylyov
2009-06-07 11:43 ` Bartlomiej Zolnierkiewicz

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=200905311658.45703.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).