From: Kevin Hao <haokexin@gmail.com>
To: linux-ide@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Dan Williams <dan.j.williams@intel.com>
Subject: [PATCH v2 2/2] sata_fsl: set the correct queue depth for the host controller
Date: Sun, 6 Jul 2014 14:28:41 +0800 [thread overview]
Message-ID: <1404628121-8158-3-git-send-email-haokexin@gmail.com> (raw)
In-Reply-To: <1404628121-8158-1-git-send-email-haokexin@gmail.com>
The fsl sata controller only implement a queue depth of 16. So use
the ata_host_set_queue_depth() to set the correct queue depth for
host controller. Also add a WARN_ON_ONCE() if a tag above 16 is
used.
Fixes: 8a4aeec8d2d6 ("libata/ahci: accommodate tag ordered controllers")
Cc: stable@vger.kernel.org
Signed-off-by: Kevin Hao <haokexin@gmail.com>
---
v2: Add a WARN_ON_ONCE().
drivers/ata/sata_fsl.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/ata/sata_fsl.c b/drivers/ata/sata_fsl.c
index 07bc7e4dbd04..ae55440af86d 100644
--- a/drivers/ata/sata_fsl.c
+++ b/drivers/ata/sata_fsl.c
@@ -402,6 +402,7 @@ static inline unsigned int sata_fsl_tag(unsigned int tag,
if (unlikely(tag >= SATA_FSL_QUEUE_DEPTH)) {
DPRINTK("tag %d invalid : out of range\n", tag);
+ WARN_ON_ONCE(1);
return 0;
}
@@ -1506,6 +1507,8 @@ static int sata_fsl_probe(struct platform_device *ofdev)
goto error_exit_with_cleanup;
}
+ ata_host_set_queue_depth(host, SATA_FSL_QUEUE_DEPTH);
+
/* host->iomap is not used currently */
host->private_data = host_priv;
--
1.9.3
prev parent reply other threads:[~2014-07-06 6:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-06 6:28 [PATCH v2 0/2] libata: support the ata host which implements a queue depth less than 32 Kevin Hao
2014-07-06 6:28 ` [PATCH v2 1/2] libata: introduce ata_host_set_queue_depth() Kevin Hao
2014-07-07 13:49 ` Tejun Heo
2014-07-08 2:58 ` Kevin Hao
2014-07-07 18:19 ` Dan Williams
2014-07-07 20:06 ` Tejun Heo
2014-07-07 20:56 ` Dan Williams
2014-07-08 2:41 ` Kevin Hao
2014-07-06 6:28 ` Kevin Hao [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=1404628121-8158-3-git-send-email-haokexin@gmail.com \
--to=haokexin@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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