From: Hugo Villeneuve <hugo@hugovil.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Nate Drude <Nate.D@variscite.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Pierluigi Passaro <pierluigi.p@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" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: imx8mn-var-som-symphony: fix USB OTG
Date: Wed, 5 Jul 2023 11:34:19 -0400 [thread overview]
Message-ID: <20230705113419.183f686f47252abf3532fc9e@hugovil.com> (raw)
In-Reply-To: <CAOMZO5D_p3hf+HVHNAijEevJRpzwmyGPcoHjiapsOx_ddsoksg@mail.gmail.com>
On Wed, 5 Jul 2023 12:22:55 -0300
Fabio Estevam <festevam@gmail.com> wrote:
> Hi Hugo,
>
> On Wed, Jul 5, 2023 at 11:48 AM Hugo Villeneuve <hugo@hugovil.com> wrote:
>
> > Fabio: do we need to support both configurations in the Linux kernel
> > tree, and if yes how do you propose we do it?
>
> I would suggest supporting the new revision only.
Ok, no problem.
If we go back to my original patch, the changes in it, apart from the
interrupt, are still required to make USB OTG work (at least in host
mode, so that we can plug a USB key for example). Also looking at the
latest varigit changes, I have removed the "typec1_con:
connector" node (tested ok in host mode). I also added comments in the
DTS about the particular PTN5150 interrupt pin configurations.
Let me know if I can resubmit it, and if so can I leave the interrupt
property type to IRQ_TYPE_NONE?
Thank you,
Hugo.
next prev parent reply other threads:[~2023-07-05 15:34 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
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 [this message]
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=20230705113419.183f686f47252abf3532fc9e@hugovil.com \
--to=hugo@hugovil.com \
--cc=Nate.D@variscite.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=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®