[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5AZiuEAh6nJB8Oub83At6bsvLhzOhsT_yOniZSucrAUMQ@mail.gmail.com>
Date: Tue, 4 Jul 2023 20:00:13 -0300
From: Fabio Estevam <festevam@...il.com>
To: Hugo Villeneuve <hugo@...ovil.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Pierluigi Passaro <pierluigi.p@...iscite.com>,
Nate Drude <nate.d@...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, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8mn-var-som-symphony: fix USB OTG
On Tue, Jul 4, 2023 at 6:50 PM Fabio Estevam <festevam@...il.com> wrote:
>
> On Tue, Jul 4, 2023 at 6:28 PM Hugo Villeneuve <hugo@...ovil.com> wrote:
>
> > 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.
>
> Now I looked at the schematics and you are right.
>
> In this case, GPIO1_11 should not be represented as irq then.
Variscite added an "irq-is-id-quirk" property on their tree to handle this:
https://github.com/varigit/linux-imx/commit/fbe6aa2a9c014fdb10b29a715a1be695dac60828
Powered by blists - more mailing lists