linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@it.uu.se>
To: jeff@garzik.org
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.20-rc3] sata_promise: ATAPI support
Date: Mon, 8 Jan 2007 09:55:26 +0100 (MET)	[thread overview]
Message-ID: <200701080855.l088tQ6w001683@harpo.it.uu.se> (raw)

On Sun, 07 Jan 2007 20:50:48 -0500, Jeff Garzik wrote:
> > With this patch ATAPI will work on SATA ports on second-generation
> > chips, and on the first-generation PATA-only 20619. ATAPI on the
> > 2057x' PATA port will work automatically when #promise-sata-pata
> > is updated. ATAPI on the 2037x' PATA port is enabled by a followup
> > patch for the #promise-sata-pata branch.
> > 
> > Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>
> 
> No objections, minor revision requests follow.
> 
> * general comment:  please combine the 'make first gen SATAPI work' 
> patch with this one.

Will do.

> > +static unsigned int pdc_wait_for_drq(struct ata_port *ap)
> > +{ 
> > +	void __iomem *port_mmio = (void __iomem *) ap->ioaddr.cmd_addr;
> > +	unsigned int i;
> > +	unsigned int status;
> > +
> > +	/* Following pdc-ultra's WaitForDrq() we loop here until BSY
> > +	 * is clear and DRQ is set in altstatus. We could possibly call
> > +	 * ata_busy_wait() and loop until DRQ is set, but since we don't
> > +	 * know how much time a call to ata_busy_wait() took, we don't
> > +	 * know when to time out the outer loop.
> > +	 */
> > +	for(i = 0; i < 1000; ++i) {
> > +		status = readb(port_mmio + 0x38); /* altstatus */
> > +		if (status == 0xFF)
> > +			break;
> > +		if (status & ATA_BUSY)
> > +			;
> > +		else if (status & (ATA_DRQ | ATA_ERR))
> > +			break;
> > +		mdelay(1);
> > +	}
> 
> This really hurts to do this with spinlocks held.  Long term, ponder 
> ways to move this to a kernel thread that can sleep [if it takes too long?]

On the TODO list for a later update.

> > +static void pdc_issue_atapi_pkt_cmd(struct ata_queued_cmd *qc)
> > +{
> > +	struct ata_port *ap = qc->ap;
> > +	void __iomem *port_mmio = (void __iomem *) ap->ioaddr.cmd_addr;
> > +	void __iomem *host_mmio = ap->host->mmio_base;
> > +	unsigned int nbytes;
> > +	unsigned int tmp;
> > +
> > +	/* disable INTA here, it will be re-enable when CAM use SEQ 0 for packets */
> 
> cut-n-pasted comment?  This is not CAM :)

Indeed :-) Will fix.

> > +	writeb(0x00, port_mmio + PDC_CTLSTAT); /* that the drive INT pass to SEQ 0*/
> > +	writeb(0x20, host_mmio + 0); /* but mask SEQ 0 INT */
> 
> please create named constants for these magic numbers

Will do (for this and the other places you pointed out).

/Mikael

             reply	other threads:[~2007-01-08  8:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08  8:55 Mikael Pettersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-06 20:29 [PATCH 2.6.20-rc3] sata_promise: ATAPI support Mikael Pettersson
2007-01-08  1:50 ` 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=200701080855.l088tQ6w001683@harpo.it.uu.se \
    --to=mikpe@it.uu.se \
    --cc=jeff@garzik.org \
    --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).