[PATCH 03/11] ath10k_sdio: DMA bounce buffers for read write

Kalle Valo kvalo at qca.qualcomm.com
Mon Jan 8 04:58:52 PST 2018

Alagu Sankar <alagusankar at silex-india.com> writes:

> On 2017-12-22 21:38, Kalle Valo wrote:
>> silexcommon at gmail.com writes:
>>> From: Alagu Sankar <alagusankar at silex-india.com>
>>> Some SD host controllers still need bounce buffers for SDIO data
>>> transfers. While the transfers worked fine on x86 platforms,
>>> this is found to be required for i.MX6 based systems.
>>> Changes are similar to and derived from the ath6kl sdio driver.
>>> Signed-off-by: Alagu Sankar <alagusankar at silex-india.com>
>> Why is the bounce buffer needed exactly, what are the symptoms etc? To
>> me this sounds like an ugly workaround for a SDIO controller driver
>> bug.
> We faced problems with i.MX6. The authentication frame sent by the
> driver never reached the air. The host driver accepted the buffer, but
> did not send out the packet to the sdio module. No errors reported
> anywhere, but the buffer is not accepted due to alignment.

So what kind of alignment works with i.MX6 and how are the packets
aligned by ath10k? Of course, this might be still a bug in ath10k but
most likely it's elsewhere and should be properly investigated. There
must be a much better approach to handle this problem.

> The same driver however works fine without bounce buffer on x86
> platform with stdhci drivers. To make it compliant with all host
> controllers, we introduced the bounce buffers, similar to what was
> done in ath6kl_sdio drivers.

That bounce buffer was horrible in ath6kl and with the bounce buffer you
are forcing all working platforms to suffer from a copy of every packet.
And ath10k is getting so complex that we really need to keep the code as
simple as possible to keep it maintainable.

Kalle Valo

More information about the ath10k mailing list