From: Eli Billauer <eli.billauer@gmail.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
gregkh@linuxfoundation.org, arnd@arndb.de,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: xillybus: Move out of staging
Date: Tue, 02 Sep 2014 13:23:41 +0300 [thread overview]
Message-ID: <54059AAD.2060905@gmail.com> (raw)
In-Reply-To: <54046FDA.8060905@broadcom.com>
Hello, Arend.
On 01/09/14 16:08, Arend van Spriel wrote:
> Maybe it would be better to use the DMA-API instead of the PCI wrappers.
I just found out that the PCI wrappers were indeed removed from the
DMA-API.txt documentation back in 2010, saying that "driver writers are
always able to use the DMA API with any bus":
https://lkml.org/lkml/2010/3/8/470
On the other hand, I was under the impression that the PCI API is for
(future?) platforms which may need a distinction between PCI and
non-PCI. That is why the Xillybus driver does some acrobatics, so that
the PCI API is used for PCI devices, and the general DMA API for non-PCI
devices.
Given that the distinction is already there, is it wise to remove it,
and use the plain DMA API for all? That will simplify the code, of
course, but if there's any esoteric platform that needs a different
treatment for PCI devices, it's better to stay as is, I suppose.
Thanks,
Eli
next prev parent reply other threads:[~2014-09-02 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 7:57 [PATCH] staging: xillybus: Move out of staging Eli Billauer
2014-09-01 12:13 ` Dan Carpenter
2014-09-01 13:08 ` Arend van Spriel
2014-09-02 10:23 ` Eli Billauer [this message]
2014-09-01 17:22 ` Joe Perches
2014-09-01 18:55 ` Eli Billauer
2014-09-04 15:23 ` Eli Billauer
2014-09-01 12:33 ` Tobias Klauser
2014-09-01 19:01 ` Eli Billauer
2014-09-01 19:12 ` Greg KH
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=54059AAD.2060905@gmail.com \
--to=eli.billauer@gmail.com \
--cc=arend@broadcom.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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).