This patch shows an example of PIO API usage for non-highmem pages. It
currently only modifies the !highmem case. While it is indicated to no
longer differentiate between these, there is a benefit for the !highmem
case to use the non-atomic kmap API.
Signed-off-by: Catalin Marinas <catalin.marinas@xxxxxxx>
Cc: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
Cc: Russell King <rmk@xxxxxxxxxxxxxxxx>
---
drivers/ata/libata-sff.c | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c
index 741065c..02a3be9 100644
--- a/drivers/ata/libata-sff.c
+++ b/drivers/ata/libata-sff.c
@@ -36,6 +36,7 @@
#include <linux/pci.h>
#include <linux/libata.h>
#include <linux/highmem.h>
+#include <linux/pio-mapping.h>
#include "libata.h"
@@ -888,9 +889,13 @@ static void ata_pio_sector(struct ata_queued_cmd *qc)
kunmap_atomic(buf, KM_IRQ0);
local_irq_restore(flags);
} else {
- buf = page_address(page);
+ enum dma_data_direction dir = do_write ?
+ DMA_TO_DEVICE : DMA_FROM_DEVICE;
+
+ buf = pio_kmap(page, dir);
ap->ops->sff_data_xfer(qc->dev, buf + offset, qc->sect_size,
do_write);
+ pio_kunmap(page, dir);
}
qc->curbytes += qc->sect_size;
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
