diff options
| author | Tushar Dave <tushar.n.dave@oracle.com> | 2016-11-24 12:35:16 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-11-28 15:51:31 -0500 |
| commit | 16f46050e7094a95554555a505a984535d253cf6 (patch) | |
| tree | 0cd8e73b52b77fbf26ca83114fa9a71a0dc0c855 /lib/ts_bm.c | |
| parent | e58566b1b17fef5c4590e652a337afe66277131a (diff) | |
| download | linux-16f46050e7094a95554555a505a984535d253cf6.tar.bz2 | |
dbri: Fix compiler warning
dbri uses 'u32' for dma handle while invoking kernel DMA APIs,
instead of using dma_addr_t. This hasn't caused any 'incompatible
pointer type' warning on SPARC because until now dma_addr_t is of
type u32. However, recent changes in SPARC ATU (iommu) enabled 64bit
DMA and therefore dma_addr_t became of type u64. This makes
'incompatible pointer type' warnings inevitable.
e.g.
sound/sparc/dbri.c: In function ‘snd_dbri_create’:
sound/sparc/dbri.c:2538: warning: passing argument 3 of ‘dma_zalloc_coherent’ from incompatible pointer type
./include/linux/dma-mapping.h:608: note: expected ‘dma_addr_t *’ but argument is of type ‘u32 *’
For the record, dbri(sbus) driver never executes on sun4v. Therefore
even though 64bit DMA is enabled on SPARC, dbri continues to use
legacy iommu that guarantees DMA address is always in 32bit range.
This patch resolves above compiler warning.
Signed-off-by: Tushar Dave <tushar.n.dave@oracle.com>
Reviewed-by: thomas tai <thomas.tai@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'lib/ts_bm.c')
0 files changed, 0 insertions, 0 deletions