Received: by 10.192.165.148 with SMTP id m20csp1658197imm; Wed, 25 Apr 2018 23:44:38 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpiO5BfSikJs7ldnuzizhK3fNFoFibEjRJOY5fc76jX3QC81HGQ0LU2REJojgTsp4I5jK7i X-Received: by 10.99.0.86 with SMTP id 83mr3558732pga.29.1524725078500; Wed, 25 Apr 2018 23:44:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524725078; cv=none; d=google.com; s=arc-20160816; b=COz/UhNy430JHazPIm+ZBOyVxrKeg62aYCOUf3MSOT3SJ2XcEqTUQbrs4KatEhJW4D ik7oPhEDwHTw71rgWoLN57SbP+L+vwj4EdEz8p78axLMbwIRuWlv0dZH1hS1GhQ2rUrI u9A7Z5QnOy6fr2/T3enMba//8W1erksF1jPQLLCVldJma+CK8+tR8dnw3xLmdL/YV0Lr woa66ox8ivBZqukKTyK67HGg52ms+kVxx0Zxe64ZcZtNoRS91X+X/yStwjgXPFAbtiEc Uyhl/2qTKFmvri7FEun21OruJsNQw/+cu0W0u4t8f5Et9MDFPZ+e9uj6d+3UJ+l4wFNX oPpg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=kzOaEQ5wt6roKJfPCpXm4N+Yo/eDqiT+qA8Jj/ATQuo=; b=IgJp50amAGDQPEbsdSQhnC65CkTr/2iRa/jirPL4YirizxR7xOqYgcZHKjmIN6AHyA FStksqRcM5dreL71jWI48jP+I6i4xTeA/GkM6uwRiw5VrH8VzTQfvd5u4+7mCxC0EqIz z25+N4Ms1Vh7rKgKXjSaOiiQNolmis0cuGd79z4jiooFjockc35aNH8Rx3bBXr+sCJ2V aC/yaT2rDr5c1J8/ZrRw3AjY/oAmyO4rNo/t+93eTNuH2LQ2UueGYGpVQeJgybo1hEX2 eUcLloiAZMGmBWb7cxGk/6ohkEI1LVj3gYZuillaZn+vM1++OGEaFa6RDr8t5scHcw86 +4qg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bi10-v6si41658plb.399.2018.04.25.23.44.24; Wed, 25 Apr 2018 23:44:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753565AbeDZGnW (ORCPT + 99 others); Thu, 26 Apr 2018 02:43:22 -0400 Received: from verein.lst.de ([213.95.11.211]:40552 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752630AbeDZGnS (ORCPT ); Thu, 26 Apr 2018 02:43:18 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id A966C68DA7; Thu, 26 Apr 2018 08:45:00 +0200 (CEST) Date: Thu, 26 Apr 2018 08:45:00 +0200 From: "hch@lst.de" To: Alexey Brodkin Cc: "hch@lst.de" , "deanbo422@gmail.com" , "linux-sh@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "nios2-dev@lists.rocketboards.org" , "linux-xtensa@linux-xtensa.org" , "linux-m68k@lists.linux-m68k.org" , "linux-alpha@vger.kernel.org" , "linux-hexagon@vger.kernel.org" , "linux-snps-arc@lists.infradead.org" , "green.hu@gmail.com" , "openrisc@lists.librecores.org" , "linux-arm-kernel@lists.infradead.org" , "monstr@monstr.eu" , "linux-parisc@vger.kernel.org" , "linux-c6x-dev@linux-c6x.org" , "linux-arch@vger.kernel.org" , "sparclinux@vger.kernel.org" Subject: Re: [PATCH 06/22] arc: use generic dma_noncoherent_ops Message-ID: <20180426064500.GB13895@lst.de> References: <20180420080313.18796-1-hch@lst.de> <20180420080313.18796-7-hch@lst.de> <1524655020.5315.9.camel@synopsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1524655020.5315.9.camel@synopsys.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 25, 2018 at 11:17:01AM +0000, Alexey Brodkin wrote: > Which is actually strange as I would expect ARC code to be built by bots. I don't think I got any notification. Thank for the fixes! I think I found the bug, based on the fact that so far all tests for architectures that also need a cache op for device to cpu transitions failed. I did a stupid typo when changing kconfig symbols, so please try the patch below. > > static int l2_line_sz; > static int ioc_exists; > -int slc_enable = 1, ioc_enable = 1; > +int slc_enable = 1, ioc_enable = 0; Hmm. It seems if ioc_enable is 0 we should simply be using dma_direct_ops on arc, but that is a different discussion. --- diff --git a/lib/dma-noncoherent.c b/lib/dma-noncoherent.c index f4b8532c20ac..a2c192b3508d 100644 --- a/lib/dma-noncoherent.c +++ b/lib/dma-noncoherent.c @@ -48,7 +48,7 @@ static int dma_noncoherent_map_sg(struct device *dev, struct scatterlist *sgl, return nents; } -#ifdef CONFIG_DMA_NONCOHERENT_SYNC_FOR_CPU +#ifdef CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU static void dma_noncoherent_sync_single_for_cpu(struct device *dev, dma_addr_t addr, size_t size, enum dma_data_direction dir) { @@ -88,7 +88,7 @@ const struct dma_map_ops dma_noncoherent_ops = { .sync_sg_for_device = dma_noncoherent_sync_sg_for_device, .map_page = dma_noncoherent_map_page, .map_sg = dma_noncoherent_map_sg, -#ifdef CONFIG_DMA_NONCOHERENT_SYNC_FOR_CPU +#ifdef CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU .sync_single_for_cpu = dma_noncoherent_sync_single_for_cpu, .sync_sg_for_cpu = dma_noncoherent_sync_sg_for_cpu, .unmap_page = dma_noncoherent_unmap_page,