linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: bzolnier@gmail.com, wildy@petra.hos.u-szeged.hu,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH pata-2.6 fix] hpt366: disallow Ultra133 for HPT374
Date: Wed, 6 Jun 2007 18:54:55 -0700	[thread overview]
Message-ID: <20070606185455.fc264488.akpm@linux-foundation.org> (raw)
In-Reply-To: <200706062353.28707.sshtylyov@ru.mvista.com>

On Wed, 6 Jun 2007 23:53:28 +0400 Sergei Shtylyov <sshtylyov@ru.mvista.com> wrote:

> Eliminate UltraATA/133 support for HPT374 -- the chip isn't capable of this mode
> according to the manual, and doesn't even seem to tolerate 66 MHz DPLL clock...
> 
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> 
> ---
>  drivers/ide/pci/hpt366.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> Index: linux-2.6/drivers/ide/pci/hpt366.c
> ===================================================================
> --- linux-2.6.orig/drivers/ide/pci/hpt366.c
> +++ linux-2.6/drivers/ide/pci/hpt366.c
> @@ -1,5 +1,5 @@
>  /*
> - * linux/drivers/ide/pci/hpt366.c		Version 1.03	May 4, 2007
> + * linux/drivers/ide/pci/hpt366.c		Version 1.04	Jun 4, 2007

argh.  Please just delete this version numbering.  It's a sure-fire way of
maximising patch conflicts.

It's 1.10 in Bart's tree.

>   * Copyright (C) 1999-2003		Andre Hedrick <andre@linux-ide.org>
>   * Portions Copyright (C) 2001	        Sun Microsystems, Inc.
> @@ -106,7 +106,8 @@
>   *   switch  to calculating  PCI clock frequency based on the chip's base DPLL
>   *   frequency
>   * - switch to using the  DPLL clock and enable UltraATA/133 mode by default on
> - *   anything  newer than HPT370/A
> + *   anything  newer than HPT370/A (except HPT374 that is not capable of this
> + *   mode according to the manual)
>   * - fold PCI clock detection and DPLL setup code into init_chipset_hpt366(),
>   *   also fixing the interchanged 25/40 MHz PCI clock cases for HPT36x chips;
>   *   unify HPT36x/37x timing setup code and the speedproc handlers by joining
> @@ -365,7 +366,6 @@ static u32 sixty_six_base_hpt37x[] = {
>  };
>  
>  #define HPT366_DEBUG_DRIVE_INFO		0
> -#define HPT374_ALLOW_ATA133_6		1
>  #define HPT371_ALLOW_ATA133_6		1
>  #define HPT302_ALLOW_ATA133_6		1
>  #define HPT372_ALLOW_ATA133_6		1
> @@ -450,7 +450,7 @@ static struct hpt_info hpt370a __devinit
>  
>  static struct hpt_info hpt374 __devinitdata = {
>  	.chip_type	= HPT374,
> -	.max_mode	= HPT374_ALLOW_ATA133_6 ? 4 : 3,
> +	.max_mode	= 3,
>  	.dpll_clk	= 48,
>  	.settings	= hpt37x_settings
>  };

The code in Bart's tree has

static struct hpt_info hpt374 __devinitdata = {
	.chip_type	= HPT374,
	.max_ultra	= HPT374_ALLOW_ATA133_6 ? 6 : 5,
	.dpll_clk	= 48,
	.settings	= hpt37x_settings
};

I can handle the renaming, but note that Bart's tree has different values
as well.


  reply	other threads:[~2007-06-07  1:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 19:53 [PATCH pata-2.6 fix] hpt366: disallow Ultra133 for HPT374 Sergei Shtylyov
2007-06-07  1:54 ` Andrew Morton [this message]
2007-06-07 13:26   ` Sergei Shtylyov
2007-06-08 12:44 ` 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=20070606185455.fc264488.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.com \
    --cc=wildy@petra.hos.u-szeged.hu \
    /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).