All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Saeed Bishara <saeed@marvell.com>
Cc: linux-ide@vger.kernel.org, liml@rtr.ca, saeed.bishara@gmail.com
Subject: Re: [PATCH 1/3] sata_mv: increase PIO IORDY timeout
Date: Wed, 24 Jun 2009 04:33:08 -0400	[thread overview]
Message-ID: <4A41E4C4.7050508@garzik.org> (raw)
In-Reply-To: <1245771838-1332-1-git-send-email-saeed@marvell.com>

Saeed Bishara wrote:
> The old value (0xbc) in cycles of the IORDY timeout is suitable for
> devices with core clock of 166 MHz, but some SoC controllers have
> faster core clocks. The new value will make the IORDY timeout large
> enough also for all SoC devices.
> 
> Signed-off-by: Saeed Bishara <saeed@marvell.com>
> ---
>  drivers/ata/sata_mv.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/ata/sata_mv.c b/drivers/ata/sata_mv.c
> index 23714ae..644436e 100644
> --- a/drivers/ata/sata_mv.c
> +++ b/drivers/ata/sata_mv.c
> @@ -3368,7 +3368,7 @@ static void mv_soc_reset_hc_port(struct mv_host_priv *hpriv,
>  	ZERO(0x024);		/* respq outp */
>  	ZERO(0x020);		/* respq inp */
>  	ZERO(0x02c);		/* test control */
> -	writel(0xbc, port_mmio + EDMA_IORDY_TMOUT);
> +	writel(0x800, port_mmio + EDMA_IORDY_TMOUT);

Do we really want to increase the timeout for older devices?  How does 
this change behavior for existing devices?

	Jeff





  parent reply	other threads:[~2009-06-24  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 15:43 [PATCH 1/3] sata_mv: increase PIO IORDY timeout Saeed Bishara
2009-06-23 15:43 ` [PATCH 2/3] sata_mv: support clkdev framework Saeed Bishara
2009-06-23 15:43   ` [PATCH 3/3] sata_mv: add power management support for the platform driver Saeed Bishara
2009-06-24  8:33 ` Jeff Garzik [this message]
2009-06-24 10:23   ` [PATCH 1/3] sata_mv: increase PIO IORDY timeout Saeed Bishara
2009-12-01 15:37     ` saeed bishara
2009-12-03 17:55       ` 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=4A41E4C4.7050508@garzik.org \
    --to=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=saeed.bishara@gmail.com \
    --cc=saeed@marvell.com \
    /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.