From: Jeff Garzik <jeff@garzik.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] sata_promise: fix missing PATA cable detection
Date: Thu, 08 Feb 2007 08:50:09 -0500 [thread overview]
Message-ID: <45CB2A91.6050208@garzik.org> (raw)
In-Reply-To: <200702072129.l17LTujt012924@alkaid.it.uu.se>
Mikael Pettersson wrote:
> This patch fixes an oversight which caused sata_promise to
> not perform cable detection on the TX2plus chips' PATA ports.
>
> Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>
>
> ---
>
> This patch adds yet another is-PATA-or-SATA? check, but it's in a
> cold path so shouldn't matter much. This will be cleaned up if/when
> PATA ports and SATA ports start using different ops structures.
>
> --- linux-2.6.20/drivers/ata/sata_promise.c.~1~ 2007-02-07 20:30:20.000000000 +0100
> +++ linux-2.6.20/drivers/ata/sata_promise.c 2007-02-07 20:57:34.000000000 +0100
> @@ -601,6 +601,13 @@ static void pdc_thaw(struct ata_port *ap
> readl(mmio + PDC_CTLSTAT); /* flush */
> }
>
> +static int pdc_pre_reset(struct ata_port *ap)
> +{
> + if (!sata_scr_valid(ap))
> + pdc_pata_cbl_detect(ap);
> + return ata_std_prereset(ap);
> +}
> +
Since it was a bug in the original patch, I just dropped it, waiting for
you to resend the whole thing. That keeps the git history much more clean.
I agree with your comment above -- SATA and PATA ports should use
different ops structures
Jeff
next prev parent reply other threads:[~2007-02-08 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 21:29 [PATCH] sata_promise: fix missing PATA cable detection Mikael Pettersson
2007-02-08 13:50 ` Jeff Garzik [this message]
2007-02-09 9:27 ` Tejun Heo
2007-02-15 23:09 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2007-02-08 14:39 Mikael Pettersson
2007-02-08 15:07 ` Jeff Garzik
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=45CB2A91.6050208@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).