From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arch@vger.kernel.org
Subject: [RFC PATCH 4/4] pio-mapping: Use the PIO mapping API in the ISP1760 HCD driver
Date: Fri, 05 Feb 2010 16:32:05 +0000 [thread overview]
Message-ID: <20100205163205.30827.22815.stgit@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20100205163044.30827.10915.stgit@pc1117.cambridge.arm.com>
This patch provides another example of PIO API usage. In this case,
there is no struct page information in the HCD driver and the
pio_*_single() functions are used.
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
---
drivers/usb/host/isp1760-hcd.c | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/host/isp1760-hcd.c b/drivers/usb/host/isp1760-hcd.c
index 27b8f7c..e55cb90 100644
--- a/drivers/usb/host/isp1760-hcd.c
+++ b/drivers/usb/host/isp1760-hcd.c
@@ -17,6 +17,7 @@
#include <linux/debugfs.h>
#include <linux/uaccess.h>
#include <linux/io.h>
+#include <linux/pio-mapping.h>
#include <asm/unaligned.h>
#include "../core/hcd.h"
@@ -904,6 +905,10 @@ __acquires(priv->lock)
status = 0;
}
+ pio_unmap_single(urb->transfer_buffer, urb->transfer_buffer_length,
+ usb_pipein(urb->pipe) ?
+ PIO_FROM_DEVICE : PIO_TO_DEVICE);
+
/* complete() can reenter this HCD */
usb_hcd_unlink_urb_from_ep(priv_to_hcd(priv), urb);
spin_unlock(&priv->lock);
@@ -1536,7 +1541,9 @@ static struct list_head *qh_urb_transaction(struct isp1760_hcd *priv,
/*
* data transfer stage: buffer setup
*/
- buf = urb->transfer_buffer;
+ buf = pio_map_single(urb->transfer_buffer, urb->transfer_buffer_length,
+ usb_pipein(urb->pipe) ?
+ PIO_FROM_DEVICE : PIO_TO_DEVICE);
if (is_input)
token |= IN_PID;
prev parent reply other threads:[~2010-02-05 16:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 16:31 [RFC PATCH 0/4] PIO drivers and cache coherency Catalin Marinas
2010-02-05 16:31 ` [RFC PATCH 1/4] pio-mapping: Add generic support for PIO mapping API Catalin Marinas
2010-02-05 16:31 ` [RFC PATCH 2/4] pio-mapping: Add ARM support for the " Catalin Marinas
2010-02-05 16:43 ` James Bottomley
2010-02-05 17:20 ` Catalin Marinas
2010-02-05 17:36 ` James Bottomley
2010-02-05 18:02 ` Catalin Marinas
2010-02-08 16:10 ` Catalin Marinas
2010-02-08 16:54 ` Russell King
2010-02-08 17:20 ` James Bottomley
2010-02-08 17:33 ` Russell King
2010-02-08 19:07 ` James Bottomley
2010-02-08 18:02 ` [RFC PATCH 2/4] pio-mapping: Add ARM support for the PIOmapping API Catalin Marinas
2010-02-08 19:09 ` James Bottomley
2010-02-08 17:14 ` [RFC PATCH 2/4] pio-mapping: Add ARM support for the PIO mapping API James Bottomley
2010-02-09 18:03 ` Catalin Marinas
2010-02-17 9:11 ` Benjamin Herrenschmidt
2010-02-17 20:04 ` Russell King
2010-02-17 20:39 ` Benjamin Herrenschmidt
2010-02-05 16:32 ` [RFC PATCH 3/4] pio-mapping: Use the PIO mapping API in libata-sff.c Catalin Marinas
2010-02-05 16:32 ` Catalin Marinas [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=20100205163205.30827.22815.stgit@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arch@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).