From: Jeff Garzik <jeff@garzik.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Tejun Heo <tj@kernel.org>, Brad Campbell <brad@wasp.net.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org
Subject: Re: libata bridge limits
Date: Tue, 26 Aug 2008 15:36:19 -0400 [thread overview]
Message-ID: <48B45B33.1050703@garzik.org> (raw)
In-Reply-To: <20080826135822.GE20055@kernel.dk>
Jens Axboe wrote:
> OK, something like this. Jeff, if you think this is fine, let me know
> and I'll submit a proper patch with description and so on.
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 79e3a8e..879ceac 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -2100,6 +2100,10 @@ retry:
> static inline u8 ata_dev_knobble(struct ata_device *dev)
> {
> struct ata_port *ap = dev->link->ap;
> +
> + if (ata_dev_blacklisted(dev) & ATA_HORKAGE_BRIDGE_OK)
> + return 0;
> +
> return ((ap->cbl == ATA_CBL_SATA) && (!ata_id_is_sata(dev->id)));
> }
>
> @@ -3998,6 +4002,9 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
> { "TSSTcorp CDDVDW SH-S202N", "SB00", ATA_HORKAGE_IVB, },
> { "TSSTcorp CDDVDW SH-S202N", "SB01", ATA_HORKAGE_IVB, },
>
> + /* Devices that do not need bridging limits applied */
> + { "Mtron", NULL, 0, },
> +
> /* End Marker */
> { }
> };
> diff --git a/include/linux/libata.h b/include/linux/libata.h
> index 225bfc5..9f194c0 100644
> --- a/include/linux/libata.h
> +++ b/include/linux/libata.h
> @@ -364,6 +364,7 @@ enum {
> ATA_HORKAGE_IPM = (1 << 7), /* Link PM problems */
> ATA_HORKAGE_IVB = (1 << 8), /* cbl det validity bit bugs */
> ATA_HORKAGE_STUCK_ERR = (1 << 9), /* stuck ERR on next PACKET */
> + ATA_HORKAGE_BRIDGE_OK = (1 << 10), /* no bridge limits */
>
> /* DMA mask for user DMA control: User visible values; DO NOT
> renumber */
This one seems fine to me...
Jeff
next prev parent reply other threads:[~2008-08-26 19:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 7:28 libata bridge limits Jens Axboe
2008-08-26 9:42 ` Alan Cox
2008-08-26 10:17 ` Jens Axboe
2008-08-26 10:43 ` Tejun Heo
2008-08-26 10:38 ` Alan Cox
2008-08-26 11:23 ` Tejun Heo
2008-08-26 12:25 ` Alan Cox
2008-08-26 12:45 ` Tejun Heo
2008-08-26 17:25 ` Gwendal Grignou
2008-08-26 17:45 ` James Bottomley
2008-08-26 19:25 ` Gwendal Grignou
2008-08-26 20:55 ` James Bottomley
2008-08-26 12:32 ` Brad Campbell
2008-08-26 12:48 ` Jens Axboe
2008-08-26 12:55 ` Tejun Heo
2008-08-26 13:06 ` Jens Axboe
2008-08-26 13:58 ` Jens Axboe
2008-08-26 14:20 ` Tejun Heo
2008-08-26 14:26 ` Jens Axboe
2008-08-26 14:25 ` Jens Axboe
2008-08-26 19:36 ` Jeff Garzik [this message]
2008-08-26 22:37 ` Mark Lord
2008-08-27 13:23 ` Jens Axboe
2008-10-31 5:45 ` 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=48B45B33.1050703@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=brad@wasp.net.au \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).