Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5531964imu; Mon, 26 Nov 2018 01:38:38 -0800 (PST) X-Google-Smtp-Source: AJdET5fZPLxWTlQtFqaWsIfEwS2TCuaRzVuYjdsnHLmmtmeO8wQFUCHlKtG9HzcJcqkPtYAwEGkv X-Received: by 2002:a62:9683:: with SMTP id s3mr27056448pfk.60.1543225117965; Mon, 26 Nov 2018 01:38:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543225117; cv=none; d=google.com; s=arc-20160816; b=f/+9c/b6mHb0ntIBsl2Ud5evGtna0SO7cn3ObqHBpl1LQw9Hex5S5Wh/xKod56JDus 5lXsNa/JcxvBKdRdDTSp9ukBb6z/054FhgM0Ep8tQ4br4jpGOP3D/733SgaWjEZDzSVR CZc90K1epHsx1BU5cUCOdmczWV0zrnXApc8MqJHmevE/Bi+qRmsGMCalh4dOy78j6Va8 YNYgVMvf73WW4+FXIUgNoj70/imFwkFXrgY7ak+UN7y8QJSf9fkoy+lrKYFrf0BeHHe2 EvpfSTfMvivl681/9OWfG6D7Ij7VHloSOFANMfrb9MFy+H17ibEwNYjYwSUvYNM6LGgB lLvA== 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-disposition :user-agent:in-reply-to:mime-version:references:message-id:subject :cc:to:from:date; bh=3xGj9A1zHJi5d2tKna9Zqj2QwPI6uuNv5SS7rsZRxY8=; b=TFfjGZIWF1nb/SCFix55LXYHqfuvnfxBWAR/RsfV04MhX03CaVBBJvJo/NkMwVcuCV 5F+ny1b50Mh3kLpzWX9BJNOsAHTRfKdNIb5bkH002YXc6rdlaKS42mgzrdRvgZtI7x+t 38NWNMpmOrwFsgQ+4vgd4zhbol5e0cAzI9dWh/EyS/2lsdTaSMpE939dwL38kecYiqy8 m60lm0i5dy7HwKBgdQOH9jqayFj6lTdJQ4J7WkYcycjHL9bOBJYNnDzUU3DCPy2uQuCc PwiT3sec33VpokPmreM7MbInyHJsd8tui0xw3QTivJnrQMkMrmEImu3os3GvLJ7fU9lx OCHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b="Q/qC4P5Q"; 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 k18si45695382pfd.241.2018.11.26.01.38.22; Mon, 26 Nov 2018 01:38:37 -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="Q/qC4P5Q"; 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 S1726274AbeKZUaD (ORCPT + 99 others); Mon, 26 Nov 2018 15:30:03 -0500 Received: from hqemgate16.nvidia.com ([216.228.121.65]:11412 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726157AbeKZUaD (ORCPT ); Mon, 26 Nov 2018 15:30:03 -0500 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Mon, 26 Nov 2018 01:36:38 -0800 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Mon, 26 Nov 2018 01:36:29 -0800 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Mon, 26 Nov 2018 01:36:29 -0800 Received: from localhost (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 09:36:29 +0000 Date: Mon, 26 Nov 2018 10:36:26 +0100 From: Thierry Reding To: Tony Lindgren CC: Jon Hunter , Peter Ujfalusi , Belisko Marek , LKML , , "Dr. H. Nikolaus Schaller" , Laxman Dewangan Subject: Re: omap5 fixing palmas IRQ_TYPE_NONE warning leads to gpadc timeouts Message-ID: <20181126093625.GA10878@ulmo> 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> MIME-Version: 1.0 In-Reply-To: <20181123164827.GE53235@atomide.com> X-NVConfidentiality: public User-Agent: Mutt/1.10.1 (2018-07-13) X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL101.nvidia.com (172.20.187.10) To HQMAIL101.nvidia.com (172.20.187.10) Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua" Content-Disposition: inline DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1543224998; bh=3xGj9A1zHJi5d2tKna9Zqj2QwPI6uuNv5SS7rsZRxY8=; h=X-PGP-Universal:Date:From:To:CC:Subject:Message-ID:References: MIME-Version:In-Reply-To:X-NVConfidentiality:User-Agent: X-Originating-IP:X-ClientProxiedBy:Content-Type: Content-Disposition; b=Q/qC4P5QmfgsJ0L9qrgvJJCt34uKtaKnh4rEcg/IwjIYX4ERm1Gu+sTlGeormQzmV nO0fXCLUvJOM751U/ilUtISjqAPZZunx+ZwArunHei3mIbT9L8Fz6L22VPqjKpNGCL 4ZRmFNlmkefDXIFgF89WVRoubdSJpmVEla7UIJCl7kMuMe4ujxR1ImY+XJAQ674FKe rviYyOC52NxIouaSz9lerWNbGpOZSuF1MbJVDOjRmDfOpIea+dwVgg12H/lq1WWz6u uE9HliyiS4keMt1I1WK886YHMdWb48Y820GDU6aKvi9oDBB0fZzp9z1ZJT/K27eqY5 m3vV0UH6Lv1wQ== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 23, 2018 at 08:48:27AM -0800, 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. > >=20 > > Yes Tegra can invert the polarity of the PMIC interrupt. >=20 > 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? Yes, there's indeed an IP called PMC (Power-Management Controller) on Tegra. It has a special input that is usually wired up to the PMIC interrupt and a bit in the control register that configures the polarity of that interrupt. If the PMIC generates a low-active interrupt we usually set that bit to make sure it is properly sampled by the PMC. The symptoms of this being incorrectly configured is usually an interrupt storm on the PMIC interrupt, which I think typically results in the system not booting at all, or taking a very long time to boot because of that storm. > 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. Does somebody have access to the Palmas documentation? That should pretty clearly state what the default polarity is and what it changes to if you set the interrupt polarity bit. =46rom what you're saying it sounds like either the logic is the wrong way around in the Palmas MFD driver (and we correct it by switching it back to the correct polarity in the PMC) or that you'd need to find some way of inverting in on OMAP5. Thierry --SUOF0GtieIMvvwua Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAlv7vpcACgkQ3SOs138+ s6GBZBAAvMehEa8A+LGTqIFmDqN1oCIrXPtzxBKNQOXr1R1eR5VS2YCRcZQ0CW4e UEf+mDgJ+4/i3uEWcidyv6ILuFdy/RQoWvOVOAjeTGQiMkofC8PvetxMo693NXmD 7np9OHR5KUtU87+PkKojUM3SxzJ1ADlm28YMqF3SCqOEMvphXSxoOA3YIPpUttn6 dftMt88yxmXJM58KksnMjZZ2eM/EqBSvlGshJS+uWXQP8isK1KIQgOxx3SRqfIKP mBhhmhDNq54vqoaEpKcsPjuoqwbBKmAkSj6jahlQ7TGB6bjIMweshZgxWL+Zu4Gd UPehtHm4yWKqlHYa8kquTgahn3/z8pKr1fpdvvlCrqwXBOxQIOpUMZXqiqWoOipg urDxeVvM7y0Lic+8QfKOzg0eLysCyDJmkum3rE1ubcvVG6ql1vuWxRr8yr9geTC6 /k3Mb4gU55oWAlB7RUgrvkwOFoAiEwdWnI6aJGtJhiblimW+KV6pvJheAlzQ/BZv fwaq/vYLf+wkew17Y8oxt6b5RQTGz9Hr6Vpjr5rmaiFHB/6cCR0GWVyQFz83QO2p SetWlOnIr1QcJ5ieBbuFaY0ip3GagavB+28RDfcRVXF2lMfFQ4q9luf84B4h3Ffi BjGzfsZpEAlCRoL/o9AN/J441UaEryo2KF7dLDswY1Q1Eh9NEW8= =sb3s -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua--