Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758082AbbLBM5K (ORCPT ); Wed, 2 Dec 2015 07:57:10 -0500 Received: from mail-wm0-f43.google.com ([74.125.82.43]:36509 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756425AbbLBM5H (ORCPT ); Wed, 2 Dec 2015 07:57:07 -0500 Subject: Re: [PATCH 2/4] dmaengine: qcom_bam_dma: clear BAM interrupt only if it is rised To: Arnd Bergmann , linux-arm-kernel@lists.infradead.org References: <1448961299-15161-1-git-send-email-stanimir.varbanov@linaro.org> <1448961299-15161-3-git-send-email-stanimir.varbanov@linaro.org> <6461444.oollnBsbrb@wuerfel> Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, dmaengine@vger.kernel.org, Vinod Koul , Mark Rutland , Archit Taneja , Pawel Moll , Ian Campbell , Rob Herring , Andy Gross From: Stanimir Varbanov Message-ID: <565EEA99.3070207@linaro.org> Date: Wed, 2 Dec 2015 14:56:57 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <6461444.oollnBsbrb@wuerfel> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1617 Lines: 41 On 12/01/2015 12:29 PM, Arnd Bergmann wrote: > On Tuesday 01 December 2015 11:14:57 Stanimir Varbanov wrote: >> + if (srcs & BAM_IRQ) { >> clr_mask = readl_relaxed(bam_addr(bdev, 0, BAM_IRQ_STTS)); >> >> - /* don't allow reorder of the various accesses to the BAM registers */ >> - mb(); >> + /* >> + * don't allow reorder of the various accesses to the BAM >> + * registers >> + */ >> + mb(); >> >> - writel_relaxed(clr_mask, bam_addr(bdev, 0, BAM_IRQ_CLR)); >> + writel_relaxed(clr_mask, bam_addr(bdev, 0, BAM_IRQ_CLR)); >> + } >> > > I think the comment here should be moved: change the writel_relaxed() > to writel(), which already includes the appropriate barriers, and If we agree with such a change it should be subject to another patch. > add a comment at the readl_relaxed() to explain why it doesn't need > a barrier. Infact I'm not sure that readl_relaxed(BAM_IRQ_STTS) does not need barrier. If I read the code above correctly the mb() should guarantee that all load and store operations before it are happened before the write to BAM_IRQ_CLR register, and on the other hand if we replace writel_relaxed with writel, the writel has wmb() which guarantees only store operations. Did I miss something? -- regards, Stan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/