diff options
author | 2017-07-19 14:42:30 +0300 | |
---|---|---|
committer | 2017-07-30 08:23:27 -0700 | |
commit | b064d0e6e42ed4774c42bfbec0db60f8249a9de2 (patch) | |
tree | 28a51e979f69635aa32d128abf95b074e5430bb4 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | staging: fsl-mc: fix formating of phys_addr_t on 32 bits (diff) | |
download | wireguard-linux-b064d0e6e42ed4774c42bfbec0db60f8249a9de2.tar.xz wireguard-linux-b064d0e6e42ed4774c42bfbec0db60f8249a9de2.zip |
staging: fsl-mc: don't use raw device io functions
As raw device io functions are not portable and don't handle byte-order
(triggering suspicion that endianness isn't handled well) switch to
using the standard api.
Since MC expects LE byte-order and the upper layers already take care
of that, we need to trick the device io api by doing a LE -> CPU
conversion just before calling it. This way, the CPU -> LE conversion
done in the api puts the data back in the right byte-order. Obviously,
for reads the extra step is mirrored: there's a CPU -> LE conversion
following the API call.
Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions