[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2026010746-maker-oink-39fb@gregkh>
Date: Wed, 7 Jan 2026 08:25:00 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Praveen Talari <praveen.talari@....qualcomm.com>
Cc: Jiri Slaby <jirislaby@...nel.org>, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
bryan.odonoghue@...aro.org, dmitry.baryshkov@....qualcomm.com,
andersson@...nel.org, psodagud@...cinc.com, djaggi@...cinc.com,
quic_msavaliy@...cinc.com, quic_vtanuku@...cinc.com,
quic_arandive@...cinc.com, quic_shazhuss@...cinc.com,
quic_cchiluve@...cinc.com
Subject: Re: [PATCH v1] serial: qcom_geni: Fix BT failure regression on RB2
platform
On Wed, Jan 07, 2026 at 12:18:34PM +0530, Praveen Talari wrote:
> A regression in linux-next causes Bluetooth functionality to fail during
> bootup on the RB2 platform, preventing proper BT initialization. However,
> BT works correctly after bootup completes.
>
> The issue occurs when runtime PM is enabled and uart_add_one_port() is
> called before wakeup IRQ setup. The uart_add_one_port() call activates the
> device through runtime PM, which configures GPIOs to their default state.
> When wakeup IRQ registration happens afterward, it conflicts with these
> GPIO settings, causing state corruption that breaks Bluetooth
> functionality.
>
> Fix this by moving runtime PM enablement and uart_add_one_port() after
> wakeup IRQ registration, ensuring proper initialization order.
>
> Reported-by: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
> Closes:
> https://lore.kernel.org/all/20251110101043.2108414-4-praveen.talari@oss.qualcomm.com/
No line wrapping for tags please.
thanks,
greg k-h
Powered by blists - more mailing lists