[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181127180318.GT53235@atomide.com>
Date: Tue, 27 Nov 2018 10:03:18 -0800
From: Tony Lindgren <tony@...mide.com>
To: Thierry Reding <treding@...dia.com>
Cc: Peter Ujfalusi <peter.ujfalusi@...com>,
Belisko Marek <marek.belisko@...il.com>,
LKML <linux-kernel@...r.kernel.org>, linux-omap@...r.kernel.org,
"Dr. H. Nikolaus Schaller" <hns@...delico.com>,
Laxman Dewangan <ldewangan@...dia.com>,
Jon Hunter <jonathanh@...dia.com>
Subject: Re: omap5 fixing palmas IRQ_TYPE_NONE warning leads to gpadc timeouts
* Thierry Reding <treding@...dia.com> [181126 10:14]:
> I'm not sure we need to go to those lengths. As far as I'm concerned, if
> it turns out that we've inverted the logic for Tegra114, that's a bug in
> the DTS and we should fix it along with the driver to remove the double
> negation. I don't think this would be causing any problems with existing
> DTBs since, as far as I can tell, the TPS65913 is only used on Dalmore
> (which was never publicly available) or Roth and TN7, neither of which I
> think anyone ever ran upstream Linux on other than maybe Alex who added
> the support. In all of the above cases, there is no problem updating the
> DTB since it's all loaded either from eMMC or from an Android boot image
> as far as I understand.
As Jon explained, Tegra PMC inverts the Palmas interrupt twice, so it
gets inverted total three times. So no need to do anything right now,
I'll just change the omap5 PMIC interrupt to use a GPIO instead like
dra7 is already doing.
Thanks everybody for checking the use on Tegra.
Regards,
Tony
Powered by blists - more mailing lists