Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4028596imm; Mon, 20 Aug 2018 08:38:26 -0700 (PDT) X-Google-Smtp-Source: AA+uWPyQ30n3j5a24TGMQ3MqOqVNr/GbZh9PvjJJVewh9iFumT0aJLoY6EG0/0UNALGHVGpe8dfG X-Received: by 2002:a17:902:50ec:: with SMTP id c41-v6mr46193058plj.269.1534779506646; Mon, 20 Aug 2018 08:38:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534779506; cv=none; d=google.com; s=arc-20160816; b=Oi53WpSEhHoe4U25qVh7hzzfnK8N+5zDOgZlwtlGuqEiMPe9B1V9mKRpqNO1gdVWeh yCoOV+9xO472bLZqPtMwMsiCpLqLYt9lIHG4MDgm4azZc/7fPxYtK2z2EtF9Ykxassyg zVbPQgbjP6TOFFSHHFbnnwMwJ58hI1WP7a7fszkT9cJhOU9t8Pm1GejQDZnefkIpq+ey O2g0Ml+KHJ5kHIaygUQMq8ToH+q8sElCSKC+kj8o0Q4UlpmRqgOhAb5ZNiYURrl0SW5c wibwKpR7ZUNCXWtPwukDshGsyMJZZeftS87qux7xLH8tMKvfuApKxrqtzNb8Deq2Oxgx xN/A== 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:organization:from:references:cc:to:subject :arc-authentication-results; bh=s8eNH4WVMxjwc9rl/DnNfG+IVJxAAMJp6qhRjguKZdo=; b=RX4RONHubD2masiba9oYwFSkmshxLGtWsGfQf5l3LaiDsfY4ohqsIoNzXfMYus7P3H ylCcanh+XL9JJGyPNcFhWm/zHOgsVZoPTXYZaU4Uu0Pv7xD35ZG+mGnopARG+6N2eiNH osQBnrCkNqp28AgWrh8Om7iN3AnpEeORMoGvUUjm47SuY583zMaV4e7ajwNPGE4xqsZ1 x9lGqFvKB33kqVCrHN5V14wbYgtpXJl37RVplTO8QbRb4W/1wyxCjTdssXuEwWT/2G26 OQnjsanvw5EYoC00LUJrAQCO2qgtLBStdcT4bhoVKpgR7IC2IYiA5Zmf9RyQUDLj9Hs6 lLgQ== 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 m28-v6si8375623pgd.358.2018.08.20.08.38.11; Mon, 20 Aug 2018 08:38:26 -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 S1727454AbeHTSuh (ORCPT + 99 others); Mon, 20 Aug 2018 14:50:37 -0400 Received: from foss.arm.com ([217.140.101.70]:39438 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726715AbeHTSug (ORCPT ); Mon, 20 Aug 2018 14:50:36 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id B959B18A; Mon, 20 Aug 2018 08:34:30 -0700 (PDT) Received: from [10.4.13.119] (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9E8543F24A; Mon, 20 Aug 2018 08:34:28 -0700 (PDT) Subject: Re: [PATCH RESEND v1 2/5] drivers: pinctrl: msm: enable PDC interrupt only during suspend To: Lina Iyer Cc: bjorn.andersson@linaro.org, sboyd@kernel.org, evgreen@chromium.org, linus.walleij@linaro.org, rplsssn@codeaurora.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, rnayak@codeaurora.org, devicetree@vger.kernel.org, andy.gross@linaro.org, dianders@chromium.org References: <20180817191026.32245-1-ilina@codeaurora.org> <20180817191026.32245-3-ilina@codeaurora.org> <86a7pjq0l1.wl-marc.zyngier@arm.com> <20180820152629.GR5081@codeaurora.org> From: Marc Zyngier Organization: ARM Ltd Message-ID: <047d37fb-1011-0650-6517-e6052ba47a18@arm.com> Date: Mon, 20 Aug 2018 16:34:27 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180820152629.GR5081@codeaurora.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/08/18 16:26, Lina Iyer wrote: > On Sat, Aug 18 2018 at 07:13 -0600, Marc Zyngier wrote: >> Hi Lina, >> >> On Fri, 17 Aug 2018 20:10:23 +0100, >> Lina Iyer wrote: [...] >>> @@ -920,6 +928,8 @@ static int msm_gpio_pdc_pin_request(struct irq_data *d) >>> } >>> >>> irq_set_handler_data(d->irq, irq_get_irq_data(irq)); >>> + irq_set_handler_data(irq, d); >>> + irq_set_status_flags(irq, IRQ_DISABLE_UNLAZY); >> >> Could you explain what this is trying to do? I'm trying to understand >> this code, but this function isn't in 4.18... >> > Oh, I have been able to test only on 4.14 so far. The flag does seem to > exist at least, I didn't get a compiler error. > > I read this in kernel/irq/chip.c - > > If the interrupt chip does not implement the irq_disable callback, > a driver can disable the lazy approach for a particular irq line by > calling 'irq_set_status_flags(irq, IRQ_DISABLE_UNLAZY)'. This can > be used for devices which cannot disable the interrupt at the > device level under certain circumstances and have to use > disable_irq[_nosync] instead. > > And interpreted this as something that this would prevent 'relaxed' > disable. I am enabling and disabling the IRQ in suspend path, that I > thought this would help avoid issues caused by late disable. Am I > mistaken? Sorry, I wasn't clear enough. I'm talking about what you're trying to do in this particular function (msm_gpio_pdc_pin_request), which doesn't exist in 4.18. Short of having a bit of context, I can hardly review this. Thanks, M. -- Jazz is not dead. It just smells funny...