[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <173630239533.95965.17986968259395887798.b4-ty@kernel.org>
Date: Tue, 7 Jan 2025 20:13:12 -0600
From: Bjorn Andersson <andersson@...nel.org>
To: Konrad Dybcio <konradybcio@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Sibi Sankar <quic_sibis@...cinc.com>,
Rajendra Nayak <quic_rjendra@...cinc.com>,
Abel Vesa <abel.vesa@...aro.org>
Cc: Johan Hovold <johan@...nel.org>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: x1e80100: Fix usb_2 controller interrupts
On Tue, 07 Jan 2025 15:15:16 +0200, Abel Vesa wrote:
> Back when the CRD support was brought up, the usb_2 controller didn't
> have anything connected to it in order to test it properly, so it was
> never enabled.
>
> On the Lenovo ThinkPad T14s, the usb_2 controller has the fingerprint
> controller connected to it. So enabling it, proved that the interrupts
> lines were wrong from the start.
>
> [...]
Applied, thanks!
[1/1] arm64: dts: qcom: x1e80100: Fix usb_2 controller interrupts
commit: 680421056216efe727ff4ed48f481691d5873b9e
Best regards,
--
Bjorn Andersson <andersson@...nel.org>
Powered by blists - more mailing lists