linux-kernel - Re: [PATCH v1] serial: qcom_geni: Fix BT failure regression on RB2 platform

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <36d8fb98-562a-43dc-8b47-b4f6d29475f1@oss.qualcomm.com>
Date: Wed, 7 Jan 2026 14:54:13 +0530
From: Praveen Talari <praveen.talari@....qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        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, 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

Hi

On 1/7/2026 12:52 PM, Dmitry Baryshkov wrote:
> On Wed, 7 Jan 2026 at 09:06, Praveen Talari
> <praveen.talari@....qualcomm.com> wrote:
>>
>> Hi Dmistry,
>>
>> On 1/7/2026 12:24 PM, Dmitry Baryshkov wrote:
>>> On Wed, 7 Jan 2026 at 08:48, Praveen Talari
>>> <praveen.talari@....qualcomm.com> wrote:
>>>>
>>>> A regression in linux-next causes Bluetooth functionality to fail during
>>>
>>> linux-next is an ephemeral thing. Please reference the exact commit.
>>>
>>>> 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.
>>>
>>> How does it "conflict with GPIO settings", what is "state corruption"?
>>
>> I mean the issue occurs because the GPIO state is being altered during
>> the wakeup source registration process..
> 
> Altered how?

During the runtime resume of devices, GPIOs are configured to QUP mode. 
However, when registering the wakeup IRQ using 
dev_pm_set_dedicated_wake_irq(), these GPIOs are reset back to FUNC 
mode, which impacts the RX GPIO and leads to Bluetooth failures

Thanks,
Praveen
> 
>>
>> Thanks,
>> Praveen Talari
>>>
>>>
>>>>
>>>> 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/
>>>> Fixes: 10904d725f6e ("serial: qcom-geni: Enable PM runtime for serial driver")
>>>> Signed-off-by: Praveen Talari <praveen.talari@....qualcomm.com>
>>>> ---
>>>>    drivers/tty/serial/qcom_geni_serial.c | 12 ++++++------
>>>>    1 file changed, 6 insertions(+), 6 deletions(-)
>>>>
>>>
>>> Tested-by: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
>>>
>>>
>>
> 
>