2006-08-30 05:12:40 +07:00
|
|
|
/*
|
|
|
|
* Libata driver for the highpoint 37x and 30x UDMA66 ATA controllers.
|
|
|
|
*
|
|
|
|
* This driver is heavily based upon:
|
|
|
|
*
|
|
|
|
* linux/drivers/ide/pci/hpt366.c Version 0.36 April 25, 2003
|
|
|
|
*
|
|
|
|
* Copyright (C) 1999-2003 Andre Hedrick <andre@linux-ide.org>
|
|
|
|
* Portions Copyright (C) 2001 Sun Microsystems, Inc.
|
|
|
|
* Portions Copyright (C) 2003 Red Hat Inc
|
2007-08-10 23:58:46 +07:00
|
|
|
* Portions Copyright (C) 2005-2007 MontaVista Software, Inc.
|
2006-08-30 05:12:40 +07:00
|
|
|
*
|
|
|
|
* TODO
|
2007-08-10 23:58:46 +07:00
|
|
|
* Look into engine reset on timeout errors. Should not be required.
|
2006-08-30 05:12:40 +07:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/pci.h>
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/blkdev.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <scsi/scsi_host.h>
|
|
|
|
#include <linux/libata.h>
|
|
|
|
|
|
|
|
#define DRV_NAME "pata_hpt37x"
|
2008-02-27 04:35:54 +07:00
|
|
|
#define DRV_VERSION "0.6.11"
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
struct hpt_clock {
|
|
|
|
u8 xfer_speed;
|
|
|
|
u32 timing;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct hpt_chip {
|
|
|
|
const char *name;
|
|
|
|
unsigned int base;
|
|
|
|
struct hpt_clock const *clocks[4];
|
|
|
|
};
|
|
|
|
|
|
|
|
/* key for bus clock timings
|
|
|
|
* bit
|
|
|
|
* 0:3 data_high_time. inactive time of DIOW_/DIOR_ for PIO and MW
|
|
|
|
* DMA. cycles = value + 1
|
|
|
|
* 4:8 data_low_time. active time of DIOW_/DIOR_ for PIO and MW
|
|
|
|
* DMA. cycles = value + 1
|
|
|
|
* 9:12 cmd_high_time. inactive time of DIOW_/DIOR_ during task file
|
|
|
|
* register access.
|
|
|
|
* 13:17 cmd_low_time. active time of DIOW_/DIOR_ during task file
|
|
|
|
* register access.
|
|
|
|
* 18:21 udma_cycle_time. clock freq and clock cycles for UDMA xfer.
|
|
|
|
* during task file register access.
|
|
|
|
* 22:24 pre_high_time. time to initialize 1st cycle for PIO and MW DMA
|
|
|
|
* xfer.
|
|
|
|
* 25:27 cmd_pre_high_time. time to initialize 1st PIO cycle for task
|
|
|
|
* register access.
|
|
|
|
* 28 UDMA enable
|
|
|
|
* 29 DMA enable
|
|
|
|
* 30 PIO_MST enable. if set, the chip is in bus master mode during
|
|
|
|
* PIO.
|
|
|
|
* 31 FIFO enable.
|
|
|
|
*/
|
|
|
|
|
2007-03-09 06:28:52 +07:00
|
|
|
static struct hpt_clock hpt37x_timings_33[] = {
|
|
|
|
{ XFER_UDMA_6, 0x12446231 }, /* 0x12646231 ?? */
|
|
|
|
{ XFER_UDMA_5, 0x12446231 },
|
|
|
|
{ XFER_UDMA_4, 0x12446231 },
|
|
|
|
{ XFER_UDMA_3, 0x126c6231 },
|
|
|
|
{ XFER_UDMA_2, 0x12486231 },
|
|
|
|
{ XFER_UDMA_1, 0x124c6233 },
|
|
|
|
{ XFER_UDMA_0, 0x12506297 },
|
|
|
|
|
|
|
|
{ XFER_MW_DMA_2, 0x22406c31 },
|
|
|
|
{ XFER_MW_DMA_1, 0x22406c33 },
|
|
|
|
{ XFER_MW_DMA_0, 0x22406c97 },
|
|
|
|
|
|
|
|
{ XFER_PIO_4, 0x06414e31 },
|
|
|
|
{ XFER_PIO_3, 0x06414e42 },
|
|
|
|
{ XFER_PIO_2, 0x06414e53 },
|
|
|
|
{ XFER_PIO_1, 0x06814e93 },
|
|
|
|
{ XFER_PIO_0, 0x06814ea7 }
|
2006-08-30 05:12:40 +07:00
|
|
|
};
|
|
|
|
|
2007-03-09 06:28:52 +07:00
|
|
|
static struct hpt_clock hpt37x_timings_50[] = {
|
|
|
|
{ XFER_UDMA_6, 0x12848242 },
|
|
|
|
{ XFER_UDMA_5, 0x12848242 },
|
|
|
|
{ XFER_UDMA_4, 0x12ac8242 },
|
|
|
|
{ XFER_UDMA_3, 0x128c8242 },
|
|
|
|
{ XFER_UDMA_2, 0x120c8242 },
|
|
|
|
{ XFER_UDMA_1, 0x12148254 },
|
|
|
|
{ XFER_UDMA_0, 0x121882ea },
|
|
|
|
|
|
|
|
{ XFER_MW_DMA_2, 0x22808242 },
|
|
|
|
{ XFER_MW_DMA_1, 0x22808254 },
|
|
|
|
{ XFER_MW_DMA_0, 0x228082ea },
|
|
|
|
|
|
|
|
{ XFER_PIO_4, 0x0a81f442 },
|
|
|
|
{ XFER_PIO_3, 0x0a81f443 },
|
|
|
|
{ XFER_PIO_2, 0x0a81f454 },
|
|
|
|
{ XFER_PIO_1, 0x0ac1f465 },
|
|
|
|
{ XFER_PIO_0, 0x0ac1f48a }
|
2006-08-30 05:12:40 +07:00
|
|
|
};
|
|
|
|
|
2007-03-09 06:28:52 +07:00
|
|
|
static struct hpt_clock hpt37x_timings_66[] = {
|
|
|
|
{ XFER_UDMA_6, 0x1c869c62 },
|
|
|
|
{ XFER_UDMA_5, 0x1cae9c62 }, /* 0x1c8a9c62 */
|
|
|
|
{ XFER_UDMA_4, 0x1c8a9c62 },
|
|
|
|
{ XFER_UDMA_3, 0x1c8e9c62 },
|
|
|
|
{ XFER_UDMA_2, 0x1c929c62 },
|
|
|
|
{ XFER_UDMA_1, 0x1c9a9c62 },
|
|
|
|
{ XFER_UDMA_0, 0x1c829c62 },
|
|
|
|
|
|
|
|
{ XFER_MW_DMA_2, 0x2c829c62 },
|
|
|
|
{ XFER_MW_DMA_1, 0x2c829c66 },
|
|
|
|
{ XFER_MW_DMA_0, 0x2c829d2e },
|
|
|
|
|
|
|
|
{ XFER_PIO_4, 0x0c829c62 },
|
|
|
|
{ XFER_PIO_3, 0x0c829c84 },
|
|
|
|
{ XFER_PIO_2, 0x0c829ca6 },
|
|
|
|
{ XFER_PIO_1, 0x0d029d26 },
|
|
|
|
{ XFER_PIO_0, 0x0d029d5e }
|
2006-08-30 05:12:40 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
static const struct hpt_chip hpt370 = {
|
|
|
|
"HPT370",
|
|
|
|
48,
|
|
|
|
{
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_33,
|
2006-08-30 05:12:40 +07:00
|
|
|
NULL,
|
|
|
|
NULL,
|
2007-04-26 14:19:25 +07:00
|
|
|
NULL
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct hpt_chip hpt370a = {
|
|
|
|
"HPT370A",
|
|
|
|
48,
|
|
|
|
{
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_33,
|
2006-08-30 05:12:40 +07:00
|
|
|
NULL,
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_50,
|
2007-04-26 14:19:25 +07:00
|
|
|
NULL
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct hpt_chip hpt372 = {
|
|
|
|
"HPT372",
|
|
|
|
55,
|
|
|
|
{
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_33,
|
2006-08-30 05:12:40 +07:00
|
|
|
NULL,
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_50,
|
|
|
|
hpt37x_timings_66
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct hpt_chip hpt302 = {
|
|
|
|
"HPT302",
|
|
|
|
66,
|
|
|
|
{
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_33,
|
2006-08-30 05:12:40 +07:00
|
|
|
NULL,
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_50,
|
|
|
|
hpt37x_timings_66
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct hpt_chip hpt371 = {
|
|
|
|
"HPT371",
|
|
|
|
66,
|
|
|
|
{
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_33,
|
2006-08-30 05:12:40 +07:00
|
|
|
NULL,
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_50,
|
|
|
|
hpt37x_timings_66
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct hpt_chip hpt372a = {
|
|
|
|
"HPT372A",
|
|
|
|
66,
|
|
|
|
{
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_33,
|
2006-08-30 05:12:40 +07:00
|
|
|
NULL,
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_50,
|
|
|
|
hpt37x_timings_66
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct hpt_chip hpt374 = {
|
|
|
|
"HPT374",
|
|
|
|
48,
|
|
|
|
{
|
2007-03-09 06:28:52 +07:00
|
|
|
hpt37x_timings_33,
|
2006-08-30 05:12:40 +07:00
|
|
|
NULL,
|
|
|
|
NULL,
|
|
|
|
NULL
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt37x_find_mode - reset the hpt37x bus
|
|
|
|
* @ap: ATA port
|
|
|
|
* @speed: transfer mode
|
|
|
|
*
|
|
|
|
* Return the 32bit register programming information for this channel
|
|
|
|
* that matches the speed provided.
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static u32 hpt37x_find_mode(struct ata_port *ap, int speed)
|
|
|
|
{
|
|
|
|
struct hpt_clock *clocks = ap->host->private_data;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
while(clocks->xfer_speed) {
|
|
|
|
if (clocks->xfer_speed == speed)
|
|
|
|
return clocks->timing;
|
|
|
|
clocks++;
|
|
|
|
}
|
|
|
|
BUG();
|
|
|
|
return 0xffffffffU; /* silence compiler warning */
|
|
|
|
}
|
|
|
|
|
|
|
|
static int hpt_dma_blacklisted(const struct ata_device *dev, char *modestr, const char *list[])
|
|
|
|
{
|
2007-01-02 18:19:40 +07:00
|
|
|
unsigned char model_num[ATA_ID_PROD_LEN + 1];
|
2006-08-30 05:12:40 +07:00
|
|
|
int i = 0;
|
|
|
|
|
2007-01-02 18:19:40 +07:00
|
|
|
ata_id_c_string(dev->id, model_num, ATA_ID_PROD, sizeof(model_num));
|
2006-08-30 05:12:40 +07:00
|
|
|
|
2007-01-02 18:19:40 +07:00
|
|
|
while (list[i] != NULL) {
|
|
|
|
if (!strcmp(list[i], model_num)) {
|
2006-08-31 11:03:49 +07:00
|
|
|
printk(KERN_WARNING DRV_NAME ": %s is not supported for %s.\n",
|
2006-08-30 05:12:40 +07:00
|
|
|
modestr, list[i]);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
i++;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const char *bad_ata33[] = {
|
|
|
|
"Maxtor 92720U8", "Maxtor 92040U6", "Maxtor 91360U4", "Maxtor 91020U3", "Maxtor 90845U3", "Maxtor 90650U2",
|
|
|
|
"Maxtor 91360D8", "Maxtor 91190D7", "Maxtor 91020D6", "Maxtor 90845D5", "Maxtor 90680D4", "Maxtor 90510D3", "Maxtor 90340D2",
|
|
|
|
"Maxtor 91152D8", "Maxtor 91008D7", "Maxtor 90845D6", "Maxtor 90840D6", "Maxtor 90720D5", "Maxtor 90648D5", "Maxtor 90576D4",
|
|
|
|
"Maxtor 90510D4",
|
|
|
|
"Maxtor 90432D3", "Maxtor 90288D2", "Maxtor 90256D2",
|
|
|
|
"Maxtor 91000D8", "Maxtor 90910D8", "Maxtor 90875D7", "Maxtor 90840D7", "Maxtor 90750D6", "Maxtor 90625D5", "Maxtor 90500D4",
|
|
|
|
"Maxtor 91728D8", "Maxtor 91512D7", "Maxtor 91303D6", "Maxtor 91080D5", "Maxtor 90845D4", "Maxtor 90680D4", "Maxtor 90648D3", "Maxtor 90432D2",
|
|
|
|
NULL
|
|
|
|
};
|
|
|
|
|
|
|
|
static const char *bad_ata100_5[] = {
|
|
|
|
"IBM-DTLA-307075",
|
|
|
|
"IBM-DTLA-307060",
|
|
|
|
"IBM-DTLA-307045",
|
|
|
|
"IBM-DTLA-307030",
|
|
|
|
"IBM-DTLA-307020",
|
|
|
|
"IBM-DTLA-307015",
|
|
|
|
"IBM-DTLA-305040",
|
|
|
|
"IBM-DTLA-305030",
|
|
|
|
"IBM-DTLA-305020",
|
|
|
|
"IC35L010AVER07-0",
|
|
|
|
"IC35L020AVER07-0",
|
|
|
|
"IC35L030AVER07-0",
|
|
|
|
"IC35L040AVER07-0",
|
|
|
|
"IC35L060AVER07-0",
|
|
|
|
"WDC AC310200R",
|
|
|
|
NULL
|
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt370_filter - mode selection filter
|
|
|
|
* @adev: ATA device
|
|
|
|
*
|
|
|
|
* Block UDMA on devices that cause trouble with this controller.
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2007-03-09 21:34:07 +07:00
|
|
|
static unsigned long hpt370_filter(struct ata_device *adev, unsigned long mask)
|
2006-08-30 05:12:40 +07:00
|
|
|
{
|
2007-01-06 07:37:01 +07:00
|
|
|
if (adev->class == ATA_DEV_ATA) {
|
2006-08-30 05:12:40 +07:00
|
|
|
if (hpt_dma_blacklisted(adev, "UDMA", bad_ata33))
|
|
|
|
mask &= ~ATA_MASK_UDMA;
|
|
|
|
if (hpt_dma_blacklisted(adev, "UDMA100", bad_ata100_5))
|
2008-02-27 04:35:54 +07:00
|
|
|
mask &= ~(0xE0 << ATA_SHIFT_UDMA);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
2008-04-07 20:47:16 +07:00
|
|
|
return ata_bmdma_mode_filter(adev, mask);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt370a_filter - mode selection filter
|
|
|
|
* @adev: ATA device
|
|
|
|
*
|
|
|
|
* Block UDMA on devices that cause trouble with this controller.
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2007-03-09 21:34:07 +07:00
|
|
|
static unsigned long hpt370a_filter(struct ata_device *adev, unsigned long mask)
|
2006-08-30 05:12:40 +07:00
|
|
|
{
|
2007-11-06 05:53:38 +07:00
|
|
|
if (adev->class == ATA_DEV_ATA) {
|
2006-08-30 05:12:40 +07:00
|
|
|
if (hpt_dma_blacklisted(adev, "UDMA100", bad_ata100_5))
|
2008-02-27 04:35:54 +07:00
|
|
|
mask &= ~(0xE0 << ATA_SHIFT_UDMA);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
2008-04-07 20:47:16 +07:00
|
|
|
return ata_bmdma_mode_filter(adev, mask);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/**
|
|
|
|
* hpt37x_pre_reset - reset the hpt37x bus
|
2007-08-06 16:36:23 +07:00
|
|
|
* @link: ATA link to reset
|
libata: add deadline support to prereset and reset methods
Add @deadline to prereset and reset methods and make them honor it.
ata_wait_ready() which directly takes @deadline is implemented to be
used as the wait function. This patch is in preparation for EH timing
improvements.
* ata_wait_ready() never does busy sleep. It's only used from EH and
no wait in EH is that urgent. This function also prints 'be
patient' message automatically after 5 secs of waiting if more than
3 secs is remaining till deadline.
* ata_bus_post_reset() now fails with error code if any of its wait
fails. This is important because earlier reset tries will have
shorter timeout than the spec requires. If a device fails to
respond before the short timeout, reset should be retried with
longer timeout rather than silently ignoring the device.
There are three behavior differences.
1. Timeout is applied to both devices at once, not separately. This
is more consistent with what the spec says.
2. When a device passes devchk but fails to become ready before
deadline. Previouly, post_reset would just succeed and let
device classification remove the device. New code fails the
reset thus causing reset retry. After a few times, EH will give
up disabling the port.
3. When slave device passes devchk but fails to become accessible
(TF-wise) after reset. Original code disables dev1 after 30s
timeout and continues as if the device doesn't exist, while the
patched code fails reset. When this happens, new code fails
reset on whole port rather than proceeding with only the primary
device.
If the failing device is suffering transient problems, new code
retries reset which is a better behavior. If the failing device is
actually broken, the net effect is identical to it, but not to the
other device sharing the channel. In the previous code, reset would
have succeeded after 30s thus detecting the working one. In the new
code, reset fails and whole port gets disabled. IMO, it's a
pathological case anyway (broken device sharing bus with working
one) and doesn't really matter.
* ata_bus_softreset() is changed to return error code from
ata_bus_post_reset(). It used to return 0 unconditionally.
* Spin up waiting is to be removed and not converted to honor
deadline.
* To be on the safe side, deadline is set to 40s for the time being.
Signed-off-by: Tejun Heo <htejun@gmail.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-02-02 14:50:52 +07:00
|
|
|
* @deadline: deadline jiffies for the operation
|
2006-08-30 05:12:40 +07:00
|
|
|
*
|
|
|
|
* Perform the initial reset handling for the 370/372 and 374 func 0
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2007-08-06 16:36:23 +07:00
|
|
|
static int hpt37x_pre_reset(struct ata_link *link, unsigned long deadline)
|
2006-08-30 05:12:40 +07:00
|
|
|
{
|
|
|
|
u8 scr2, ata66;
|
2007-08-06 16:36:23 +07:00
|
|
|
struct ata_port *ap = link->ap;
|
2006-08-30 05:12:40 +07:00
|
|
|
struct pci_dev *pdev = to_pci_dev(ap->host->dev);
|
2006-11-08 23:18:26 +07:00
|
|
|
static const struct pci_bits hpt37x_enable_bits[] = {
|
|
|
|
{ 0x50, 1, 0x04, 0x04 },
|
|
|
|
{ 0x54, 1, 0x04, 0x04 }
|
|
|
|
};
|
|
|
|
if (!pci_test_config_bits(pdev, &hpt37x_enable_bits[ap->port_no]))
|
|
|
|
return -ENOENT;
|
2006-12-11 23:14:06 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
pci_read_config_byte(pdev, 0x5B, &scr2);
|
|
|
|
pci_write_config_byte(pdev, 0x5B, scr2 & ~0x01);
|
|
|
|
/* Cable register now active */
|
|
|
|
pci_read_config_byte(pdev, 0x5A, &ata66);
|
|
|
|
/* Restore state */
|
|
|
|
pci_write_config_byte(pdev, 0x5B, scr2);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2007-11-19 21:39:13 +07:00
|
|
|
if (ata66 & (2 >> ap->port_no))
|
2006-08-30 05:12:40 +07:00
|
|
|
ap->cbl = ATA_CBL_PATA40;
|
|
|
|
else
|
|
|
|
ap->cbl = ATA_CBL_PATA80;
|
|
|
|
|
|
|
|
/* Reset the state machine */
|
2007-03-09 06:28:52 +07:00
|
|
|
pci_write_config_byte(pdev, 0x50 + 4 * ap->port_no, 0x37);
|
2006-08-30 05:12:40 +07:00
|
|
|
udelay(100);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2008-04-07 20:47:16 +07:00
|
|
|
return ata_sff_prereset(link, deadline);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
static int hpt374_fn1_pre_reset(struct ata_link *link, unsigned long deadline)
|
2006-08-30 05:12:40 +07:00
|
|
|
{
|
2006-11-08 23:18:26 +07:00
|
|
|
static const struct pci_bits hpt37x_enable_bits[] = {
|
|
|
|
{ 0x50, 1, 0x04, 0x04 },
|
|
|
|
{ 0x54, 1, 0x04, 0x04 }
|
|
|
|
};
|
2007-11-06 05:53:38 +07:00
|
|
|
u16 mcr3;
|
2006-08-30 05:12:40 +07:00
|
|
|
u8 ata66;
|
2007-08-06 16:36:23 +07:00
|
|
|
struct ata_port *ap = link->ap;
|
2006-08-30 05:12:40 +07:00
|
|
|
struct pci_dev *pdev = to_pci_dev(ap->host->dev);
|
2007-11-06 05:53:38 +07:00
|
|
|
unsigned int mcrbase = 0x50 + 4 * ap->port_no;
|
2006-11-08 23:18:26 +07:00
|
|
|
|
|
|
|
if (!pci_test_config_bits(pdev, &hpt37x_enable_bits[ap->port_no]))
|
|
|
|
return -ENOENT;
|
2006-12-11 23:14:06 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Do the extra channel work */
|
2007-11-06 05:53:38 +07:00
|
|
|
pci_read_config_word(pdev, mcrbase + 2, &mcr3);
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Set bit 15 of 0x52 to enable TCBLID as input
|
|
|
|
*/
|
2007-11-06 05:53:38 +07:00
|
|
|
pci_write_config_word(pdev, mcrbase + 2, mcr3 | 0x8000);
|
2006-08-30 05:12:40 +07:00
|
|
|
pci_read_config_byte(pdev, 0x5A, &ata66);
|
|
|
|
/* Reset TCBLID/FCBLID to output */
|
2007-12-20 00:50:32 +07:00
|
|
|
pci_write_config_word(pdev, mcrbase + 2, mcr3);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2007-11-06 05:53:38 +07:00
|
|
|
if (ata66 & (2 >> ap->port_no))
|
2006-08-30 05:12:40 +07:00
|
|
|
ap->cbl = ATA_CBL_PATA40;
|
|
|
|
else
|
|
|
|
ap->cbl = ATA_CBL_PATA80;
|
|
|
|
|
|
|
|
/* Reset the state machine */
|
2007-03-09 06:28:52 +07:00
|
|
|
pci_write_config_byte(pdev, 0x50 + 4 * ap->port_no, 0x37);
|
2006-08-30 05:12:40 +07:00
|
|
|
udelay(100);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2008-04-07 20:47:16 +07:00
|
|
|
return ata_sff_prereset(link, deadline);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt370_set_piomode - PIO setup
|
|
|
|
* @ap: ATA interface
|
|
|
|
* @adev: device on the interface
|
|
|
|
*
|
2006-08-31 11:03:49 +07:00
|
|
|
* Perform PIO mode setup.
|
2006-08-30 05:12:40 +07:00
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static void hpt370_set_piomode(struct ata_port *ap, struct ata_device *adev)
|
|
|
|
{
|
|
|
|
struct pci_dev *pdev = to_pci_dev(ap->host->dev);
|
|
|
|
u32 addr1, addr2;
|
|
|
|
u32 reg;
|
|
|
|
u32 mode;
|
|
|
|
u8 fast;
|
|
|
|
|
|
|
|
addr1 = 0x40 + 4 * (adev->devno + 2 * ap->port_no);
|
|
|
|
addr2 = 0x51 + 4 * ap->port_no;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Fast interrupt prediction disable, hold off interrupt disable */
|
|
|
|
pci_read_config_byte(pdev, addr2, &fast);
|
|
|
|
fast &= ~0x02;
|
|
|
|
fast |= 0x01;
|
|
|
|
pci_write_config_byte(pdev, addr2, fast);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
pci_read_config_dword(pdev, addr1, ®);
|
|
|
|
mode = hpt37x_find_mode(ap, adev->pio_mode);
|
|
|
|
mode &= ~0x8000000; /* No FIFO in PIO */
|
|
|
|
mode &= ~0x30070000; /* Leave config bits alone */
|
|
|
|
reg &= 0x30070000; /* Strip timing bits */
|
|
|
|
pci_write_config_dword(pdev, addr1, reg | mode);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt370_set_dmamode - DMA timing setup
|
|
|
|
* @ap: ATA interface
|
|
|
|
* @adev: Device being configured
|
|
|
|
*
|
|
|
|
* Set up the channel for MWDMA or UDMA modes. Much the same as with
|
|
|
|
* PIO, load the mode number and then set MWDMA or UDMA flag.
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static void hpt370_set_dmamode(struct ata_port *ap, struct ata_device *adev)
|
|
|
|
{
|
|
|
|
struct pci_dev *pdev = to_pci_dev(ap->host->dev);
|
|
|
|
u32 addr1, addr2;
|
|
|
|
u32 reg;
|
|
|
|
u32 mode;
|
|
|
|
u8 fast;
|
|
|
|
|
|
|
|
addr1 = 0x40 + 4 * (adev->devno + 2 * ap->port_no);
|
|
|
|
addr2 = 0x51 + 4 * ap->port_no;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Fast interrupt prediction disable, hold off interrupt disable */
|
|
|
|
pci_read_config_byte(pdev, addr2, &fast);
|
|
|
|
fast &= ~0x02;
|
|
|
|
fast |= 0x01;
|
|
|
|
pci_write_config_byte(pdev, addr2, fast);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
pci_read_config_dword(pdev, addr1, ®);
|
|
|
|
mode = hpt37x_find_mode(ap, adev->dma_mode);
|
|
|
|
mode |= 0x8000000; /* FIFO in MWDMA or UDMA */
|
|
|
|
mode &= ~0xC0000000; /* Leave config bits alone */
|
|
|
|
reg &= 0xC0000000; /* Strip timing bits */
|
|
|
|
pci_write_config_dword(pdev, addr1, reg | mode);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt370_bmdma_start - DMA engine begin
|
|
|
|
* @qc: ATA command
|
|
|
|
*
|
|
|
|
* The 370 and 370A want us to reset the DMA engine each time we
|
|
|
|
* use it. The 372 and later are fine.
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static void hpt370_bmdma_start(struct ata_queued_cmd *qc)
|
|
|
|
{
|
|
|
|
struct ata_port *ap = qc->ap;
|
|
|
|
struct pci_dev *pdev = to_pci_dev(ap->host->dev);
|
|
|
|
pci_write_config_byte(pdev, 0x50 + 4 * ap->port_no, 0x37);
|
|
|
|
udelay(10);
|
|
|
|
ata_bmdma_start(qc);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt370_bmdma_end - DMA engine stop
|
|
|
|
* @qc: ATA command
|
|
|
|
*
|
|
|
|
* Work around the HPT370 DMA engine.
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static void hpt370_bmdma_stop(struct ata_queued_cmd *qc)
|
|
|
|
{
|
|
|
|
struct ata_port *ap = qc->ap;
|
|
|
|
struct pci_dev *pdev = to_pci_dev(ap->host->dev);
|
2007-02-01 13:06:36 +07:00
|
|
|
u8 dma_stat = ioread8(ap->ioaddr.bmdma_addr + 2);
|
2006-08-30 05:12:40 +07:00
|
|
|
u8 dma_cmd;
|
2007-02-01 13:06:36 +07:00
|
|
|
void __iomem *bmdma = ap->ioaddr.bmdma_addr;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
if (dma_stat & 0x01) {
|
|
|
|
udelay(20);
|
2007-02-01 13:06:36 +07:00
|
|
|
dma_stat = ioread8(bmdma + 2);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
if (dma_stat & 0x01) {
|
|
|
|
/* Clear the engine */
|
|
|
|
pci_write_config_byte(pdev, 0x50 + 4 * ap->port_no, 0x37);
|
|
|
|
udelay(10);
|
|
|
|
/* Stop DMA */
|
2007-02-01 13:06:36 +07:00
|
|
|
dma_cmd = ioread8(bmdma );
|
|
|
|
iowrite8(dma_cmd & 0xFE, bmdma);
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Clear Error */
|
2007-02-01 13:06:36 +07:00
|
|
|
dma_stat = ioread8(bmdma + 2);
|
|
|
|
iowrite8(dma_stat | 0x06 , bmdma + 2);
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Clear the engine */
|
|
|
|
pci_write_config_byte(pdev, 0x50 + 4 * ap->port_no, 0x37);
|
|
|
|
udelay(10);
|
|
|
|
}
|
|
|
|
ata_bmdma_stop(qc);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt372_set_piomode - PIO setup
|
|
|
|
* @ap: ATA interface
|
|
|
|
* @adev: device on the interface
|
|
|
|
*
|
2006-08-31 11:03:49 +07:00
|
|
|
* Perform PIO mode setup.
|
2006-08-30 05:12:40 +07:00
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static void hpt372_set_piomode(struct ata_port *ap, struct ata_device *adev)
|
|
|
|
{
|
|
|
|
struct pci_dev *pdev = to_pci_dev(ap->host->dev);
|
|
|
|
u32 addr1, addr2;
|
|
|
|
u32 reg;
|
|
|
|
u32 mode;
|
|
|
|
u8 fast;
|
|
|
|
|
|
|
|
addr1 = 0x40 + 4 * (adev->devno + 2 * ap->port_no);
|
|
|
|
addr2 = 0x51 + 4 * ap->port_no;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Fast interrupt prediction disable, hold off interrupt disable */
|
|
|
|
pci_read_config_byte(pdev, addr2, &fast);
|
|
|
|
fast &= ~0x07;
|
|
|
|
pci_write_config_byte(pdev, addr2, fast);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
pci_read_config_dword(pdev, addr1, ®);
|
|
|
|
mode = hpt37x_find_mode(ap, adev->pio_mode);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
printk("Find mode for %d reports %X\n", adev->pio_mode, mode);
|
|
|
|
mode &= ~0x80000000; /* No FIFO in PIO */
|
|
|
|
mode &= ~0x30070000; /* Leave config bits alone */
|
|
|
|
reg &= 0x30070000; /* Strip timing bits */
|
|
|
|
pci_write_config_dword(pdev, addr1, reg | mode);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt372_set_dmamode - DMA timing setup
|
|
|
|
* @ap: ATA interface
|
|
|
|
* @adev: Device being configured
|
|
|
|
*
|
|
|
|
* Set up the channel for MWDMA or UDMA modes. Much the same as with
|
|
|
|
* PIO, load the mode number and then set MWDMA or UDMA flag.
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static void hpt372_set_dmamode(struct ata_port *ap, struct ata_device *adev)
|
|
|
|
{
|
|
|
|
struct pci_dev *pdev = to_pci_dev(ap->host->dev);
|
|
|
|
u32 addr1, addr2;
|
|
|
|
u32 reg;
|
|
|
|
u32 mode;
|
|
|
|
u8 fast;
|
|
|
|
|
|
|
|
addr1 = 0x40 + 4 * (adev->devno + 2 * ap->port_no);
|
|
|
|
addr2 = 0x51 + 4 * ap->port_no;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Fast interrupt prediction disable, hold off interrupt disable */
|
|
|
|
pci_read_config_byte(pdev, addr2, &fast);
|
|
|
|
fast &= ~0x07;
|
|
|
|
pci_write_config_byte(pdev, addr2, fast);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
pci_read_config_dword(pdev, addr1, ®);
|
|
|
|
mode = hpt37x_find_mode(ap, adev->dma_mode);
|
|
|
|
printk("Find mode for DMA %d reports %X\n", adev->dma_mode, mode);
|
|
|
|
mode &= ~0xC0000000; /* Leave config bits alone */
|
|
|
|
mode |= 0x80000000; /* FIFO in MWDMA or UDMA */
|
|
|
|
reg &= 0xC0000000; /* Strip timing bits */
|
|
|
|
pci_write_config_dword(pdev, addr1, reg | mode);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt37x_bmdma_end - DMA engine stop
|
|
|
|
* @qc: ATA command
|
|
|
|
*
|
|
|
|
* Clean up after the HPT372 and later DMA engine
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static void hpt37x_bmdma_stop(struct ata_queued_cmd *qc)
|
|
|
|
{
|
|
|
|
struct ata_port *ap = qc->ap;
|
|
|
|
struct pci_dev *pdev = to_pci_dev(ap->host->dev);
|
2007-01-06 07:37:01 +07:00
|
|
|
int mscreg = 0x50 + 4 * ap->port_no;
|
2006-08-30 05:12:40 +07:00
|
|
|
u8 bwsr_stat, msc_stat;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
pci_read_config_byte(pdev, 0x6A, &bwsr_stat);
|
|
|
|
pci_read_config_byte(pdev, mscreg, &msc_stat);
|
|
|
|
if (bwsr_stat & (1 << ap->port_no))
|
|
|
|
pci_write_config_byte(pdev, mscreg, msc_stat | 0x30);
|
|
|
|
ata_bmdma_stop(qc);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static struct scsi_host_template hpt37x_sht = {
|
2008-03-25 10:22:49 +07:00
|
|
|
ATA_BMDMA_SHT(DRV_NAME),
|
2006-08-30 05:12:40 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Configuration for HPT370
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static struct ata_port_operations hpt370_port_ops = {
|
libata: implement and use ops inheritance
libata lets low level drivers build ata_port_operations table and
register it with libata core layer. This allows low level drivers
high level of flexibility but also burdens them with lots of
boilerplate entries.
This becomes worse for drivers which support related similar
controllers which differ slightly. They share most of the operations
except for a few. However, the driver still needs to list all
operations for each variant. This results in large number of
duplicate entries, which is not only inefficient but also error-prone
as it becomes very difficult to tell what the actual differences are.
This duplicate boilerplates all over the low level drivers also make
updating the core layer exteremely difficult and error-prone. When
compounded with multi-branched development model, it ends up
accumulating inconsistencies over time. Some of those inconsistencies
cause immediate problems and fixed. Others just remain there dormant
making maintenance increasingly difficult.
To rectify the problem, this patch implements ata_port_operations
inheritance. To allow LLDs to easily re-use their own ops tables
overriding only specific methods, this patch implements poor man's
class inheritance. An ops table has ->inherits field which can be set
to any ops table as long as it doesn't create a loop. When the host
is started, the inheritance chain is followed and any operation which
isn't specified is taken from the nearest ancestor which has it
specified. This operation is called finalization and done only once
per an ops table and the LLD doesn't have to do anything special about
it other than making the ops table non-const such that libata can
update it.
libata provides four base ops tables lower drivers can inherit from -
base, sata, pmp, sff and bmdma. To avoid overriding these ops
accidentaly, these ops are declared const and LLDs should always
inherit these instead of using them directly.
After finalization, all the ops table are identical before and after
the patch except for setting .irq_handler to ata_interrupt in drivers
which didn't use to. The .irq_handler doesn't have any actual effect
and the field will soon be removed by later patch.
* sata_sx4 is still using old style EH and currently doesn't take
advantage of ops inheritance.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:49 +07:00
|
|
|
.inherits = &ata_bmdma_port_ops,
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
.bmdma_start = hpt370_bmdma_start,
|
|
|
|
.bmdma_stop = hpt370_bmdma_stop,
|
|
|
|
|
libata: implement and use ops inheritance
libata lets low level drivers build ata_port_operations table and
register it with libata core layer. This allows low level drivers
high level of flexibility but also burdens them with lots of
boilerplate entries.
This becomes worse for drivers which support related similar
controllers which differ slightly. They share most of the operations
except for a few. However, the driver still needs to list all
operations for each variant. This results in large number of
duplicate entries, which is not only inefficient but also error-prone
as it becomes very difficult to tell what the actual differences are.
This duplicate boilerplates all over the low level drivers also make
updating the core layer exteremely difficult and error-prone. When
compounded with multi-branched development model, it ends up
accumulating inconsistencies over time. Some of those inconsistencies
cause immediate problems and fixed. Others just remain there dormant
making maintenance increasingly difficult.
To rectify the problem, this patch implements ata_port_operations
inheritance. To allow LLDs to easily re-use their own ops tables
overriding only specific methods, this patch implements poor man's
class inheritance. An ops table has ->inherits field which can be set
to any ops table as long as it doesn't create a loop. When the host
is started, the inheritance chain is followed and any operation which
isn't specified is taken from the nearest ancestor which has it
specified. This operation is called finalization and done only once
per an ops table and the LLD doesn't have to do anything special about
it other than making the ops table non-const such that libata can
update it.
libata provides four base ops tables lower drivers can inherit from -
base, sata, pmp, sff and bmdma. To avoid overriding these ops
accidentaly, these ops are declared const and LLDs should always
inherit these instead of using them directly.
After finalization, all the ops table are identical before and after
the patch except for setting .irq_handler to ata_interrupt in drivers
which didn't use to. The .irq_handler doesn't have any actual effect
and the field will soon be removed by later patch.
* sata_sx4 is still using old style EH and currently doesn't take
advantage of ops inheritance.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:49 +07:00
|
|
|
.mode_filter = hpt370_filter,
|
|
|
|
.set_piomode = hpt370_set_piomode,
|
|
|
|
.set_dmamode = hpt370_set_dmamode,
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
.prereset = hpt37x_pre_reset,
|
2006-08-31 11:03:49 +07:00
|
|
|
};
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Configuration for HPT370A. Close to 370 but less filters
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static struct ata_port_operations hpt370a_port_ops = {
|
libata: implement and use ops inheritance
libata lets low level drivers build ata_port_operations table and
register it with libata core layer. This allows low level drivers
high level of flexibility but also burdens them with lots of
boilerplate entries.
This becomes worse for drivers which support related similar
controllers which differ slightly. They share most of the operations
except for a few. However, the driver still needs to list all
operations for each variant. This results in large number of
duplicate entries, which is not only inefficient but also error-prone
as it becomes very difficult to tell what the actual differences are.
This duplicate boilerplates all over the low level drivers also make
updating the core layer exteremely difficult and error-prone. When
compounded with multi-branched development model, it ends up
accumulating inconsistencies over time. Some of those inconsistencies
cause immediate problems and fixed. Others just remain there dormant
making maintenance increasingly difficult.
To rectify the problem, this patch implements ata_port_operations
inheritance. To allow LLDs to easily re-use their own ops tables
overriding only specific methods, this patch implements poor man's
class inheritance. An ops table has ->inherits field which can be set
to any ops table as long as it doesn't create a loop. When the host
is started, the inheritance chain is followed and any operation which
isn't specified is taken from the nearest ancestor which has it
specified. This operation is called finalization and done only once
per an ops table and the LLD doesn't have to do anything special about
it other than making the ops table non-const such that libata can
update it.
libata provides four base ops tables lower drivers can inherit from -
base, sata, pmp, sff and bmdma. To avoid overriding these ops
accidentaly, these ops are declared const and LLDs should always
inherit these instead of using them directly.
After finalization, all the ops table are identical before and after
the patch except for setting .irq_handler to ata_interrupt in drivers
which didn't use to. The .irq_handler doesn't have any actual effect
and the field will soon be removed by later patch.
* sata_sx4 is still using old style EH and currently doesn't take
advantage of ops inheritance.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:49 +07:00
|
|
|
.inherits = &hpt370_port_ops,
|
2006-08-30 05:12:40 +07:00
|
|
|
.mode_filter = hpt370a_filter,
|
2006-08-31 11:03:49 +07:00
|
|
|
};
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Configuration for HPT372, HPT371, HPT302. Slightly different PIO
|
|
|
|
* and DMA mode setting functionality.
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static struct ata_port_operations hpt372_port_ops = {
|
libata: implement and use ops inheritance
libata lets low level drivers build ata_port_operations table and
register it with libata core layer. This allows low level drivers
high level of flexibility but also burdens them with lots of
boilerplate entries.
This becomes worse for drivers which support related similar
controllers which differ slightly. They share most of the operations
except for a few. However, the driver still needs to list all
operations for each variant. This results in large number of
duplicate entries, which is not only inefficient but also error-prone
as it becomes very difficult to tell what the actual differences are.
This duplicate boilerplates all over the low level drivers also make
updating the core layer exteremely difficult and error-prone. When
compounded with multi-branched development model, it ends up
accumulating inconsistencies over time. Some of those inconsistencies
cause immediate problems and fixed. Others just remain there dormant
making maintenance increasingly difficult.
To rectify the problem, this patch implements ata_port_operations
inheritance. To allow LLDs to easily re-use their own ops tables
overriding only specific methods, this patch implements poor man's
class inheritance. An ops table has ->inherits field which can be set
to any ops table as long as it doesn't create a loop. When the host
is started, the inheritance chain is followed and any operation which
isn't specified is taken from the nearest ancestor which has it
specified. This operation is called finalization and done only once
per an ops table and the LLD doesn't have to do anything special about
it other than making the ops table non-const such that libata can
update it.
libata provides four base ops tables lower drivers can inherit from -
base, sata, pmp, sff and bmdma. To avoid overriding these ops
accidentaly, these ops are declared const and LLDs should always
inherit these instead of using them directly.
After finalization, all the ops table are identical before and after
the patch except for setting .irq_handler to ata_interrupt in drivers
which didn't use to. The .irq_handler doesn't have any actual effect
and the field will soon be removed by later patch.
* sata_sx4 is still using old style EH and currently doesn't take
advantage of ops inheritance.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:49 +07:00
|
|
|
.inherits = &ata_bmdma_port_ops,
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
.bmdma_stop = hpt37x_bmdma_stop,
|
|
|
|
|
libata: implement and use ops inheritance
libata lets low level drivers build ata_port_operations table and
register it with libata core layer. This allows low level drivers
high level of flexibility but also burdens them with lots of
boilerplate entries.
This becomes worse for drivers which support related similar
controllers which differ slightly. They share most of the operations
except for a few. However, the driver still needs to list all
operations for each variant. This results in large number of
duplicate entries, which is not only inefficient but also error-prone
as it becomes very difficult to tell what the actual differences are.
This duplicate boilerplates all over the low level drivers also make
updating the core layer exteremely difficult and error-prone. When
compounded with multi-branched development model, it ends up
accumulating inconsistencies over time. Some of those inconsistencies
cause immediate problems and fixed. Others just remain there dormant
making maintenance increasingly difficult.
To rectify the problem, this patch implements ata_port_operations
inheritance. To allow LLDs to easily re-use their own ops tables
overriding only specific methods, this patch implements poor man's
class inheritance. An ops table has ->inherits field which can be set
to any ops table as long as it doesn't create a loop. When the host
is started, the inheritance chain is followed and any operation which
isn't specified is taken from the nearest ancestor which has it
specified. This operation is called finalization and done only once
per an ops table and the LLD doesn't have to do anything special about
it other than making the ops table non-const such that libata can
update it.
libata provides four base ops tables lower drivers can inherit from -
base, sata, pmp, sff and bmdma. To avoid overriding these ops
accidentaly, these ops are declared const and LLDs should always
inherit these instead of using them directly.
After finalization, all the ops table are identical before and after
the patch except for setting .irq_handler to ata_interrupt in drivers
which didn't use to. The .irq_handler doesn't have any actual effect
and the field will soon be removed by later patch.
* sata_sx4 is still using old style EH and currently doesn't take
advantage of ops inheritance.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:49 +07:00
|
|
|
.set_piomode = hpt372_set_piomode,
|
|
|
|
.set_dmamode = hpt372_set_dmamode,
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
.prereset = hpt37x_pre_reset,
|
2006-08-31 11:03:49 +07:00
|
|
|
};
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Configuration for HPT374. Mode setting works like 372 and friends
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
* but we have a different cable detection procedure for function 1.
|
2006-08-30 05:12:40 +07:00
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
static struct ata_port_operations hpt374_fn1_port_ops = {
|
libata: implement and use ops inheritance
libata lets low level drivers build ata_port_operations table and
register it with libata core layer. This allows low level drivers
high level of flexibility but also burdens them with lots of
boilerplate entries.
This becomes worse for drivers which support related similar
controllers which differ slightly. They share most of the operations
except for a few. However, the driver still needs to list all
operations for each variant. This results in large number of
duplicate entries, which is not only inefficient but also error-prone
as it becomes very difficult to tell what the actual differences are.
This duplicate boilerplates all over the low level drivers also make
updating the core layer exteremely difficult and error-prone. When
compounded with multi-branched development model, it ends up
accumulating inconsistencies over time. Some of those inconsistencies
cause immediate problems and fixed. Others just remain there dormant
making maintenance increasingly difficult.
To rectify the problem, this patch implements ata_port_operations
inheritance. To allow LLDs to easily re-use their own ops tables
overriding only specific methods, this patch implements poor man's
class inheritance. An ops table has ->inherits field which can be set
to any ops table as long as it doesn't create a loop. When the host
is started, the inheritance chain is followed and any operation which
isn't specified is taken from the nearest ancestor which has it
specified. This operation is called finalization and done only once
per an ops table and the LLD doesn't have to do anything special about
it other than making the ops table non-const such that libata can
update it.
libata provides four base ops tables lower drivers can inherit from -
base, sata, pmp, sff and bmdma. To avoid overriding these ops
accidentaly, these ops are declared const and LLDs should always
inherit these instead of using them directly.
After finalization, all the ops table are identical before and after
the patch except for setting .irq_handler to ata_interrupt in drivers
which didn't use to. The .irq_handler doesn't have any actual effect
and the field will soon be removed by later patch.
* sata_sx4 is still using old style EH and currently doesn't take
advantage of ops inheritance.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:49 +07:00
|
|
|
.inherits = &hpt372_port_ops,
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
.prereset = hpt374_fn1_pre_reset,
|
2006-08-31 11:03:49 +07:00
|
|
|
};
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
/**
|
|
|
|
* htp37x_clock_slot - Turn timing to PC clock entry
|
|
|
|
* @freq: Reported frequency timing
|
|
|
|
* @base: Base timing
|
|
|
|
*
|
|
|
|
* Turn the timing data intoa clock slot (0 for 33, 1 for 40, 2 for 50
|
|
|
|
* and 3 for 66Mhz)
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static int hpt37x_clock_slot(unsigned int freq, unsigned int base)
|
|
|
|
{
|
|
|
|
unsigned int f = (base * freq) / 192; /* Mhz */
|
|
|
|
if (f < 40)
|
|
|
|
return 0; /* 33Mhz slot */
|
|
|
|
if (f < 45)
|
|
|
|
return 1; /* 40Mhz slot */
|
|
|
|
if (f < 55)
|
|
|
|
return 2; /* 50Mhz slot */
|
|
|
|
return 3; /* 60Mhz slot */
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hpt37x_calibrate_dpll - Calibrate the DPLL loop
|
2006-08-31 11:03:49 +07:00
|
|
|
* @dev: PCI device
|
2006-08-30 05:12:40 +07:00
|
|
|
*
|
|
|
|
* Perform a calibration cycle on the HPT37x DPLL. Returns 1 if this
|
|
|
|
* succeeds
|
|
|
|
*/
|
|
|
|
|
|
|
|
static int hpt37x_calibrate_dpll(struct pci_dev *dev)
|
|
|
|
{
|
|
|
|
u8 reg5b;
|
|
|
|
u32 reg5c;
|
|
|
|
int tries;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
for(tries = 0; tries < 0x5000; tries++) {
|
|
|
|
udelay(50);
|
|
|
|
pci_read_config_byte(dev, 0x5b, ®5b);
|
|
|
|
if (reg5b & 0x80) {
|
|
|
|
/* See if it stays set */
|
|
|
|
for(tries = 0; tries < 0x1000; tries ++) {
|
|
|
|
pci_read_config_byte(dev, 0x5b, ®5b);
|
|
|
|
/* Failed ? */
|
|
|
|
if ((reg5b & 0x80) == 0)
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
/* Turn off tuning, we have the DPLL set */
|
|
|
|
pci_read_config_dword(dev, 0x5c, ®5c);
|
|
|
|
pci_write_config_dword(dev, 0x5c, reg5c & ~ 0x100);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* Never went stable */
|
|
|
|
return 0;
|
|
|
|
}
|
2007-11-06 05:53:38 +07:00
|
|
|
|
|
|
|
static u32 hpt374_read_freq(struct pci_dev *pdev)
|
|
|
|
{
|
|
|
|
u32 freq;
|
|
|
|
unsigned long io_base = pci_resource_start(pdev, 4);
|
|
|
|
if (PCI_FUNC(pdev->devfn) & 1) {
|
2007-12-14 07:01:38 +07:00
|
|
|
struct pci_dev *pdev_0;
|
|
|
|
|
|
|
|
pdev_0 = pci_get_slot(pdev->bus, pdev->devfn - 1);
|
2007-11-06 05:53:38 +07:00
|
|
|
/* Someone hot plugged the controller on us ? */
|
|
|
|
if (pdev_0 == NULL)
|
|
|
|
return 0;
|
|
|
|
io_base = pci_resource_start(pdev_0, 4);
|
|
|
|
freq = inl(io_base + 0x90);
|
|
|
|
pci_dev_put(pdev_0);
|
2007-12-14 07:01:38 +07:00
|
|
|
} else
|
2007-11-06 05:53:38 +07:00
|
|
|
freq = inl(io_base + 0x90);
|
|
|
|
return freq;
|
|
|
|
}
|
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/**
|
|
|
|
* hpt37x_init_one - Initialise an HPT37X/302
|
|
|
|
* @dev: PCI device
|
|
|
|
* @id: Entry in match table
|
|
|
|
*
|
|
|
|
* Initialise an HPT37x device. There are some interesting complications
|
|
|
|
* here. Firstly the chip may report 366 and be one of several variants.
|
|
|
|
* Secondly all the timings depend on the clock for the chip which we must
|
|
|
|
* detect and look up
|
|
|
|
*
|
|
|
|
* This is the known chip mappings. It may be missing a couple of later
|
|
|
|
* releases.
|
|
|
|
*
|
|
|
|
* Chip version PCI Rev Notes
|
|
|
|
* HPT366 4 (HPT366) 0 Other driver
|
|
|
|
* HPT366 4 (HPT366) 1 Other driver
|
|
|
|
* HPT368 4 (HPT366) 2 Other driver
|
|
|
|
* HPT370 4 (HPT366) 3 UDMA100
|
|
|
|
* HPT370A 4 (HPT366) 4 UDMA100
|
|
|
|
* HPT372 4 (HPT366) 5 UDMA133 (1)
|
|
|
|
* HPT372N 4 (HPT366) 6 Other driver
|
|
|
|
* HPT372A 5 (HPT372) 1 UDMA133 (1)
|
|
|
|
* HPT372N 5 (HPT372) 2 Other driver
|
|
|
|
* HPT302 6 (HPT302) 1 UDMA133
|
|
|
|
* HPT302N 6 (HPT302) 2 Other driver
|
|
|
|
* HPT371 7 (HPT371) * UDMA133
|
|
|
|
* HPT374 8 (HPT374) * UDMA133 4 channel
|
|
|
|
* HPT372N 9 (HPT372N) * Other driver
|
|
|
|
*
|
|
|
|
* (1) UDMA133 support depends on the bus clock
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
static int hpt37x_init_one(struct pci_dev *dev, const struct pci_device_id *id)
|
|
|
|
{
|
|
|
|
/* HPT370 - UDMA100 */
|
2007-05-04 17:43:58 +07:00
|
|
|
static const struct ata_port_info info_hpt370 = {
|
2007-05-28 17:59:48 +07:00
|
|
|
.flags = ATA_FLAG_SLAVE_POSS,
|
2009-03-15 03:38:24 +07:00
|
|
|
.pio_mask = ATA_PIO4,
|
|
|
|
.mwdma_mask = ATA_MWDMA2,
|
2007-07-09 23:16:50 +07:00
|
|
|
.udma_mask = ATA_UDMA5,
|
2006-08-30 05:12:40 +07:00
|
|
|
.port_ops = &hpt370_port_ops
|
|
|
|
};
|
|
|
|
/* HPT370A - UDMA100 */
|
2007-05-04 17:43:58 +07:00
|
|
|
static const struct ata_port_info info_hpt370a = {
|
2007-05-28 17:59:48 +07:00
|
|
|
.flags = ATA_FLAG_SLAVE_POSS,
|
2009-03-15 03:38:24 +07:00
|
|
|
.pio_mask = ATA_PIO4,
|
|
|
|
.mwdma_mask = ATA_MWDMA2,
|
2007-07-09 23:16:50 +07:00
|
|
|
.udma_mask = ATA_UDMA5,
|
2006-08-30 05:12:40 +07:00
|
|
|
.port_ops = &hpt370a_port_ops
|
|
|
|
};
|
2007-03-09 06:28:52 +07:00
|
|
|
/* HPT370 - UDMA100 */
|
2007-05-04 17:43:58 +07:00
|
|
|
static const struct ata_port_info info_hpt370_33 = {
|
2007-05-28 17:59:48 +07:00
|
|
|
.flags = ATA_FLAG_SLAVE_POSS,
|
2009-03-15 03:38:24 +07:00
|
|
|
.pio_mask = ATA_PIO4,
|
|
|
|
.mwdma_mask = ATA_MWDMA2,
|
2007-11-06 05:53:38 +07:00
|
|
|
.udma_mask = ATA_UDMA5,
|
2007-03-09 06:28:52 +07:00
|
|
|
.port_ops = &hpt370_port_ops
|
|
|
|
};
|
|
|
|
/* HPT370A - UDMA100 */
|
2007-05-04 17:43:58 +07:00
|
|
|
static const struct ata_port_info info_hpt370a_33 = {
|
2007-05-28 17:59:48 +07:00
|
|
|
.flags = ATA_FLAG_SLAVE_POSS,
|
2009-03-15 03:38:24 +07:00
|
|
|
.pio_mask = ATA_PIO4,
|
|
|
|
.mwdma_mask = ATA_MWDMA2,
|
2007-11-06 05:53:38 +07:00
|
|
|
.udma_mask = ATA_UDMA5,
|
2007-03-09 06:28:52 +07:00
|
|
|
.port_ops = &hpt370a_port_ops
|
|
|
|
};
|
2006-08-30 05:12:40 +07:00
|
|
|
/* HPT371, 372 and friends - UDMA133 */
|
2007-05-04 17:43:58 +07:00
|
|
|
static const struct ata_port_info info_hpt372 = {
|
2007-05-28 17:59:48 +07:00
|
|
|
.flags = ATA_FLAG_SLAVE_POSS,
|
2009-03-15 03:38:24 +07:00
|
|
|
.pio_mask = ATA_PIO4,
|
|
|
|
.mwdma_mask = ATA_MWDMA2,
|
2007-07-09 23:16:50 +07:00
|
|
|
.udma_mask = ATA_UDMA6,
|
2006-08-30 05:12:40 +07:00
|
|
|
.port_ops = &hpt372_port_ops
|
|
|
|
};
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
/* HPT374 - UDMA100, function 1 uses different prereset method */
|
|
|
|
static const struct ata_port_info info_hpt374_fn0 = {
|
|
|
|
.flags = ATA_FLAG_SLAVE_POSS,
|
2009-03-15 03:38:24 +07:00
|
|
|
.pio_mask = ATA_PIO4,
|
|
|
|
.mwdma_mask = ATA_MWDMA2,
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
.udma_mask = ATA_UDMA5,
|
|
|
|
.port_ops = &hpt372_port_ops
|
|
|
|
};
|
|
|
|
static const struct ata_port_info info_hpt374_fn1 = {
|
2007-05-28 17:59:48 +07:00
|
|
|
.flags = ATA_FLAG_SLAVE_POSS,
|
2009-03-15 03:38:24 +07:00
|
|
|
.pio_mask = ATA_PIO4,
|
|
|
|
.mwdma_mask = ATA_MWDMA2,
|
2007-07-09 23:16:50 +07:00
|
|
|
.udma_mask = ATA_UDMA5,
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
.port_ops = &hpt374_fn1_port_ops
|
2006-08-30 05:12:40 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
static const int MHz[4] = { 33, 40, 50, 66 };
|
2007-05-04 17:43:58 +07:00
|
|
|
void *private_data = NULL;
|
2008-03-25 10:22:49 +07:00
|
|
|
const struct ata_port_info *ppi[] = { NULL, NULL };
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
u8 irqmask;
|
|
|
|
u32 class_rev;
|
2007-03-09 06:28:52 +07:00
|
|
|
u8 mcr1;
|
2006-08-30 05:12:40 +07:00
|
|
|
u32 freq;
|
2007-03-09 06:28:52 +07:00
|
|
|
int prefer_dpll = 1;
|
2007-05-22 07:14:23 +07:00
|
|
|
|
2007-03-09 06:28:52 +07:00
|
|
|
unsigned long iobase = pci_resource_start(dev, 4);
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
const struct hpt_chip *chip_table;
|
|
|
|
int clock_slot;
|
2008-03-25 10:22:47 +07:00
|
|
|
int rc;
|
|
|
|
|
|
|
|
rc = pcim_enable_device(dev);
|
|
|
|
if (rc)
|
|
|
|
return rc;
|
2006-08-30 05:12:40 +07:00
|
|
|
|
|
|
|
pci_read_config_dword(dev, PCI_CLASS_REVISION, &class_rev);
|
|
|
|
class_rev &= 0xFF;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
if (dev->device == PCI_DEVICE_ID_TTI_HPT366) {
|
|
|
|
/* May be a later chip in disguise. Check */
|
|
|
|
/* Older chips are in the HPT366 driver. Ignore them */
|
|
|
|
if (class_rev < 3)
|
|
|
|
return -ENODEV;
|
|
|
|
/* N series chips have their own driver. Ignore */
|
|
|
|
if (class_rev == 6)
|
|
|
|
return -ENODEV;
|
|
|
|
|
2006-08-31 11:03:49 +07:00
|
|
|
switch(class_rev) {
|
2006-08-30 05:12:40 +07:00
|
|
|
case 3:
|
2008-03-25 10:22:49 +07:00
|
|
|
ppi[0] = &info_hpt370;
|
2006-08-30 05:12:40 +07:00
|
|
|
chip_table = &hpt370;
|
2007-03-09 06:28:52 +07:00
|
|
|
prefer_dpll = 0;
|
2006-08-30 05:12:40 +07:00
|
|
|
break;
|
|
|
|
case 4:
|
2008-03-25 10:22:49 +07:00
|
|
|
ppi[0] = &info_hpt370a;
|
2006-08-30 05:12:40 +07:00
|
|
|
chip_table = &hpt370a;
|
2007-03-09 06:28:52 +07:00
|
|
|
prefer_dpll = 0;
|
2006-08-30 05:12:40 +07:00
|
|
|
break;
|
|
|
|
case 5:
|
2008-03-25 10:22:49 +07:00
|
|
|
ppi[0] = &info_hpt372;
|
2006-08-30 05:12:40 +07:00
|
|
|
chip_table = &hpt372;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
printk(KERN_ERR "pata_hpt37x: Unknown HPT366 subtype please report (%d).\n", class_rev);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
switch(dev->device) {
|
|
|
|
case PCI_DEVICE_ID_TTI_HPT372:
|
|
|
|
/* 372N if rev >= 2*/
|
|
|
|
if (class_rev >= 2)
|
|
|
|
return -ENODEV;
|
2008-03-25 10:22:49 +07:00
|
|
|
ppi[0] = &info_hpt372;
|
2006-08-30 05:12:40 +07:00
|
|
|
chip_table = &hpt372a;
|
|
|
|
break;
|
|
|
|
case PCI_DEVICE_ID_TTI_HPT302:
|
|
|
|
/* 302N if rev > 1 */
|
|
|
|
if (class_rev > 1)
|
|
|
|
return -ENODEV;
|
2008-03-25 10:22:49 +07:00
|
|
|
ppi[0] = &info_hpt372;
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Check this */
|
|
|
|
chip_table = &hpt302;
|
|
|
|
break;
|
|
|
|
case PCI_DEVICE_ID_TTI_HPT371:
|
2007-03-09 06:28:52 +07:00
|
|
|
if (class_rev > 1)
|
|
|
|
return -ENODEV;
|
2008-03-25 10:22:49 +07:00
|
|
|
ppi[0] = &info_hpt372;
|
2006-08-30 05:12:40 +07:00
|
|
|
chip_table = &hpt371;
|
2007-04-26 14:19:25 +07:00
|
|
|
/* Single channel device, master is not present
|
|
|
|
but the BIOS (or us for non x86) must mark it
|
2007-03-09 06:28:52 +07:00
|
|
|
absent */
|
|
|
|
pci_read_config_byte(dev, 0x50, &mcr1);
|
|
|
|
mcr1 &= ~0x04;
|
|
|
|
pci_write_config_byte(dev, 0x50, mcr1);
|
2006-08-30 05:12:40 +07:00
|
|
|
break;
|
|
|
|
case PCI_DEVICE_ID_TTI_HPT374:
|
|
|
|
chip_table = &hpt374;
|
libata: make reset related methods proper port operations
Currently reset methods are not specified directly in the
ata_port_operations table. If a LLD wants to use custom reset
methods, it should construct and use a error_handler which uses those
reset methods. It's done this way for two reasons.
First, the ops table already contained too many methods and adding
four more of them would noticeably increase the amount of necessary
boilerplate code all over low level drivers.
Second, as ->error_handler uses those reset methods, it can get
confusing. ie. By overriding ->error_handler, those reset ops can be
made useless making layering a bit hazy.
Now that ops table uses inheritance, the first problem doesn't exist
anymore. The second isn't completely solved but is relieved by
providing default values - most drivers can just override what it has
implemented and don't have to concern itself about higher level
callbacks. In fact, there currently is no driver which actually
modifies error handling behavior. Drivers which override
->error_handler just wraps the standard error handler only to prepare
the controller for EH. I don't think making ops layering strict has
any noticeable benefit.
This patch makes ->prereset, ->softreset, ->hardreset, ->postreset and
their PMP counterparts propoer ops. Default ops are provided in the
base ops tables and drivers are converted to override individual reset
methods instead of creating custom error_handler.
* ata_std_error_handler() doesn't use sata_std_hardreset() if SCRs
aren't accessible. sata_promise doesn't need to use separate
error_handlers for PATA and SATA anymore.
* softreset is broken for sata_inic162x and sata_sx4. As libata now
always prefers hardreset, this doesn't really matter but the ops are
forced to NULL using ATA_OP_NULL for documentation purpose.
* pata_hpt374 needs to use different prereset for the first and second
PCI functions. This used to be done by branching from
hpt374_error_handler(). The proper way to do this is to use
separate ops and port_info tables for each function. Converted.
Signed-off-by: Tejun Heo <htejun@gmail.com>
2008-03-25 10:22:50 +07:00
|
|
|
if (!(PCI_FUNC(dev->devfn) & 1))
|
|
|
|
*ppi = &info_hpt374_fn0;
|
|
|
|
else
|
|
|
|
*ppi = &info_hpt374_fn1;
|
2006-08-30 05:12:40 +07:00
|
|
|
break;
|
|
|
|
default:
|
|
|
|
printk(KERN_ERR "pata_hpt37x: PCI table is bogus please report (%d).\n", dev->device);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/* Ok so this is a chip we support */
|
|
|
|
|
|
|
|
pci_write_config_byte(dev, PCI_CACHE_LINE_SIZE, (L1_CACHE_BYTES / 4));
|
|
|
|
pci_write_config_byte(dev, PCI_LATENCY_TIMER, 0x78);
|
|
|
|
pci_write_config_byte(dev, PCI_MIN_GNT, 0x08);
|
|
|
|
pci_write_config_byte(dev, PCI_MAX_LAT, 0x08);
|
|
|
|
|
|
|
|
pci_read_config_byte(dev, 0x5A, &irqmask);
|
|
|
|
irqmask &= ~0x10;
|
|
|
|
pci_write_config_byte(dev, 0x5a, irqmask);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* default to pci clock. make sure MA15/16 are set to output
|
|
|
|
* to prevent drives having problems with 40-pin cables. Needed
|
|
|
|
* for some drives such as IBM-DTLA which will not enter ready
|
|
|
|
* state on reset when PDIAG is a input.
|
|
|
|
*/
|
|
|
|
|
2006-08-31 11:03:49 +07:00
|
|
|
pci_write_config_byte(dev, 0x5b, 0x23);
|
2007-05-22 07:14:23 +07:00
|
|
|
|
2007-03-09 06:28:52 +07:00
|
|
|
/*
|
|
|
|
* HighPoint does this for HPT372A.
|
|
|
|
* NOTE: This register is only writeable via I/O space.
|
|
|
|
*/
|
|
|
|
if (chip_table == &hpt372a)
|
|
|
|
outb(0x0e, iobase + 0x9c);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2007-03-09 06:28:52 +07:00
|
|
|
/* Some devices do not let this value be accessed via PCI space
|
2007-11-06 05:53:38 +07:00
|
|
|
according to the old driver. In addition we must use the value
|
|
|
|
from FN 0 on the HPT374 */
|
|
|
|
|
|
|
|
if (chip_table == &hpt374) {
|
|
|
|
freq = hpt374_read_freq(dev);
|
|
|
|
if (freq == 0)
|
|
|
|
return -ENODEV;
|
|
|
|
} else
|
|
|
|
freq = inl(iobase + 0x90);
|
2007-03-09 06:28:52 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
if ((freq >> 12) != 0xABCDE) {
|
|
|
|
int i;
|
|
|
|
u8 sr;
|
|
|
|
u32 total = 0;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
printk(KERN_WARNING "pata_hpt37x: BIOS has not set timing clocks.\n");
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/* This is the process the HPT371 BIOS is reported to use */
|
|
|
|
for(i = 0; i < 128; i++) {
|
|
|
|
pci_read_config_byte(dev, 0x78, &sr);
|
2007-03-09 06:28:52 +07:00
|
|
|
total += sr & 0x1FF;
|
2006-08-30 05:12:40 +07:00
|
|
|
udelay(15);
|
|
|
|
}
|
|
|
|
freq = total / 128;
|
|
|
|
}
|
|
|
|
freq &= 0x1FF;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/*
|
|
|
|
* Turn the frequency check into a band and then find a timing
|
|
|
|
* table to match it.
|
|
|
|
*/
|
2007-05-22 07:14:23 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
clock_slot = hpt37x_clock_slot(freq, chip_table->base);
|
2007-03-09 06:28:52 +07:00
|
|
|
if (chip_table->clocks[clock_slot] == NULL || prefer_dpll) {
|
2006-08-30 05:12:40 +07:00
|
|
|
/*
|
|
|
|
* We need to try PLL mode instead
|
2007-03-09 06:28:52 +07:00
|
|
|
*
|
|
|
|
* For non UDMA133 capable devices we should
|
|
|
|
* use a 50MHz DPLL by choice
|
2006-08-30 05:12:40 +07:00
|
|
|
*/
|
2007-03-09 06:28:52 +07:00
|
|
|
unsigned int f_low, f_high;
|
2007-05-26 02:48:55 +07:00
|
|
|
int dpll, adjust;
|
2007-05-22 07:14:23 +07:00
|
|
|
|
2007-05-26 02:48:55 +07:00
|
|
|
/* Compute DPLL */
|
2008-03-25 10:22:49 +07:00
|
|
|
dpll = (ppi[0]->udma_mask & 0xC0) ? 3 : 2;
|
2007-05-22 07:14:23 +07:00
|
|
|
|
2007-05-26 02:48:55 +07:00
|
|
|
f_low = (MHz[clock_slot] * 48) / MHz[dpll];
|
2007-03-09 06:28:52 +07:00
|
|
|
f_high = f_low + 2;
|
2007-05-26 02:48:55 +07:00
|
|
|
if (clock_slot > 1)
|
|
|
|
f_high += 2;
|
2007-03-09 06:28:52 +07:00
|
|
|
|
|
|
|
/* Select the DPLL clock. */
|
|
|
|
pci_write_config_byte(dev, 0x5b, 0x21);
|
2007-07-24 21:17:48 +07:00
|
|
|
pci_write_config_dword(dev, 0x5C, (f_high << 16) | f_low | 0x100);
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
for(adjust = 0; adjust < 8; adjust++) {
|
|
|
|
if (hpt37x_calibrate_dpll(dev))
|
|
|
|
break;
|
|
|
|
/* See if it'll settle at a fractionally different clock */
|
2007-07-24 21:17:48 +07:00
|
|
|
if (adjust & 1)
|
|
|
|
f_low -= adjust >> 1;
|
|
|
|
else
|
|
|
|
f_high += adjust >> 1;
|
|
|
|
pci_write_config_dword(dev, 0x5C, (f_high << 16) | f_low | 0x100);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
if (adjust == 8) {
|
2007-08-11 00:02:15 +07:00
|
|
|
printk(KERN_ERR "pata_hpt37x: DPLL did not stabilize!\n");
|
2006-08-30 05:12:40 +07:00
|
|
|
return -ENODEV;
|
|
|
|
}
|
2007-05-26 02:48:55 +07:00
|
|
|
if (dpll == 3)
|
2007-05-04 17:43:58 +07:00
|
|
|
private_data = (void *)hpt37x_timings_66;
|
2007-03-09 06:28:52 +07:00
|
|
|
else
|
2007-05-04 17:43:58 +07:00
|
|
|
private_data = (void *)hpt37x_timings_50;
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2007-08-11 00:02:15 +07:00
|
|
|
printk(KERN_INFO "pata_hpt37x: bus clock %dMHz, using %dMHz DPLL.\n",
|
|
|
|
MHz[clock_slot], MHz[dpll]);
|
2006-08-30 05:12:40 +07:00
|
|
|
} else {
|
2007-05-04 17:43:58 +07:00
|
|
|
private_data = (void *)chip_table->clocks[clock_slot];
|
2006-08-30 05:12:40 +07:00
|
|
|
/*
|
2007-04-26 14:19:25 +07:00
|
|
|
* Perform a final fixup. Note that we will have used the
|
|
|
|
* DPLL on the HPT372 which means we don't have to worry
|
|
|
|
* about lack of UDMA133 support on lower clocks
|
|
|
|
*/
|
2006-08-31 11:03:49 +07:00
|
|
|
|
2008-03-25 10:22:49 +07:00
|
|
|
if (clock_slot < 2 && ppi[0] == &info_hpt370)
|
|
|
|
ppi[0] = &info_hpt370_33;
|
|
|
|
if (clock_slot < 2 && ppi[0] == &info_hpt370a)
|
|
|
|
ppi[0] = &info_hpt370a_33;
|
2007-08-11 00:02:15 +07:00
|
|
|
printk(KERN_INFO "pata_hpt37x: %s using %dMHz bus clock.\n",
|
|
|
|
chip_table->name, MHz[clock_slot]);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
2007-03-09 06:28:52 +07:00
|
|
|
|
2006-08-30 05:12:40 +07:00
|
|
|
/* Now kick off ATA set up */
|
2008-04-07 20:47:16 +07:00
|
|
|
return ata_pci_sff_init_one(dev, ppi, &hpt37x_sht, private_data);
|
2006-08-30 05:12:40 +07:00
|
|
|
}
|
|
|
|
|
2006-09-29 07:21:59 +07:00
|
|
|
static const struct pci_device_id hpt37x[] = {
|
|
|
|
{ PCI_VDEVICE(TTI, PCI_DEVICE_ID_TTI_HPT366), },
|
|
|
|
{ PCI_VDEVICE(TTI, PCI_DEVICE_ID_TTI_HPT371), },
|
|
|
|
{ PCI_VDEVICE(TTI, PCI_DEVICE_ID_TTI_HPT372), },
|
|
|
|
{ PCI_VDEVICE(TTI, PCI_DEVICE_ID_TTI_HPT374), },
|
|
|
|
{ PCI_VDEVICE(TTI, PCI_DEVICE_ID_TTI_HPT302), },
|
|
|
|
|
|
|
|
{ },
|
2006-08-30 05:12:40 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
static struct pci_driver hpt37x_pci_driver = {
|
2006-09-29 07:21:59 +07:00
|
|
|
.name = DRV_NAME,
|
2006-08-30 05:12:40 +07:00
|
|
|
.id_table = hpt37x,
|
|
|
|
.probe = hpt37x_init_one,
|
|
|
|
.remove = ata_pci_remove_one
|
|
|
|
};
|
|
|
|
|
|
|
|
static int __init hpt37x_init(void)
|
|
|
|
{
|
|
|
|
return pci_register_driver(&hpt37x_pci_driver);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void __exit hpt37x_exit(void)
|
|
|
|
{
|
|
|
|
pci_unregister_driver(&hpt37x_pci_driver);
|
|
|
|
}
|
|
|
|
|
|
|
|
MODULE_AUTHOR("Alan Cox");
|
|
|
|
MODULE_DESCRIPTION("low-level driver for the Highpoint HPT37x/30x");
|
|
|
|
MODULE_LICENSE("GPL");
|
|
|
|
MODULE_DEVICE_TABLE(pci, hpt37x);
|
|
|
|
MODULE_VERSION(DRV_VERSION);
|
|
|
|
|
|
|
|
module_init(hpt37x_init);
|
|
|
|
module_exit(hpt37x_exit);
|