From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "silexcommon@gmail.com" <silexcommon@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Alagu Sankar <alagusankar@silex-india.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 03/11] ath10k_sdio: DMA bounce buffers for read write
Date: Fri, 22 Dec 2017 16:08:40 +0000 [thread overview]
Message-ID: <87lghu9247.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1506793068-27445-4-git-send-email-alagusankar@silex-india.com> (silexcommon@gmail.com's message of "Sat, 30 Sep 2017 23:07:40 +0530")
silexcommon@gmail.com writes:
> From: Alagu Sankar <alagusankar@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@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.
--=20
Kalle Valo=
next prev parent reply other threads:[~2017-12-22 16:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 17:37 [PATCH 00/11] SDIO support for ath10k silexcommon
2017-09-30 17:37 ` [PATCH 01/11] ath10k_sdio: sdio htt data transfer fixes silexcommon
2017-10-02 7:36 ` Arend van Spriel
2017-10-02 7:44 ` Alagu Sankar
2017-10-04 8:55 ` Kalle Valo
2017-09-30 17:37 ` [PATCH 02/11] ath10k_sdio: wb396 reference card fix silexcommon
2017-10-01 22:47 ` Steve deRosier
2017-10-02 7:02 ` Alagu Sankar
2017-10-02 9:06 ` Erik Stromdahl
2017-09-30 17:37 ` [PATCH 03/11] ath10k_sdio: DMA bounce buffers for read write silexcommon
2017-12-22 16:08 ` Kalle Valo [this message]
2017-12-25 12:26 ` Alagu Sankar
2017-12-25 16:11 ` Adrian Chadd
2017-12-27 18:49 ` Arend van Spriel
2017-12-27 19:26 ` Adrian Chadd
2018-01-08 12:58 ` Kalle Valo
2017-09-30 17:37 ` [PATCH 04/11] ath10k_sdio: reduce transmit msdu count silexcommon
2017-09-30 17:37 ` [PATCH 05/11] ath10k_sdio: use clean packet headers silexcommon
2017-09-30 17:37 ` [PATCH 06/11] ath10k_sdio: high latency fixes for beacon buffer silexcommon
2017-09-30 17:37 ` [PATCH 07/11] ath10k_sdio: fix rssi indication silexcommon
2017-09-30 17:37 ` [PATCH 08/11] ath10k_sdio: common read write silexcommon
2017-10-04 9:49 ` Kalle Valo
2017-10-05 10:09 ` [08/11] " Gary Bisson
2017-10-05 17:33 ` Alagu Sankar
2017-12-08 14:42 ` Gary Bisson
2017-09-30 17:37 ` [PATCH 09/11] ath10k_sdio: virtual scatter gather for receive silexcommon
2017-10-04 19:56 ` Erik Stromdahl
2017-09-30 17:37 ` [PATCH 10/11] ath10k_sdio: enable firmware crash dump silexcommon
2017-09-30 17:37 ` [PATCH 11/11] ath10k_sdio: hif start once addition silexcommon
2017-10-02 9:02 ` [PATCH 00/11] SDIO support for ath10k Erik Stromdahl
2017-10-04 6:22 ` Alagu Sankar
2017-10-04 15:53 ` Erik Stromdahl
2017-10-05 15:12 ` Gary Bisson
2017-10-05 17:24 ` Alagu Sankar
2017-10-06 11:16 ` Gary Bisson
2017-12-18 16:19 ` Gary Bisson
2017-12-22 16:21 ` Kalle Valo
2017-12-22 16:25 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lghu9247.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=alagusankar@silex-india.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=silexcommon@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).