From: Jeff Garzik <jeff@garzik.org>
To: Saeed Bishara <saeed@marvell.com>
Cc: linux-ide@vger.kernel.org, liml@rtr.ca, nico@fluxnic.net,
buytenh@wantstofly.org
Subject: Re: [PATCH 1/6] sata_mv: increase PIO IORDY timeout
Date: Thu, 17 Dec 2009 01:03:34 -0500 [thread overview]
Message-ID: <4B29C9B6.7020105@garzik.org> (raw)
In-Reply-To: <1260116782-31714-1-git-send-email-saeed@marvell.com>
On 12/06/2009 11:26 AM, 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(-)
applied 1-4
prev parent reply other threads:[~2009-12-17 6:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 16:26 [PATCH 1/6] sata_mv: increase PIO IORDY timeout Saeed Bishara
2009-12-06 16:26 ` [PATCH 2/6] sata_mv: support clkdev framework Saeed Bishara
2009-12-06 16:26 ` [PATCH 3/6] sata_mv: add power management support for the platform driver Saeed Bishara
2009-12-06 16:26 ` [PATCH 4/6] sata_mv: move the PCI bar description initialization code from mv_init_host to mv_pci_init_one Saeed Bishara
2009-12-06 16:26 ` [PATCH 5/6] sata_mv: store the board_idx into the host private data Saeed Bishara
2009-12-06 16:26 ` [PATCH 6/6] sata_mv: add power management support for the PCI controllers Saeed Bishara
2009-12-07 6:32 ` Grant Grundler
2009-12-17 6:07 ` Jeff Garzik
2009-12-17 6:06 ` [PATCH 5/6] sata_mv: store the board_idx into the host private data Jeff Garzik
2009-12-07 6:14 ` [PATCH 3/6] sata_mv: add power management support for the platform driver Grant Grundler
2009-12-17 6:03 ` Jeff Garzik [this message]
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=4B29C9B6.7020105@garzik.org \
--to=jeff@garzik.org \
--cc=buytenh@wantstofly.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=nico@fluxnic.net \
--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.