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 pata-2.6] cmd64x: fix multiword and remove single-word DMA support
Date: Mon, 23 Apr 2007 23:49:43 +0200	[thread overview]
Message-ID: <200704232349.44067.bzolnier@gmail.com> (raw)
In-Reply-To: <200704142309.04099.sshtylyov@ru.mvista.com>

On Saturday 14 April 2007, Sergei Shtylyov wrote:
> Fix the multiword DMA and drop the single-word DMA support (which nobody will
> miss, I think).  In order to do it, a number of changes was necessary:
> 
> - rename program_drive_counts() to program_cycle_times(), pass to it cycle's
>   total/active times instead of the clock counts, and convert them into the
>   active/recovery clocks there instead of cmd64x_tune_pio() -- this causes
>   quantize_timing() to also move;
> 
> - contrarywise, move all the code handling the address setup timing into
>   cmd64x_tune_pio(), so that setting MWDMA mode wouldn't change address setup;
> 
> - remove from the speedproc() method the  bogus code pretending to set the DMA
>   timings by twiddling bits in the BMIDE status register, handle setting MWDMA
>   by just calling program_cycle_times(); while at it, improve the style of that
>   whole switch statement;
> 
> - stop fiddling with the DMA capable bits in the speedproc() method -- they do
>   not enable DMA, and are properly dealt with by the dma_host_{on,off} methods;
> 
> - don't set hwif->swdma_mask in the init_hwif() method anymore.
> 
> In addition to those changes, do the following:
> 
> - in cmd64x_tune_pio(), when writing to ARTTIM23 register preserve the interrupt
>   status bit, eliminate local_irq_{save|restore}() around this code as there's
>   *no* actual race with the interrupt handler, and move cmdprintk() to a more
>   fitting place -- after ide_get_best_pio_mode() call;
> 
> - make {arttim|drwtim}_regs arrays single-dimensional, indexed with drive->dn;
> 
> - rename {setup|recovery}_counts[] into more fitting {setup|recovery}_values[];
> 
> - in  the speedproc() method, get rid of the duplicate reads/writes from/to the
>   UDIDETCRx registers and of the extra variable used to store the transfer mode
>   value after filtering,  use another method of determining master/slave drive,
>   and cleanup useless parens;
> 
> - beautify cmdprintk() output here and there.
> 
> While at it, remove meaningless comment about the driver being used only on
> UltraSPARC and long non-relevant RCS tag. :-)
> 
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> 
> ---
> This patch is basically the result of merge of the former two:
> cmd64x-remove-brokem-sw-mw-dma-support.patch and
> cmd64x-add-back-mwdma-support.patch (minus the part removing the timing register
> setup form the init_chipset() method -- that's been moved to another patch).
> Has been (at last!) tested on PCI-649.

applied

      reply	other threads:[~2007-04-23 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 21:00 [PATCH] (pata-2.6 fix queue) cmd64x: remove broken SW/MW DMA support Sergei Shtylyov
2007-04-14 19:09 ` [PATCH pata-2.6] cmd64x: fix multiword and remove single-word " Sergei Shtylyov
2007-04-23 21:49   ` Bartlomiej Zolnierkiewicz [this message]

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=200704232349.44067.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).