From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [RFC PATCH 2/4] pio-mapping: Add ARM support for the PIO mapping API
Date: Fri, 05 Feb 2010 10:43:54 -0600 [thread overview]
Message-ID: <1265388234.14404.47.camel@mulgrave.site> (raw)
In-Reply-To: <20100205163154.30827.6636.stgit@pc1117.cambridge.arm.com>
On Fri, 2010-02-05 at 16:31 +0000, Catalin Marinas wrote:
> This patch introduces support for the PIO mapping API on the ARM
> architecture. It is currently only meant as an example for discussions
> and it can be further optimised.
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> ---
> arch/arm/Kconfig | 3 ++
> arch/arm/include/asm/pio-mapping.h | 52 ++++++++++++++++++++++++++++++++++++
> 2 files changed, 55 insertions(+), 0 deletions(-)
> create mode 100644 arch/arm/include/asm/pio-mapping.h
>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 4c33ca8..e48adcf 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -161,6 +161,9 @@ config ARCH_MTD_XIP
> config GENERIC_HARDIRQS_NO__DO_IRQ
> def_bool y
>
> +config HAVE_ARCH_PIO
> + def_bool y
> +
> if OPROFILE
>
> config OPROFILE_ARMV6
> diff --git a/arch/arm/include/asm/pio-mapping.h b/arch/arm/include/asm/pio-mapping.h
> new file mode 100644
> index 0000000..d7c866a
> --- /dev/null
> +++ b/arch/arm/include/asm/pio-mapping.h
> @@ -0,0 +1,52 @@
> +/*
> + * include/linux/pio-mapping.h
> + *
> + * Copyright (C) 2010 ARM Ltd.
> + * Written by Catalin Marinas <catalin.marinas@arm.com>
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + * GNU General Public License for more details.
> + *
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, write to the Free Software
> + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
> + */
> +
> +#ifndef ASM_PIO_MAPPING_H
> +#define ASM_PIO_MAPPING_H
> +
> +#include <asm/cacheflush.h>
> +
> +static inline void *pio_map_single(void *addr, size_t size,
> + enum pio_data_direction dir)
> +{
> + return addr;
This API is a bit semantically nasty to use, isn't it? What we usually
get in the I/O path is a scatter gather list of pages and offsets (or
just a page in the network case).
In a highmem kernel, we'd have to kmap the page before it actually had a
kernel virtual address, so now the use case of the API becomes
vaddr = kmap_...(page)
pio_map_single(vaddr)
and the reverse on unmap.
Why not just combine the two since we always have to do them anyway and
do
kmap_pio ... with the various atomic versions?
enum pio_data_direction dir looks a bit wrong too ... why not just use
the exsiting enum dma_data_direction since that's what the dma API uses?
your pio_map_page is going to have to contain a kmap in the arch
implementation anyway ...
James
next prev parent reply other threads:[~2010-02-05 16:43 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 [this message]
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 ` [RFC PATCH 4/4] pio-mapping: Use the PIO mapping API in the ISP1760 HCD driver Catalin Marinas
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=1265388234.14404.47.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=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).