Re: [PATCH v2] serial: qcom_geni: Fix BT failure regression on RB2 platform

[Praveen Talari]

Hi Dmistry,

Thank you for your inputs.

On 1/7/2026 11:11 PM, Dmitry Baryshkov wrote:
> On Wed, Jan 07, 2026 at 09:56:10PM +0530, Praveen Talari wrote:
> > Commit 10904d725f6e ("serial: qcom-geni: Enable PM runtime for serial
> > driver") caused BT init 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 the "qup_x"
> > pinmux function during runtime resume. When wakeup IRQ registration
> > happens afterward using dev_pm_set_dedicated_wake_irq(), these GPIOs
> > are reset back to the "gpio" pinmux function, which impacts the RX GPIO
> > and leads to Bluetooth failures.
> >
> > Fix this by ensuring wakeup IRQ setup is completed before calling
> > uart_add_one_port() to prevent the pinmux function conflict.
> >
> > Tested-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxxxxxxxx>
> > Reported-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxxxxxxxx>
> > Closes: https://lore.kernel.org/all/20251110101043.2108414-4-praveen.talari@xxxxxxxxxxxxxxxx/
> > Fixes: 10904d725f6e ("serial: qcom-geni: Enable PM runtime for serial driver")
>
> The order of tags is odd. How can it be tested before being reported?
> I'd suggest the following order:
> - Fixes
> - Reported-by
> - Closes
> - Tested-by
> - Reviewed-by

Thank you for your inputs. Will do it in next patch.

Thanks,
Praveen Talari
> > Signed-off-by: Praveen Talari <praveen.talari@xxxxxxxxxxxxxxxx>
> > ---
> > v1 -> v2
> > - Updated commit text.
> > - Added Tested-by in commit text
> > ---
> >   drivers/tty/serial/qcom_geni_serial.c | 12 ++++++------
> >   1 file changed, 6 insertions(+), 6 deletions(-)
>
> With the tag order fixed:
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxxxxxxxx>