Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5567279imu; Mon, 26 Nov 2018 02:15:14 -0800 (PST) X-Google-Smtp-Source: AFSGD/XqC7fc7Hlkov/h8q7UdD6datp+P62G5Z96LHfIpHFzs9ycIQomJwtwGYZmbffZBxGVmkhj X-Received: by 2002:a17:902:29ab:: with SMTP id h40mr26888315plb.238.1543227314561; Mon, 26 Nov 2018 02:15:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543227314; cv=none; d=google.com; s=arc-20160816; b=ooLnY3GcjXgjUxg1V6//jJDWi+v4GlqhsgymJ3Vei0BJhPC/jvT1QPYV2m+76q//K1 z7I1hi7tmiVHrKvuf5kpYhT/gMHPc3E6B2TPYR6hPgjqGvofTUG1+YXMrGG5yO4v0ERk v4F8TECk1TLlJWcCpUjVuP1ckOTb1qbRZfumbfamQIt5yI281DfuAkh3sJiWjnu18bqg 2RjkiFEuWz2KlRuW6IcTMgiKaZxWp+rp1hRVtKhj3L5cqQNTxGUAHJmayxPJOjvNCBBd wkiulK5qnGe15XU8FZB737kYVtUpg+yRjw4Mh60unNSljbv9gjQOIWb3N4FeZLmsmEtm G31A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=4e269GsUd7HKpDB9juxIiM2TtLZaEZ0ZpaBeZtzBYwU=; b=o7m/hGDVObcSJzwMsCy7QIoT7Yn2peSWnMYnxDfB685iYATaNfhwHkmS0dBRBxKgF4 herD0Uue/7I2kDvRN1r3MxiMF8wjy7nHw2MDi/4dKRREijLprx1RwKJap5KFyQl79yPa S3goPJSIZyZbp1pzKpg4BLs10HOewgqQyUC1k6A6ynjoJygHPxgklok9TI6dcbiStgT7 FSyExnF809UfSw2C+Ep6ssUJEK8HjKzy9yrWbmmd5l7WBki/RrAbyPaEKQ80cIUkvzm2 mSRUQTUHMTfKUUr4y9uER/Geq8JDbTcz8u0eUmEHsyF/afqH9lQBGnF6IWwSgwMe2G+V pmDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=bweiKNkv; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c11si54674285pgh.18.2018.11.26.02.14.59; Mon, 26 Nov 2018 02:15:14 -0800 (PST) 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; dkim=pass header.i=@nvidia.com header.s=n1 header.b=bweiKNkv; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726398AbeKZVHk (ORCPT + 99 others); Mon, 26 Nov 2018 16:07:40 -0500 Received: from hqemgate14.nvidia.com ([216.228.121.143]:14620 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726176AbeKZVHk (ORCPT ); Mon, 26 Nov 2018 16:07:40 -0500 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate14.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Mon, 26 Nov 2018 02:14:04 -0800 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Mon, 26 Nov 2018 02:14:02 -0800 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Mon, 26 Nov 2018 02:14:02 -0800 Received: from [10.26.11.165] (10.124.1.5) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 26 Nov 2018 10:13:59 +0000 Subject: Re: omap5 fixing palmas IRQ_TYPE_NONE warning leads to gpadc timeouts To: Tony Lindgren CC: Peter Ujfalusi , Belisko Marek , LKML , , "Dr. H. Nikolaus Schaller" , Laxman Dewangan , Thierry Reding References: <20180703084516.GT112168@atomide.com> <20181113180656.GE53235@atomide.com> <46d271b2-35d3-6353-c530-3292cdac53ab@ti.com> <20181119161906.GP53235@atomide.com> <20181119171406.GQ53235@atomide.com> <725df8e7-4aff-3751-d0b0-809b89e882e5@nvidia.com> <20181123164827.GE53235@atomide.com> From: Jon Hunter Message-ID: <7d433094-4797-9bff-ba7b-325a706882c6@nvidia.com> Date: Mon, 26 Nov 2018 10:13:56 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20181123164827.GE53235@atomide.com> X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL108.nvidia.com (172.18.146.13) To HQMAIL101.nvidia.com (172.20.187.10) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1543227244; bh=4e269GsUd7HKpDB9juxIiM2TtLZaEZ0ZpaBeZtzBYwU=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=bweiKNkvzlxv6SjYR4JySVMukfuRkk0G2cBADiaaKEkxePGJAIe1T2TomMZlwNsR2 iOS/nrYgDhYYgmNb0wc4xsW2bCEUIQt8LoVuG2be6PblaTQtDaHViBYXwgLBTfeVzY 8Yh/QJaeFciKUYyD0TybUu6moJpDUIb0bgBeO30CFv8UByELgwvtnww3fP4XvjqySn OIwuKy6THPKeJf+TtBUREuB3XzGSimdLEQmjgl73/J5CzJWkYGb4gS4m0t41NpxWCt 9UnJ0m2RJhXXzOE1KaRlzQTjm3AIAAdyj+jDsdEmUQ9MP0m+TF1U3xEvtiBnU0mYUe WFjBy1prtQ7kg== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23/11/2018 16:48, Tony Lindgren wrote: > * Jon Hunter [181120 11:14]: >> On 19/11/2018 17:14, Tony Lindgren wrote: >>> Well so commit 7e9d474954f4 ("ARM: tegra: Correct polarity for >>> Tegra114 PMIC interrupt") states that tegra114 inverts the >>> polarity of the PMIC interrupt. So adding Jon and Thierry to Cc. >> >> Yes Tegra can invert the polarity of the PMIC interrupt. > > So is there some IP on Tegra called "Tegra PMC" that is > inverting the interrupt? Or is the "Tegra PMC" that commit > 7e9d474954f4 mentions just the palmas configuration for > inverting the interrupt? > > The problem I'm having is With omap5 where I can only get the > PMIC interrupts working with IRQ_TYPE_LEVEL_HIGH if > PALMAS_POLARITY_CTRL_INT_POLARITY is not set unlike for > Tegra. I see what you are saying and so technically we should not need to invert with the Tegra PMC as well. This PMIC is used on the Tegra114 Dalmore board which was where I saw the original problem. However, I have not tested this board for a while (and not part of our current nightly testing). Do you know if something has changed recently? Cheers Jon -- nvpublic