linux-kernel - Re: [PATCH] staging: xillybus: Move out of staging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 02 Sep 2014 13:23:41 +0300
From:	Eli Billauer <eli.billauer@...il.com>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	Dan Carpenter <dan.carpenter@...cle.com>,
	gregkh@...uxfoundation.org, arnd@...db.de,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: xillybus: Move out of staging

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/