[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230705115106.a4c314e8e177f6516bebda13@hugovil.com>
Date: Wed, 5 Jul 2023 11:51:06 -0400
From: Hugo Villeneuve <hugo@...ovil.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Fabio Estevam <festevam@...il.com>,
Nate Drude <Nate.D@...iscite.com>,
Pierluigi Passaro <pierluigi.p@...iscite.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>,
Hugo Villeneuve <hvilleneuve@...onoff.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: imx8mn-var-som-symphony: fix USB OTG
On Wed, 5 Jul 2023 17:44:05 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> wrote:
> On 05/07/2023 17:34, Hugo Villeneuve wrote:
> > On Wed, 5 Jul 2023 12:22:55 -0300
> > Fabio Estevam <festevam@...il.com> wrote:
> >
> >> Hi Hugo,
> >>
> >> On Wed, Jul 5, 2023 at 11:48 AM Hugo Villeneuve <hugo@...ovil.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?
>
> As I wrote, interrupt type cannot be none. What does it even mean "none"
> for your case?
Hi,
I have no idea why Variscite are using this IRQ type of NONE.
I can put IRQ_TYPE_EDGE_FALLING since I tested it and it works.
Hugo.
Powered by blists - more mailing lists