linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pata_cmd640: CMD640 PCI support
Date: Fri, 02 Mar 2007 18:26:05 -0500	[thread overview]
Message-ID: <45E8B28D.7030500@garzik.org> (raw)
In-Reply-To: <20070302150306.368e24b9@lxorguk.ukuu.org.uk>

Alan Cox wrote:
> Support for the PCI CMD640 (not VLB)
> 
> Signed-off-by: Alan Cox <alan@redhat.com>

Overall ACK, with minor comments/questions below

Not applying (yet) due to cable_detect dependency.  will await resend 
once dependency is satisfied.


> +static void cmd640_set_piomode(struct ata_port *ap, struct ata_device *adev)
> +{
> +	struct cmd640_reg *timing = ap->private_data;
> +	struct pci_dev *pdev = to_pci_dev(ap->host->dev);
> +	struct ata_timing t;
> +	const unsigned long T = 1000000 / 33;
> +	const u8 setup_data[] = { 0x40, 0x40, 0x40, 0x80, 0x00 };
> +	u8 reg;
> +	int arttim = ARTIM0 + 2 * adev->devno;
> +	struct ata_device *pair = ata_dev_pair(adev);
> +
> +	if (ata_timing_compute(adev, adev->pio_mode, &t, T, 0) < 0) {
> +		printk(KERN_ERR DRV_NAME ": mode computation failed.\n");

ata_dev_printk or dev_printk


> +	/* The second channel has shared timings and the setup timing is
> +	   messy to switch to merge it for worst case */
> +	if (ap->port_no && pair) {
> +		struct ata_timing p;
> +		ata_timing_compute(pair, pair->pio_mode, &p, T, 1);
> +		ata_timing_merge(&p, &t, &t, ATA_TIMING_SETUP);
> +	}
> +
> +	/* Make the timings fit */
> +	if (t.recover > 16) {
> +		t.active += t.recover - 16;
> +		t.recover = 16;
> +	}
> +	if (t.active > 16)
> +		t.active = 16;
> +
> +	/* Now convert the clocks into values we can actually stuff into
> +	   the chip */
> +
> +	if (t.recover > 1)
> +		t.recover--;	/* 640B only */
> +	else
> +		t.recover = 15;
> +
> +	if (t.setup > 4)
> +		t.setup = 0xC0;
> +	else
> +		t.setup = setup_data[t.setup];
> +
> +	if (ap->port_no == 0) {
> +		t.active &= 0x0F;	/* 0 = 16 */
> +
> +		/* Load setup timing */
> +		pci_read_config_byte(pdev, arttim, &reg);
> +		reg &= 0x3F;
> +		reg |= t.setup;
> +		pci_write_config_byte(pdev, arttim, reg);
> +
> +		/* Load active/recovery */
> +		pci_write_config_byte(pdev, arttim + 1, (t.active << 4) | t.recover);
> +	} else {
> +		/* Save the shared timings for channel, they will be loaded
> +		   by qc_issue_prot. Reloading the setup time is expensive 
> +		   so we keep a merged one loaded */
> +		pci_read_config_byte(pdev, ARTIM23, &reg);
> +		reg &= 0x3F;
> +		reg |= t.setup;
> +		pci_write_config_byte(pdev, ARTIM23, reg);
> +		timing->reg58[adev->devno] = (t.active << 4) | t.recover;
> +	}
> +}
> +
> +
> +/**
> + *	cmd640_qc_issue_prot	-	command preparation hook
> + *	@qc: Command to be issued
> + *
> + *	Channel 1 has shared timings. We must reprogram the
> + *	clock each drive 2/3 switch we do.
> + */
> +
> +static unsigned int cmd640_qc_issue_prot(struct ata_queued_cmd *qc)
> +{
> +	struct ata_port *ap = qc->ap;
> +	struct ata_device *adev = qc->dev;
> +	struct pci_dev *pdev = to_pci_dev(ap->host->dev);
> +	struct cmd640_reg *timing = ap->private_data;
> +	
> +	if (ap->port_no != 0 && adev->devno != timing->last) {
> +		pci_write_config_byte(pdev, DRWTIM23, timing->reg58[adev->devno]);
> +		timing->last = adev->devno;
> +	}

It might be worth looking into whether ->dev_select is a better place 
for this sort of code


> +	return ata_qc_issue_prot(qc);
> +}
> +

> +static int cmd640_init_one(struct pci_dev *pdev, const struct pci_device_id *id)
> +{
> +	u8 r;
> +	u8 ctrl;
> +	
> +	static struct ata_port_info info = {
> +		.sht = &cmd640_sht,
> +		.flags = ATA_FLAG_SLAVE_POSS | ATA_FLAG_SRST,
> +		.pio_mask = 0x1f,

I-dont-know-the-hardware question:  does this h/w have no DMA support?


> +	static struct ata_port_info *port_info[2] = { &info, &info };
> +
> +	/* CMD640 detected, commiserations */
> +	pci_write_config_byte(pdev, 0x5C, 0x00);

magic number


> +	/* Get version info */
> +	pci_read_config_byte(pdev, CFR, &r);
> +	/* PIO0 command cycles */
> +	pci_write_config_byte(pdev, CMDTIM, 0);
> +	/* 512 byte bursts (sector) */
> +	pci_write_config_byte(pdev, BRST, 0x40);
> +	/* 
> +	 * A reporter a long time ago
> +	 * Had problems with the data fifo
> +	 * So don't run the risk
> +	 * Of putting crap on the disk
> +	 * For its better just to go slow
> +	 */
> +	/* Do channel 0 */
> +	pci_read_config_byte(pdev, CNTRL, &ctrl);
> +	pci_write_config_byte(pdev, CNTRL, ctrl | 0xC0);
> +	/* Ditto for channel 1 */
> +	pci_read_config_byte(pdev, ARTIM23, &ctrl);
> +	ctrl |= 0x0C;
> +	pci_write_config_byte(pdev, ARTIM23, ctrl);
> +	
> +	return ata_pci_init_one(pdev, port_info, 2);
> +}
> +
> +static int cmd640_reinit_one(struct pci_dev *pdev)
> +{
> +	return ata_pci_device_resume(pdev);
> +}

appears to be useless wrapper



  reply	other threads:[~2007-03-02 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 15:03 [PATCH] pata_cmd640: CMD640 PCI support Alan Cox
2007-03-02 23:26 ` Jeff Garzik [this message]
2007-03-03  0:52   ` Alan Cox
2007-03-03 17:12   ` Sergei Shtylyov
2007-03-03 20:33     ` Alan Cox
2007-03-03 19:38       ` Sergei Shtylyov

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=45E8B28D.7030500@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.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).