redonkable/remarkable-linux
redonkable/remarkable-linux
1
0
Fork 0
Code Releases Activity

Staging: vme: Rename VME DMA functions

Browse source 
The DMA resource allocation function is called "vme_request_dma" while
master and slave window allocation functions are called
"vme_master_request" and "vme_slave_request" respectively. Rename
"vme_request_dma" to "vme_dma_request" to fit the pattern.

Signed-off-by: Martyn Welch <martyn.welch@gefanuc.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
This commit is contained in:
Martyn Welch 2009-10-29 16:35:20 +00:00 committed by Greg Kroah-Hartman
parent a4b02959d5
commit 58e507987b
4 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
drivers/staging/vme/TODO
View file

@ -11,7 +11,7 @@ The current DMA resource Allocation provides no means of selecting the
suitability of a DMA controller based on it's supported modes of operation, as
opposed to the resource allocation mechanisms for master and slave windows:
struct vme_resource *vme_request_dma(struct device *dev);
struct vme_resource *vme_dma_request(struct device *dev);
As opposed to:

4
drivers/staging/vme/vme.c
View file

@ -643,7 +643,7 @@ EXPORT_SYMBOL(vme_master_free);
* Request a DMA controller with specific attributes, return some unique
* identifier.
*/
struct vme_resource *vme_request_dma(struct device *dev)
struct vme_resource *vme_dma_request(struct device *dev)
{
struct vme_bridge *bridge;
struct list_head *dma_pos = NULL;
@ -704,7 +704,7 @@ err_ctrlr:
err_bus:
return NULL;
}
EXPORT_SYMBOL(vme_request_dma);
EXPORT_SYMBOL(vme_dma_request);
/*
* Start new list

2
drivers/staging/vme/vme.h
View file

@ -123,7 +123,7 @@ unsigned int vme_master_rmw (struct vme_resource *, unsigned int, unsigned int,
unsigned int, loff_t);
void vme_master_free(struct vme_resource *);
struct vme_resource *vme_request_dma(struct device *);
struct vme_resource *vme_dma_request(struct device *);
struct vme_dma_list *vme_new_dma_list(struct vme_resource *);
struct vme_dma_attr *vme_dma_pattern_attribute(u32, vme_pattern_t);
struct vme_dma_attr *vme_dma_pci_attribute(dma_addr_t);

2
drivers/staging/vme/vme_api.txt
View file

@ -77,7 +77,7 @@ driver in question:
struct vme_resource * vme_slave_request(struct device *dev,
vme_address_t aspace, vme_cycle_t cycle);
struct vme_resource *vme_request_dma(struct device *dev);
struct vme_resource *vme_dma_request(struct device *dev);
For slave windows these attributes are split into those of type 'vme_address_t'
and 'vme_cycle_t'. Master windows add a further set of attributes 'vme_cycle_t'.