Re: [PATCH v2 3/3] ath10k: make target endianess more explicit

2014-08-27 Thread Michal Kazior
On 27 August 2014 09:28, Kalle Valo wrote: > Michal Kazior writes: > >> Some copy engine structures are target specific >> and are uploaded to the device during >> init/configuration. >> >> This also cleans up a bit diag_mem_read/write >> implicit byteswap mess leaving only >> diag_access_read/wr

Re: [PATCH v2 3/3] ath10k: make target endianess more explicit

2014-08-27 Thread Michal Kazior
On 27 August 2014 09:26, Kalle Valo wrote: > Michal Kazior writes: > >> Some copy engine structures are target specific >> and are uploaded to the device during >> init/configuration. >> >> This also cleans up a bit diag_mem_read/write >> implicit byteswap mess leaving only >> diag_access_read/wr

Re: [PATCH v2 3/3] ath10k: make target endianess more explicit

2014-08-27 Thread Kalle Valo
Michal Kazior writes: > Some copy engine structures are target specific > and are uploaded to the device during > init/configuration. > > This also cleans up a bit diag_mem_read/write > implicit byteswap mess leaving only > diag_access_read/write with an implicit endianess > byteswap. > > Signed-

Re: [PATCH v2 3/3] ath10k: make target endianess more explicit

2014-08-27 Thread Kalle Valo
Michal Kazior writes: > Some copy engine structures are target specific > and are uploaded to the device during > init/configuration. > > This also cleans up a bit diag_mem_read/write > implicit byteswap mess leaving only > diag_access_read/write with an implicit endianess > byteswap. > > Signed-

[PATCH v2 3/3] ath10k: make target endianess more explicit

2014-08-25 Thread Michal Kazior
Some copy engine structures are target specific and are uploaded to the device during init/configuration. This also cleans up a bit diag_mem_read/write implicit byteswap mess leaving only diag_access_read/write with an implicit endianess byteswap. Signed-off-by: Michal Kazior --- Notes: v2: