From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1WoT7M-0007rE-22 for ath10k@lists.infradead.org; Sun, 25 May 2014 07:45:16 +0000 From: Kalle Valo Subject: Re: [PATCH 3/3] ath10k: add explicit memory barrier for ring index update References: <1400158139-13836-1-git-send-email-michal.kazior@tieto.com> <1400158139-13836-4-git-send-email-michal.kazior@tieto.com> Date: Sun, 25 May 2014 10:44:46 +0300 In-Reply-To: <1400158139-13836-4-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 15 May 2014 14:48:59 +0200") Message-ID: <87mwe6ti8h.fsf@kamboji.qca.qualcomm.com> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Michal Kazior Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org, apenwarr@gmail.com Michal Kazior writes: > Avery reported he had some issues related to > instructions being re-ordered on his ARM test > system resulting in firmware crashes. > > This makes sure that data is in place before CE > ring index is updated telling firmware it can > fetch the data. > > Reported-By: Avery Pennarun > Signed-off-by: Michal Kazior I have dropped this patch for now. Like I said before, let's first be sure that all memory barrier issues are resolved and only then apply this. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k