All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 13/15] ide: add ata_set{_max}_pio()
Date: Sat, 30 Jun 2007 16:03:27 -0400	[thread overview]
Message-ID: <4686B70F.9080606@garzik.org> (raw)
In-Reply-To: <200706302111.29322.bzolnier@gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> * Add IDE_HFLAG_ABUSE_{PREFETCH,FAST_DEVSEL,DMA_MODES} flags
>   and set them in ht6560, cmd640, cmd64x and sc1200 host drivers.
> 
> * Add set_pio_mode_abuse() for checking if host driver has a non-standard
>   ->tuneproc() implementation and use it in do_special().
> 
> * Add ata_set_pio() for setting PIO mode (it uses hwif->pio_mask to find
>   the maximum PIO mode supported by the host), also add ata_set_max_pio()
>   wrapper for ata_set_pio() to use for auto-tuning.  Convert users of
>   ->tuneproc to use ata_set{_max}_pio() where possible.  This leaves only
>   do_special(), set_using_pio(), ide_hwif_restore() and ata_set_pio() as
>   a direct users of ->tuneproc.
> 
> * Remove no longer needed ide_get_best_pio_mode() calls and printk-s
>   reporting PIO mode selected from ->tuneproc implementations.
> 
> * Rename ->tuneproc hook to ->set_pio_mode and make 'pio' argument const.
> 
> * Remove stale comment from ide_config_drive_speed().
> 
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>

It seems highly inconsistent for drivers/ide to use the "ide_" prefix 
the vast majority of the time, but then "ata_" prefix in this one case, 
particularly when libata uses the "ata_" prefix almost exclusively.

	Jeff




  reply	other threads:[~2007-06-30 20:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30 19:11 [PATCH 13/15] ide: add ata_set{_max}_pio() Bartlomiej Zolnierkiewicz
2007-06-30 20:03 ` Jeff Garzik [this message]
2007-06-30 20:31   ` Bartlomiej Zolnierkiewicz
2007-06-30 20:21     ` Jeff Garzik
2007-06-30 20:46       ` Bartlomiej Zolnierkiewicz
2007-06-30 22:39     ` Alan Cox

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=4686B70F.9080606@garzik.org \
    --to=jeff@garzik.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.