From: Hugo Villeneuve <hugo@hugovil.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Pierluigi Passaro <pierluigi.p@variscite.com>,
Nate Drude <nate.d@variscite.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8mn-var-som-symphony: fix USB OTG
Date: Tue, 4 Jul 2023 17:28:01 -0400 [thread overview]
Message-ID: <20230704172801.f11422b3f947c625f53af871@hugovil.com> (raw)
In-Reply-To: <CAOMZO5BNaQVMKbxU9rc5zOBwv9c+HayLnkjqrSgPKgMGzQ585A@mail.gmail.com>
On Tue, 4 Jul 2023 18:02:53 -0300
Fabio Estevam <festevam@gmail.com> wrote:
> Hi Hugo,
>
> On Tue, Jul 4, 2023 at 5:41 PM Hugo Villeneuve <hugo@hugovil.com> wrote:
>
> > Hi Fabio,
> > with interrupts = <11 IRQ_TYPE_LEVEL_LOW>, USB OTG doesn't work.
>
> PTN5150 datasheet says:
>
> "Any changes in the attach/detach events or Rp current source changes
> will trigger INTB pin to go LOW."
Hi Fabio,
it is important to remember that on this board, like I explained
before, the INTB pin is not connected to anything.
It is only the ID pin (9) that is connected to the GPIO1_11 pin.
> What about: interrupts = <11 IRQ_TYPE_EDGE_FALLING>; ?
With this setting, USB OTG works:
$ dmesg | grep 5150
[ 4.833529] ptn5150 1-003d: No VBUS GPIO, ignoring VBUS control
[ 4.839972] ptn5150 1-003d: DEBUG_IRQ: i2c->irq: 42
[ 4.874173] ptn5150 1-003d: DEBUG_IRQ: error in usb_role_switch_get()
[ 4.896822] ptn5150 1-003d: No VBUS GPIO, ignoring VBUS control
[ 4.902905] ptn5150 1-003d: DEBUG_IRQ: i2c->irq: 42
[ 4.911190] ptn5150 1-003d: DEBUG_IRQ: error in usb_role_switch_get()
[ 4.918462] ptn5150 1-003d: No VBUS GPIO, ignoring VBUS control
[ 4.926197] ptn5150 1-003d: DEBUG_IRQ: i2c->irq: 42
[ 4.935210] ptn5150 1-003d: DEBUG_IRQ: error in usb_role_switch_get()
[ 4.947673] ptn5150 1-003d: No VBUS GPIO, ignoring VBUS control
[ 4.953771] ptn5150 1-003d: DEBUG_IRQ: i2c->irq: 42
[ 4.961104] ptn5150 1-003d: DEBUG_IRQ: error in usb_role_switch_get()
[ 5.052165] ptn5150 1-003d: No VBUS GPIO, ignoring VBUS control
[ 5.058234] ptn5150 1-003d: DEBUG_IRQ: i2c->irq: 42
[ 5.064632] ptn5150 1-003d: DEBUG_IRQ: error in usb_role_switch_get()
[ 5.096452] ptn5150 1-003d: No VBUS GPIO, ignoring VBUS control
[ 5.102578] ptn5150 1-003d: DEBUG_IRQ: i2c->irq: 42
[ 5.114959] ptn5150 1-003d: DEBUG_IRQ: error in usb_role_switch_get()
[ 5.187060] ptn5150 1-003d: No VBUS GPIO, ignoring VBUS control
[ 5.193243] ptn5150 1-003d: DEBUG_IRQ: i2c->irq: 42
[ 5.206235] ptn5150 1-003d: DEBUG_IRQ: probe done
> Also, please add a pullup to the GPIO1_11 pad.
There is already an external 10K pull-up resistor (R88) to +3.3V
on GPIO1_11 pin...
Hugo.
next prev parent reply other threads:[~2023-07-04 21:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 15:02 Hugo Villeneuve
2023-07-04 15:08 ` Krzysztof Kozlowski
2023-07-04 15:31 ` Hugo Villeneuve
2023-07-04 16:20 ` Krzysztof Kozlowski
2023-07-04 16:33 ` Fabio Estevam
2023-07-04 16:55 ` Hugo Villeneuve
2023-07-04 17:02 ` Hugo Villeneuve
2023-07-04 18:04 ` Fabio Estevam
2023-07-04 20:41 ` Hugo Villeneuve
2023-07-04 21:02 ` Fabio Estevam
2023-07-04 21:28 ` Hugo Villeneuve [this message]
2023-07-04 21:50 ` Fabio Estevam
2023-07-04 23:00 ` Fabio Estevam
2023-07-05 13:35 ` Hugo Villeneuve
2023-07-05 13:42 ` Nate Drude
2023-07-05 13:49 ` Fabio Estevam
2023-07-05 14:25 ` Hugo Villeneuve
2023-07-05 14:31 ` Nate Drude
2023-07-05 14:48 ` Hugo Villeneuve
2023-07-05 15:22 ` Fabio Estevam
2023-07-05 15:34 ` Hugo Villeneuve
2023-07-05 15:44 ` Krzysztof Kozlowski
2023-07-05 15:51 ` Hugo Villeneuve
2023-07-05 15:54 ` Krzysztof Kozlowski
2023-07-05 15:57 ` Hugo Villeneuve
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=20230704172801.f11422b3f947c625f53af871@hugovil.com \
--to=hugo@hugovil.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hvilleneuve@dimonoff.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nate.d@variscite.com \
--cc=pierluigi.p@variscite.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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®