From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 3/5] sil24: use SRST for phy_reset
Date: Wed, 16 Nov 2005 07:28:01 -0500 [thread overview]
Message-ID: <437B25D1.3000805@pobox.com> (raw)
In-Reply-To: <20051116080505.GC22807@htj.dyndns.org>
Tejun Heo wrote:
> There seems to be no way to obtain device signature from sil24 after
> SATA phy reset and SRST is needed anyway for later port multiplier
> suppport. This patch converts sil24_phy_reset to use SRST instaed.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
>
> Index: work/drivers/scsi/sata_sil24.c
> ===================================================================
> --- work.orig/drivers/scsi/sata_sil24.c 2005-11-16 16:58:01.000000000 +0900
> +++ work/drivers/scsi/sata_sil24.c 2005-11-16 17:02:56.000000000 +0900
> @@ -333,7 +333,7 @@ static struct ata_port_info sil24_port_i
> {
> .sht = &sil24_sht,
> .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
> - ATA_FLAG_SATA_RESET | ATA_FLAG_MMIO |
> + ATA_FLAG_SRST | ATA_FLAG_MMIO |
> ATA_FLAG_PIO_DMA | SIL24_NPORTS2FLAG(4),
> .pio_mask = 0x1f, /* pio0-4 */
> .mwdma_mask = 0x07, /* mwdma0-2 */
> @@ -344,7 +344,7 @@ static struct ata_port_info sil24_port_i
> {
> .sht = &sil24_sht,
> .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
> - ATA_FLAG_SATA_RESET | ATA_FLAG_MMIO |
> + ATA_FLAG_SRST | ATA_FLAG_MMIO |
> ATA_FLAG_PIO_DMA | SIL24_NPORTS2FLAG(2),
> .pio_mask = 0x1f, /* pio0-4 */
> .mwdma_mask = 0x07, /* mwdma0-2 */
> @@ -355,7 +355,7 @@ static struct ata_port_info sil24_port_i
> {
> .sht = &sil24_sht,
> .host_flags = ATA_FLAG_SATA | ATA_FLAG_NO_LEGACY |
> - ATA_FLAG_SATA_RESET | ATA_FLAG_MMIO |
> + ATA_FLAG_SRST | ATA_FLAG_MMIO |
> ATA_FLAG_PIO_DMA | SIL24_NPORTS2FLAG(1),
> .pio_mask = 0x1f, /* pio0-4 */
> .mwdma_mask = 0x07, /* mwdma0-2 */
This is not only OK, it is preferred, since 3124 port reset issues
COMRESET for us.
> @@ -415,16 +415,69 @@ static void sil24_tf_read(struct ata_por
> *tf = pp->tf;
> }
>
> +static int sil24_issue_SRST(struct ata_port *ap)
> +{
> + void __iomem *port = (void __iomem *)ap->ioaddr.cmd_addr;
> + struct sil24_port_priv *pp = ap->private_data;
> + struct sil24_prb *prb = &pp->cmd_block[0].prb;
> + dma_addr_t paddr = pp->cmd_block_dma;
> + u32 irq_enable, irq_stat;
> + int cnt;
> +
> + /* temporarily turn off IRQs during SRST */
> + irq_enable = readl(port + PORT_IRQ_ENABLE_SET);
> + writel(irq_enable, port + PORT_IRQ_ENABLE_CLR);
> +
> + /* delay 10 ms */
> + udelay(10000);
NAK:
* long udelay (always NAK'd), as they chew processor and lock out other
things, for no reason.
* passing 1000 or more to udelay() means you should use mdelay() instead
* in this case, msleep() works just fine
* I don't see why this delay is needed at all?
> + prb->ctrl = PRB_CTRL_SRST;
> + prb->fis[1] = 0; /* no PM yet */
> +
> + writel((u32)paddr, port + PORT_CMD_ACTIVATE);
> +
> + for (cnt = 0; cnt < 100; cnt++) {
> + irq_stat = readl(port + PORT_IRQ_STAT);
> + writel(irq_stat, port + PORT_IRQ_STAT); /* clear irq */
> +
> + irq_stat >>= PORT_IRQ_RAW_SHIFT;
> + if (irq_stat & (PORT_IRQ_COMPLETE | PORT_IRQ_ERROR))
> + break;
> +
> + udelay(1000);
NAK:
* long udelay (always NAK'd)
* passing 1000 or more to udelay() means you should use mdelay() instead
* in this case, msleep() works just fine
next prev parent reply other threads:[~2005-11-16 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 8:05 [PATCH 3/5] sil24: use SRST for phy_reset Tejun Heo
2005-11-16 12:28 ` Jeff Garzik [this message]
2005-11-16 13:24 ` Tejun Heo
2005-11-16 14:46 ` Mark Lord
2005-11-16 15:03 ` 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=437B25D1.3000805@pobox.com \
--to=jgarzik@pobox.com \
--cc=htejun@gmail.com \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.