On Tue, Aug 26 2008, Jens Axboe wrote:
> On Tue, Aug 26 2008, Jens Axboe wrote:
> > On Tue, Aug 26 2008, Tejun Heo wrote:
> > > Jens Axboe wrote:
> > > > Given that this problem should be going away and that it only really
> > > > matters on very select devices (like this SSD), I think we should just
> > > > add a quick white list for the bridge limits.
> > >
> > > Yeah, it sucks that up & coming SSDs are still using PATA-SATA bridges.
> > > The expectation when adding the wildcard limitation was that those P/S
> > > bridges are not gonna be around for too long and the limit is most
> > > likely not be an actual problem. Oh well...
> >
> > I would hope that only the current generation do that, and to be honest
> > I'm still pretty baffled that they exist :-)
> >
> > > > Below is a quick'n dirty for that...
> > > >
> > > > diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> > > > index 79e3a8e..fe8033a 100644
> > > > --- a/drivers/ata/libata-core.c
> > > > +++ b/drivers/ata/libata-core.c
> > > > @@ -2097,9 +2097,70 @@ retry:
> > > > return rc;
> > > > }
> > > >
> > > > +struct ata_blacklist_entry {
> > > > + const char *model_num;
> > > > + const char *model_rev;
> > > > + unsigned long horkage;
> > > > +};
> > > > +
> > > > +static const struct ata_blacklist_entry ata_bridge_whitelist[] = {
> > > > + /*
> > > > + * The following devices sit behind a bridge, but don't need
> > > > + * transfer rate or size limits applied.
> > > > + */
> > > > + { "Mtron", },
> > > > +
> > > > + /* End Marker */
> > > > + { }
> > > > +};
> > >
> > > Any reason this can't be part of the existing blacklist? It already
> > > supports wildcard matching and all.
> >
> > Sure, just with an inverse flag, I'll do that.
>
> 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.
This one has a better chance of actually working...
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 79e3a8e..f3bda2c 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, ATA_HORKAGE_BRIDGE_OK, },
+
/* 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 */
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
