From: Kumar Gala <galak@kernel.crashing.org>
To: Li Yang <leoli@freescale.com>
Cc: Zhang Wei <zw@zh-kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, linuxppc-dev@ozlabs.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 1/6] rapidio: add common mapping APIs for RapidIO memory access
Date: Wed, 10 Jun 2009 23:13:00 -0500 [thread overview]
Message-ID: <90AED712-28A1-4800-978C-125A887D0DA7@kernel.crashing.org> (raw)
In-Reply-To: <1242117363-14949-1-git-send-email-leoli@freescale.com>
On May 12, 2009, at 3:35 AM, Li Yang wrote:
> Add the mapping functions used to support direct IO memory access of
> rapidIO.
>
> Signed-off-by: Zhang Wei <zw@zh-kernel.org>
> Signed-off-by: Li Yang <leoli@freescale.com>
Use inbnd/outbnd instead of inb/outb which make one think of byte
level io accessors.
As I look at this I don't think this is the correct API. I think we
should be using the DMA mapping API to hide these details. The
concept of mapping like this seems to be more a function of FSL's
Address translation/mapping unit (ATMU) than anything specific to the
RIO bus standard.
> ---
> drivers/rapidio/rio.c | 95 ++++++++++++++++++++++++++++++++++++++
> +++++++++
> include/linux/rio.h | 25 ++++++++++++
> include/linux/rio_drv.h | 24 +++++++++---
> 3 files changed, 138 insertions(+), 6 deletions(-)
- k
next prev parent reply other threads:[~2009-06-11 4:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 8:35 [PATCH 1/6] rapidio: add common mapping APIs for RapidIO memory access Li Yang
2009-05-12 8:35 ` [PATCH 2/6] powerpc/fsl_rio: use LAW address from device tree Li Yang
2009-05-12 8:36 ` [PATCH 3/6] powerpc: add memory map support to Freescale RapidIO block Li Yang
2009-05-12 8:36 ` [PATCH 4/6] rionet: add memory access to simulated Ethernet over rapidio Li Yang
2009-05-12 8:36 ` [PATCH 5/6] rio: warn_unused_result warnings fix Li Yang
2009-05-12 8:36 ` [PATCH 6/6] rio: fix section mismatch Li Yang
2009-05-13 22:08 ` Kumar Gala
2009-05-12 22:11 ` [PATCH 5/6] rio: warn_unused_result warnings fix Andrew Morton
2009-06-11 4:34 ` Kumar Gala
2009-05-12 22:10 ` [PATCH 4/6] rionet: add memory access to simulated Ethernet over rapidio Andrew Morton
2009-05-12 22:05 ` [PATCH 3/6] powerpc: add memory map support to Freescale RapidIO block Andrew Morton
2009-05-21 10:43 ` Li Yang
2009-05-13 22:08 ` [PATCH 2/6] powerpc/fsl_rio: use LAW address from device tree Kumar Gala
2009-06-11 4:13 ` Kumar Gala [this message]
2009-06-11 9:47 ` [PATCH 1/6] rapidio: add common mapping APIs for RapidIO memory access Li Yang-R58472
2009-06-11 13:32 ` Kumar Gala
2009-06-12 13:27 ` Li Yang
2009-06-12 13:58 ` Kumar Gala
2009-06-15 10:38 ` Li Yang
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=90AED712-28A1-4800-978C-125A887D0DA7@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=zw@zh-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).