linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/7] it821x: use ide_get_pair_dev() helper
Date: Mon, 22 Dec 2008 13:11:38 +0300	[thread overview]
Message-ID: <494F67DA.2090903@ru.mvista.com> (raw)
In-Reply-To: <20081221210029.23795.66085.sendpatchset@localhost.localdomain>

Bartlomiej Zolnierkiewicz wrote:

> Because presence of the peer device was not checked in
> it821x_set_pio_mode() PIO0 mode was used for taskfile PIO
> in single device configurations.
>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
>   

Acked-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>

> Index: b/drivers/ide/it821x.c
> ===================================================================
> --- a/drivers/ide/it821x.c
> +++ b/drivers/ide/it821x.c
> @@ -167,12 +167,10 @@ static void it821x_clock_strategy(ide_dr
>  	ide_hwif_t *hwif = drive->hwif;
>  	struct pci_dev *dev = to_pci_dev(hwif->dev);
>  	struct it821x_dev *itdev = ide_get_hwifdata(hwif);
> -	ide_drive_t *pair;
> +	ide_drive_t *pair = ide_get_pair_dev(drive);
>  	int clock, altclock, sel = 0;
>  	u8 unit = drive->dn & 1, v;
>  
> -	pair = &hwif->drives[1 - unit];
> -
>  	if(itdev->want[0][0] > itdev->want[1][0]) {
>  		clock = itdev->want[0][1];
>  		altclock = itdev->want[1][1];
> @@ -239,15 +237,13 @@ static void it821x_set_pio_mode(ide_driv
>  {
>  	ide_hwif_t *hwif = drive->hwif;
>  	struct it821x_dev *itdev = ide_get_hwifdata(hwif);
> -	ide_drive_t *pair;
> +	ide_drive_t *pair = ide_get_pair_dev(drive);
>  	u8 unit = drive->dn & 1, set_pio = pio;
>  
>  	/* Spec says 89 ref driver uses 88 */
>  	static u16 pio_timings[]= { 0xAA88, 0xA382, 0xA181, 0x3332, 0x3121 };
>  	static u8 pio_want[]    = { ATA_66, ATA_66, ATA_66, ATA_66, ATA_ANY };
>  
> -	pair = &hwif->drives[1 - unit];
> -
>  	/*
>  	 * Compute the best PIO mode we can for a given device. We must
>  	 * pick a speed that does not cause problems with the other device

  I wonder why this driver was testing 'pair', there was absolutely no 
chance for it being NULL. :-)

MBR, Sergei



  reply	other threads:[~2008-12-22 10:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-21 21:00 [PATCH 1/7] amd74xx: use ide_get_pair_dev() helper Bartlomiej Zolnierkiewicz
2008-12-21 21:00 ` [PATCH 2/7] cmd640: " Bartlomiej Zolnierkiewicz
2008-12-22 10:08   ` Sergei Shtylyov
2008-12-21 21:00 ` [PATCH 3/7] cmd64x: " Bartlomiej Zolnierkiewicz
2008-12-22 10:07   ` Sergei Shtylyov
2008-12-21 21:00 ` [PATCH 4/7] it821x: " Bartlomiej Zolnierkiewicz
2008-12-22 10:11   ` Sergei Shtylyov [this message]
2008-12-21 21:00 ` [PATCH 5/7] ide: NUMA aware allocation of host and port structures Bartlomiej Zolnierkiewicz
2008-12-21 21:00 ` [PATCH 6/7] ide: dynamic allocation of device structures Bartlomiej Zolnierkiewicz
2008-12-21 21:00 ` [PATCH 7/7] ide: add port and host iterators Bartlomiej Zolnierkiewicz
2008-12-22 10:09 ` [PATCH 1/7] amd74xx: use ide_get_pair_dev() helper Sergei Shtylyov

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=494F67DA.2090903@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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 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).