diff options
author | 2015-12-08 16:47:21 +0100 | |
---|---|---|
committer | 2016-03-03 09:17:17 +0100 | |
commit | 52807ae90e76b69fd01688d6031190271536d29f (patch) | |
tree | 6c0f5fd554797a733db7f530e7c2a1521cc9fad8 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | drm: sti: remove sti_gem_prime_export hack (diff) | |
download | linux-dev-52807ae90e76b69fd01688d6031190271536d29f.tar.xz linux-dev-52807ae90e76b69fd01688d6031190271536d29f.zip |
drm/sti: use u32 to store DMA addresses
The STi drm driver correctly warns about invalid format strings
when built with 64-bit dma_addr_t:
sti_hqvdp.c: In function 'sti_hqvdp_vtg_cb':
sti_hqvdp.c:605:119: warning: format '%x' expects argument of type
'unsigned int', but argument 5 has type 'dma_addr_t {aka long long
unsigned int}' [-Wformat=]
sti_hqvdp.c: In function 'sti_hqvdp_atomic_update':
sti_hqvdp.c:931:118: warning: format '%x' expects argument of type
'unsigned int', but argument 5 has type 'dma_addr_t {aka long long
unsigned int}' [-Wformat=]
This could be changed to using the %pad format string, but that
does not work when printing an rvalue, so instead I'm changing
the type in the sti_hqvdp structure to u32, which is what gets
written into the registers anyway.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Vincent Abriou <vincent.abriou@st.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions