From: Tony Lindgren <tony@atomide.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Thierry Reding <treding@nvidia.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Belisko Marek <marek.belisko@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-omap@vger.kernel.org,
"Dr. H. Nikolaus Schaller" <hns@goldelico.com>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: omap5 fixing palmas IRQ_TYPE_NONE warning leads to gpadc timeouts
Date: Tue, 27 Nov 2018 10:17:46 -0800 [thread overview]
Message-ID: <20181127181746.GU53235@atomide.com> (raw)
In-Reply-To: <20181127175538.GS53235@atomide.com>
* Tony Lindgren <tony@atomide.com> [181127 17:55]:
> The only option that works for omap5 at palmas end is if
> PALMAS_POLARITY_CTRL_INT_POLARITY is cleared. Setting the SoC internal
> pulls does not make a difference, so I suspect there is either some
> unknown pull-up/pull-down configuration register in palmas, or there
> is an external pull resistor.
Remuxing the palmas interrupt to gpio_wk16 instead of sys_nirq1
makes the palmas interrupt work just fine configured with active-low
or active-high with the internal pulls. So palmas.c is doing the
right thing, and the issue configuring palmas interrupt active-high
with sys_nirq1 on omap5 is somewhere between omap wkupegen and GIC.
Regards,
Tony
next prev parent reply other threads:[~2018-11-27 18:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 16:37 omap5 fixing palmas IRQ_TYPE_NONE warning leads to gpadc timeouts Belisko Marek
2018-07-03 8:45 ` Tony Lindgren
2018-07-03 18:31 ` Belisko Marek
2018-11-13 18:06 ` Tony Lindgren
2018-11-14 17:03 ` Tony Lindgren
2018-11-14 17:26 ` Tony Lindgren
2018-11-19 10:18 ` Peter Ujfalusi
2018-11-19 10:18 ` Peter Ujfalusi
2018-11-19 16:19 ` Tony Lindgren
2018-11-19 17:14 ` Tony Lindgren
2018-11-20 11:14 ` Jon Hunter
2018-11-20 11:14 ` Jon Hunter
2018-11-23 16:48 ` Tony Lindgren
2018-11-26 9:36 ` Thierry Reding
2018-11-26 9:36 ` Thierry Reding
2018-11-26 9:49 ` Peter Ujfalusi
2018-11-26 9:49 ` Peter Ujfalusi
2018-11-26 10:25 ` Thierry Reding
2018-11-26 10:25 ` Thierry Reding
2018-11-26 19:32 ` Tony Lindgren
2018-11-26 20:17 ` Jon Hunter
2018-11-26 20:17 ` Jon Hunter
2018-11-27 17:55 ` Tony Lindgren
2018-11-27 18:17 ` Tony Lindgren [this message]
2018-11-26 10:13 ` Jon Hunter
2018-11-26 10:13 ` Jon Hunter
2018-11-20 12:22 ` Laxman Dewangan
2018-11-20 12:22 ` Laxman Dewangan
2018-11-26 10:14 ` Thierry Reding
2018-11-26 10:14 ` Thierry Reding
2018-11-26 19:14 ` Tony Lindgren
2018-11-26 19:19 ` Santosh Shilimkar
2018-11-27 18:03 ` Tony Lindgren
2018-11-20 7:36 ` Peter Ujfalusi
2018-11-20 7:36 ` Peter Ujfalusi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181127181746.GU53235@atomide.com \
--to=tony@atomide.com \
--cc=hns@goldelico.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=peter.ujfalusi@ti.com \
--cc=treding@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.