From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: ide <linux-ide@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sata_sil: add Large Block Transfer support
Date: Mon, 22 Dec 2008 19:19:48 +0900 [thread overview]
Message-ID: <494F69C4.2060708@kernel.org> (raw)
In-Reply-To: <4945BDED.7050205@shaw.ca>
Hello,
Robert Hancock wrote:
> Obviously not 2.6.28 material, but could potentially head into .29.
> I've done some testing with a DVD drive connected to this controller
> and verified that reading off an entire DVD returns correct data
> (and that the controller is actually getting requests that cross
> 64K boundaries). More testing would certainly be useful..
Ah... nice. It would be great to have this in -next for some time.
> +static void sil_bmdma_stop(struct ata_queued_cmd *qc)
> +{
> + struct ata_port *ap = qc->ap;
> + void __iomem *mmio_base = ap->host->iomap[SIL_MMIO_BAR];
> + void __iomem *bmdma2 = mmio_base + sil_port[ap->port_no].bmdma2;
> +
> + /* clear start/stop bit - can safely always write 0 */
> + writeb(0, bmdma2);
ioread/iowrite?
> + /* one-PIO-cycle guaranteed wait, per spec, for HDMA1:0 transition */
> + ata_sff_dma_pause(ap);
> +}
> +
> +static void sil_bmdma_setup(struct ata_queued_cmd *qc)
> +{
> + struct ata_port *ap = qc->ap;
> + void __iomem *bmdma = ap->ioaddr.bmdma_addr;
> +
> + /* load PRD table addr. */
> + mb(); /* make sure PRD table writes are visible to controller */
I know it's not specific to this change but does mb() really make
sense here? I don't think we need any barrier here.
> + writel(ap->prd_dma, bmdma + ATA_DMA_TABLE_OFS);
> +
> + /* issue r/w command */
> + ap->ops->sff_exec_command(ap, &qc->tf);
> +}
Thanks.
--
tejun
next prev parent reply other threads:[~2008-12-22 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 2:16 [PATCH] sata_sil: add Large Block Transfer support Robert Hancock
2008-12-22 10:19 ` Tejun Heo [this message]
2008-12-23 4:35 ` Robert Hancock
2008-12-23 4:40 ` Tejun Heo
2008-12-23 10:10 ` Alan Cox
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=494F69C4.2060708@kernel.org \
--to=tj@kernel.org \
--cc=hancockr@shaw.ca \
--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).