Received: by 10.192.165.148 with SMTP id m20csp375491imm; Thu, 26 Apr 2018 23:55:10 -0700 (PDT) X-Google-Smtp-Source: AB8JxZptclVJ2dbwUfqNKPCYmtHTd6G3hHoiVeG2ykLfYlgBYf53vf6UDEm3B5MRFol+UYf88dHc X-Received: by 2002:a17:902:7283:: with SMTP id d3-v6mr1163661pll.308.1524812110602; Thu, 26 Apr 2018 23:55:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524812110; cv=none; d=google.com; s=arc-20160816; b=MlZayOB50VfwqGNmu2+FR3fiHK39+M6VVhotI/4Fz4yn9Fz/E9/Ne7pJGZNzmBZMyL 1t2Av4lH/IcSqgob7C+A50zOkZAJaCxzRyVeuHD4Fzvcj7nRY4dhWTSfe4u7T9Amu3hI pP2EvnodVBBfZ8MCUBYP4LPcg25k0YdCyrHzU5Itk6DuDaRv/wciarL2nSz0CxaHCQ6p A7axzg8dcAhi21p24uqxqhcKdEArymp8Vrc0/ZyGRwK7fp5gDWLzW6LHIcSrzzzIUXSD XN0Ea2vyaVIol+ozjGUByazrrm3MTmIjIi3++Pzv+fCQxiUWw9Y4K54MEsoagQPjtQq+ jzug== 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=EliIghTv44slCvaiycgQkRkUlLeKHQ7xoQnfaCHWwM0=; b=Ebg5LAfKnIRnbbvDulAx20irzcNeoyiGok9JwbE0CIGLZ09JYiYKhewLDKjuEt6Ug6 S0GUK6Wlyl1jTubu9KdOxt5/3WKfE3PfyCCAQy9SgJ2lHlEPRBxA2xYkU9XZPedZetwk SOc6JR7lbtGZVPSDP0ksLQa9LArLt6fVXzdyRHywDpb55oHV8Eizw+dxINCuCNWwfTPM lnzK6qeFZIUhXWOk25L5+v6kXXMj4g3PtpBYIrd9TMkEyAz1Ljy8BrPF89h+Nxons055 L5aFrs4fs5kHYmmQCvfjTREFvcMf0PLoXthdGMeC39GDI22wJ0miYC2NirYYBElG/5rZ lNNA== 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 b123-v6si684529pgc.14.2018.04.26.23.54.56; Thu, 26 Apr 2018 23:55:10 -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 S1757464AbeD0Gxw (ORCPT + 99 others); Fri, 27 Apr 2018 02:53:52 -0400 Received: from www381.your-server.de ([78.46.137.84]:42786 "EHLO www381.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757381AbeD0Gxv (ORCPT ); Fri, 27 Apr 2018 02:53:51 -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 1fBxGM-0001gb-8j; Fri, 27 Apr 2018 08:53:46 +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 1fBxGJ-000Ks3-2u; Fri, 27 Apr 2018 08:53:43 +0200 Subject: Re: [PATCH v2] dmaengine: axi-dmac: Request IRQ with IRQF_SHARED To: Vinod Koul , Moritz Fischer Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org, dan.j.williams@intel.com References: <20180426174000.12008-1-mdf@kernel.org> <20180427051115.GX6014@localhost> From: Lars-Peter Clausen Message-ID: <748ffc14-de12-c11e-eb12-65c599fe5f4e@metafoo.de> Date: Fri, 27 Apr 2018 08:53:39 +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: <20180427051115.GX6014@localhost> 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/24517/Fri Apr 27 06:24:46 2018) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > >> >> Acked-by: Lars-Peter Clausen >> Signed-off-by: Moritz Fischer >> --- >> Changes from v1: >> - Added Lars' Acked-by >> - Dropped patch [1/2] and changed accordingly >> --- >> drivers/dma/dma-axi-dmac.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/drivers/dma/dma-axi-dmac.c b/drivers/dma/dma-axi-dmac.c >> index 2419fe524daa..15b2453d2647 100644 >> --- a/drivers/dma/dma-axi-dmac.c >> +++ b/drivers/dma/dma-axi-dmac.c >> @@ -687,7 +687,7 @@ static int axi_dmac_probe(struct platform_device *pdev) >> if (ret) >> goto err_unregister_device; >> >> - ret = request_irq(dmac->irq, axi_dmac_interrupt_handler, 0, >> + ret = request_irq(dmac->irq, axi_dmac_interrupt_handler, IRQF_SHARED, >> dev_name(&pdev->dev), dmac); >> if (ret) >> goto err_unregister_of; >> -- >> 2.17.0 >> >