Received: by 10.192.165.148 with SMTP id m20csp840384imm; Fri, 27 Apr 2018 08:20:04 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqSbFWR9zPtBQql4hVN8RcZJjwhPIpNxOemKvhG+jSh4GHfERrBT7hKUaekI8qRI/GOvuEE X-Received: by 10.98.35.215 with SMTP id q84mr2571096pfj.31.1524842404298; Fri, 27 Apr 2018 08:20:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524842404; cv=none; d=google.com; s=arc-20160816; b=Apjalu54Lk4Kksuvl/Nk/V6rBHEidLgL7Da84VO3/BStke2xPiquXYgYx9UXyJh14E r5ZMY1Vca3SIS9oKFJAc5+qKx0eLnbXcXJKoNMDI3/hlAHiox+TZjFELa00FtM1AfJ3O u1lkvH0KiNqjBPOT/S3h7TN8Wd6tRgCk9lBPVIzdmPSP9QfBOAC4fKLuYFsw9OKumMni aFNSFrx+VdA34hbca73qcgFCxgHHMk6kfYXZrYdCyv9+HpUPkbYORoAot68GbIV32jtc Z6udc7f/h9CM4VTJCqLGy04ZONvGce81ionc1hXQn7OEIHVHWenkhmO7+5ZCy30HB0rK 10vg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=r4ky9C2kc/HAJDIWTb4FJ0yX+q6Fu8GWWoq1rozoe/A=; b=JSHhGYQ00LlvVT8tMFfgz/FuNcgThWxbN5t8KhDvoiBbVPEyeZGbbQR+ap1/kIc9DT T50JNqVfmcYzWWnDuxE/JvNzlAhDeTdoauRlkZU+dVzK/8bMxKozNu7dMdjpfn/yLe5l 4XfucvBjTqK3AZkNLo6lUJYiW0LSPCZJKk3+Jb6fcXUbtfNrxHFBN8DWRrLjO2oaMd5W Zani5acbYoeBMd+y43xKh6KGA8gbo27Ji2YV6+PJ1O0a3niwkJHG2Hb7Lx05UwF1otva Oe4XZ7aWtNUL9h/DbQVLDHov1Dwa1V3TQjQheiAUqNH7Qvb8toDTHEcJ36pQzxup4NE7 1PNA== 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 z24-v6si1417730pge.161.2018.04.27.08.19.50; Fri, 27 Apr 2018 08:20:04 -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 S933622AbeD0PSn (ORCPT + 99 others); Fri, 27 Apr 2018 11:18:43 -0400 Received: from www381.your-server.de ([78.46.137.84]:42907 "EHLO www381.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933111AbeD0PSk (ORCPT ); Fri, 27 Apr 2018 11:18:40 -0400 Received: from [78.46.172.3] (helo=sslproxy06.your-server.de) by www381.your-server.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85_2) (envelope-from ) id 1fC58u-00072y-2r; Fri, 27 Apr 2018 17:18:36 +0200 Received: from [2003:86:2c44:e800:8200:bff:fe9b:6612] by sslproxy06.your-server.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1fC58q-000HPn-Tc; Fri, 27 Apr 2018 17:18:32 +0200 Subject: Re: [PATCH v2] dmaengine: axi-dmac: Request IRQ with IRQF_SHARED To: Moritz Fischer , Vinod Koul Cc: Linux Kernel Mailing List , dmaengine@vger.kernel.org, dan.j.williams@intel.com References: <20180426174000.12008-1-mdf@kernel.org> <20180427051115.GX6014@localhost> <748ffc14-de12-c11e-eb12-65c599fe5f4e@metafoo.de> <20180427070830.GC6014@localhost> From: Lars-Peter Clausen Message-ID: <716956a2-a4f4-9cbd-8761-8db477f1dfc0@metafoo.de> Date: Fri, 27 Apr 2018 17:18:29 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Authenticated-Sender: lars@metafoo.de X-Virus-Scanned: Clear (ClamAV 0.99.3/24518/Fri Apr 27 14:29:17 2018) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/27/2018 05:15 PM, Moritz Fischer wrote: > Hi Vinod, > > On Fri, Apr 27, 2018 at 12:08 AM, Vinod Koul wrote: >> On Fri, Apr 27, 2018 at 08:53:39AM +0200, Lars-Peter Clausen wrote: >>> On 04/27/2018 07:11 AM, Vinod Koul wrote: >>>> On Thu, Apr 26, 2018 at 10:40:00AM -0700, Moritz Fischer wrote: >>>>> Request IRQ with IRQF_SHARED flag. This works since the interrupt >>>>> handler already checks if there is an actual IRQ pending and returns >>>>> IRQ_NONE otherwise. >>>> >>>> hmmm what are we trying to fix here? Is your device on a shared line or not? >>> >>> IRQF_SHARED does not mean that the IRQ is on a shared line. It means that >>> the driver can handle it if the IRQ is on a shared line. Since the driver >>> can handle it setting the flag is a good idea since this enables usecases >>> where the line is shared. >> >> Yes that is correct indeed, but what is the motivation for the change. >> >> If you never expect this to be in shared environment why to do this? >> Sorry but "it works" is not a good enough reason for this change, to enable >> usecases where the line is shared is a good reason :) > > Remember, this is an FPGA soft core. I happen to have a design [1] where it > is hooked up with multiple of them on one IRQ line, so to make this work, > I need this change. I think what Vinod is asking for is a change to the commit message saying that "this change enables the driver to be used with devices where the interrupt line is shared".