From: "Alvin Šipraga" <alvin@pqrs.dk>
To: Advait Dhamorikar <advaitd@mechasystems.com>
Cc: myungjoo.ham@samsung.com, cw00.choi@samsung.com,
linux-kernel@vger.kernel.org, alsi@bang-olufsen.dk,
gregkh@linuxfoundation.org, marex@denx.de,
heikki.krogerus@linux.intel.com
Subject: Re: [PATCH] extcon: usbc-tusb320: always rewrite REG9 to deassert INT_N
Date: Wed, 29 Jul 2026 13:28:02 +0200 [thread overview]
Message-ID: <amnhB-4wv24eE0CR@pqrs.dk> (raw)
In-Reply-To: <CAAPs2HTxDi3V8+EiG2=SujGaGCXPZMeYCQ8F6vWbt-HJKiKtVQ@mail.gmail.com>
Hi Advait,
On Wed, Jul 29, 2026 at 04:38:52PM +0530, Advait Dhamorikar wrote:
> Hi Alvin,
>
> Thanks for taking a look.
>
> > Can you say a bit more about your hardware?
>
> This is on an NXP i.MX8MP based board using a TUSB320 connected over I²C.
> The INT_N signal is connected to a GPIO configured as a level-low interrupt.
(I think we agree your patch is wrong, so I cut the rest of your reply)
[snip]
> I'm trying to understand why the hardware presents an asserted
> INT_N while REG9 reports no pending interrupt.
The INT_N signal is an open-drain output, so you need an external
pull-up resistor on the line. The TUSB320 will not drive it high when
there is no interrupt. Perhaps that's the problem?
If you have a pull-up resistor, check the behaviour when you hold the
TUSB320 in reset (use EN_N signal or power it off). If it's still low
then it's not the TUSB320 that's the problem.
If you have some kind of measuring tool (oscilloscope/etc.) it will be
more meaningful to probe the physical line than to listen to what Linux
or /proc/interrupts is telling you.
Hope that helps.
Kind regards,
Alvin
prev parent reply other threads:[~2026-07-29 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 15:37 Advait Dhamorikar
2026-07-29 7:27 ` Alvin Šipraga
2026-07-29 11:08 ` Advait Dhamorikar
2026-07-29 11:28 ` Alvin Šipraga [this message]
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=amnhB-4wv24eE0CR@pqrs.dk \
--to=alvin@pqrs.dk \
--cc=advaitd@mechasystems.com \
--cc=alsi@bang-olufsen.dk \
--cc=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=myungjoo.ham@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®