From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com [205.220.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 91217327C08 for ; Wed, 7 Jan 2026 14:08:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.180.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767794901; cv=none; b=SFTjixu2+/lQA0qyK9D3ab4HvDRRpyNbi6Espvy56PQeeDI/L33xDk5Wc2oE8PAnv4VOor+B0+sd89vggqP2PPG+cJcUYH6y1IFMf2Qd/I/V0OlYV5LTn+k7MSFOfsUeRCFlmOyIYmTRWvQn+SZq3VgyOGxq1nf9yon00p/k53Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767794901; c=relaxed/simple; bh=aUCtRXbaqhLdP8PIW7MMmYazfgZB3Ep36B3bliuTmQo=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=fTBLDhc2yjXMxb3TX8tKYBb7tsG8QOLBI0zQQjB7WiQxvQA5IOojXczaIuWzFW5t0PDroxeFjDgdnl8uAApIItOIm9XJPCDol7V7H3U/7A1bGMOK6SIgjDVBePWSN/Yux60hsndUkkEKmSfOo3IrM+OEdETZBtnGI3wWbSzOVVA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=JI2U+wqC; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=gJ1KjV/S; arc=none smtp.client-ip=205.220.180.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="JI2U+wqC"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="gJ1KjV/S" Received: from pps.filterd (m0279868.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 607BKDLA1643003 for ; Wed, 7 Jan 2026 14:08:18 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= e/IXkgAHOqxTc8Sm3PgN43SHcMF+5VzPKwHvaU0kjnE=; b=JI2U+wqC/iFxxc8R L/iKo1Qrz+Ay5O8IESB0nb7pHECoJto3/EQwx91fcwaqPKoH7HOaIkgBeQKI8Sg0 cA4oX9yzfRZOZ215PAxaeixWu25xJ3nw1QijlDh+sQlTldrvrym82klJzHFmC53M QiuL7/VRZyCn3kkxhCMUChWgU7YBzoa0otOfm8b1GNtU5U+Lq2ZmkNY7jCjvD5zj ZLMnObvvOZ0aMrzgVRy+vjVLwv4W0WQoSTKftN5qUNI103rxQSmJ8ZP8bOlC+PBj EyVkroFZ9qsATt08EBi/l71KDZHZteosKOt9TY0y0okvstN/SgYLE4JN3N7XnAiu qwdEEA== Received: from mail-pg1-f199.google.com (mail-pg1-f199.google.com [209.85.215.199]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4bhgsfhngb-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Wed, 07 Jan 2026 14:08:18 +0000 (GMT) Received: by mail-pg1-f199.google.com with SMTP id 41be03b00d2f7-c3373f2bd74so1622897a12.3 for ; Wed, 07 Jan 2026 06:08:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1767794897; x=1768399697; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=e/IXkgAHOqxTc8Sm3PgN43SHcMF+5VzPKwHvaU0kjnE=; b=gJ1KjV/S/EkJw2+xV6Zn+7J+xd7N0xxMCvKxvy4MV5C4U6BOlBQ4r8IQBAgtjd0yfJ 7GVMV/HFPkzLDarqn0nq7bCMjuA/3LYyhSfk0oyHwfopgFkTbCNZ9dKKlw+QZS10U+q4 hOuD9aLpfUZNiOa74Hkx5IuWHBZ0lDNa7Ktu8BkbFBJpOnvYDtcQbh6HYT5jnJK/WoX+ E/W7H8CnOzgoNPOPlkCabhL5H2zNJkfhnrholemjb+48Uo+5FAZ+M7a0oHFArGzErxiO /fJmZ9BJUZebTCsw1vj4pzJ9/SwfPmfsgc8ziFkxBshXF9U6Pl532hyTgTg/LLcngjOs 10Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1767794897; x=1768399697; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=e/IXkgAHOqxTc8Sm3PgN43SHcMF+5VzPKwHvaU0kjnE=; b=Fy4J3V4IzC+ABTEjkqPLG1U0ownfBetQlQUSuM8tIXthIuqhgk+B2/b2uieo+JUgFr EyE8imhj6Bhj9zSQUBIqK8xSZnDXyrffzcx34vZ08ZXTcSOtiHwDqo07/XRm5mYL9Dq0 5VazuR8hAREfWrbdZvYCqxN85cKwUdEvNQ5LeznkBmLIIFpl91m/jw5xGr6ioiwYJuFn Woif8XyrWJJuStXuW14InHtBGRKohH38+5yg6KndiWw1dP0xKBolS39P2J8NRBVAjgch 1sbQRhIxirNFauoYyZJmbCsAEqSAfw/fu9QIof0PWO3D6FeUoTm4TrqwODfHMHT5zLMa wgew== X-Forwarded-Encrypted: i=1; AJvYcCVPz+LFZw7dH4cDiRPHROoUynXMRK6YJkgaLyWL+7SY8yVUuGaP9m4gTV9TF5yW124eGnExiDnteGVEr1Wt@vger.kernel.org X-Gm-Message-State: AOJu0YwNrtUuOunJfypLJ4tHskJ3mUb3kRbDvy8alIBly4yDrXN0x2qp z2t38PerB1vz4cB3UbyB75aFe9Vm8xkXHD13QUCKPlpIsLWA4c6b4qNNggfFy2OoSY0NFZh+5a+ IGZt2O+YsIyGzzOYfiaYjY/M0kEWt2iBHAWLQE9IYdRt9v1BZlt+WEIqMVWS73tdY5/N3 X-Gm-Gg: AY/fxX4OwIgtwELP8Fl+26J+LgDn5D29nwhyHFakfDh1wkOacdtVDGEUZ+h8CYRNivC jZqrk8Empef61kNM96XsnfzwzguPrdrwvk8k5QIAwarUYtHmTXW4W8S82qJakvmiFS6S973xl0r BJKmof7MtlVgo51+YWU0PiSaGrlcbljySJUihobwzMk57KH4MmT2vHFPMuak+uFcTZx6b/zZwMk nDNkF1nzxD6fx24z4dDyC9BbMc4qpDy1N2F6W/dTGifqZMPcwniX89ZeCqtY4FjP1iZp9SUgcDV 6T+FiT5dQjA34Uy3iB2mIfMiX5GVlzUvkA1V9lG/YMJA6OgqgPyAtTunaa488bjMc+6hM9wne3f rG+MXTGGG+RmulLuhOrbFRwlDFNmRk1ktk8QAlGFI X-Received: by 2002:a05:6a00:4147:b0:7f6:4a1f:68a9 with SMTP id d2e1a72fcca58-81b7f104474mr2377015b3a.23.1767794897401; Wed, 07 Jan 2026 06:08:17 -0800 (PST) X-Google-Smtp-Source: AGHT+IHrMqnbFrD/Ogjw6q/skADffcb23oZB8dneueWX+1jX467c2sCRc7k7ahqEDUlcFmFEg60wnQ== X-Received: by 2002:a05:6a00:4147:b0:7f6:4a1f:68a9 with SMTP id d2e1a72fcca58-81b7f104474mr2376978b3a.23.1767794896804; Wed, 07 Jan 2026 06:08:16 -0800 (PST) Received: from [192.168.1.2] ([49.204.107.20]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-819baa19242sm5174447b3a.7.2026.01.07.06.08.12 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 07 Jan 2026 06:08:16 -0800 (PST) Message-ID: Date: Wed, 7 Jan 2026 19:38:10 +0530 Precedence: bulk X-Mailing-List: linux-arm-msm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v1] serial: qcom_geni: Fix BT failure regression on RB2 platform To: Dmitry Baryshkov Cc: Konrad Dybcio , Greg Kroah-Hartman , Jiri Slaby , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org, bryan.odonoghue@linaro.org, andersson@kernel.org, psodagud@quicinc.com, djaggi@quicinc.com, quic_msavaliy@quicinc.com, quic_vtanuku@quicinc.com, quic_arandive@quicinc.com, quic_shazhuss@quicinc.com, quic_cchiluve@quicinc.com References: <20260107064834.1006428-1-praveen.talari@oss.qualcomm.com> <36d8fb98-562a-43dc-8b47-b4f6d29475f1@oss.qualcomm.com> <741df2ea-03fd-4af2-9a98-20d68658edcb@oss.qualcomm.com> Content-Language: en-US From: Praveen Talari In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwMTA3MDEwOSBTYWx0ZWRfX+Ir0qzmu9tgM aRC4lWQOBuAedXAgDtJHvqQSmF6+MzGYw00GWWPLE8Jrosgnbe+zoC/MEmysQ3b/WhZ1XuoRhay GSUO5LsZAfJHMNBzUqydDHNSwyMmlUoWSB6pmA2c83E22prqM6EQiN1uvZ59VltI8HF0yMEO+dA MapYujgmVG99mPF8od5y1hQG+Wj0re9MqcOWKxUK17dO3Ic8IAVdsltT9YGVsn0cb9E3UB0LzKc vUrhFvtblsVEWSL8cupt1wIxt9vxzXWLKSQFR1AaHZ8IXoOaKQ1KhQvcNCZ8qh+MbHoqA7+TkfD vnlg+FyPHzpts3wqXQLt8egkZQcLpjznO3WhL6LnaleGm4jb24eePRigVVBk1QxNS7OYs7BbBBs ntj2hfXfd2toRNAeptOglovr+QpLRFKfBHGXY4zzGWffrW8ZeBKpIQaZrMEp2rUi1KQeRNM/DcM +CNxKYP2gRxnFo11SzQ== X-Proofpoint-GUID: HVhk32yDOPQetLFb1iGclf1lq6m2NzoB X-Proofpoint-ORIG-GUID: HVhk32yDOPQetLFb1iGclf1lq6m2NzoB X-Authority-Analysis: v=2.4 cv=Abi83nXG c=1 sm=1 tr=0 ts=695e68d2 cx=c_pps a=Oh5Dbbf/trHjhBongsHeRQ==:117 a=+gEgXnvjvgnLECGlQBulyQ==:17 a=IkcTkHD0fZMA:10 a=vUbySO9Y5rIA:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=EUspDBNiAAAA:8 a=TCUISvXNB3W53Fu2B-YA:9 a=QEXdDO2ut3YA:10 a=_Vgx9l1VpLgwpw_dHYaR:22 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.100.49 definitions=2026-01-07_02,2026-01-06_01,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 bulkscore=0 suspectscore=0 phishscore=0 impostorscore=0 adultscore=0 malwarescore=0 clxscore=1015 lowpriorityscore=0 spamscore=0 priorityscore=1501 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2512120000 definitions=main-2601070109 Hi Dmistry, On 1/7/2026 5:05 PM, Dmitry Baryshkov wrote: > On Wed, Jan 07, 2026 at 04:28:22PM +0530, Praveen Talari wrote: >> Hi Konrad, >> >> On 1/7/2026 4:16 PM, Konrad Dybcio wrote: >>> On 1/7/26 10:24 AM, Praveen Talari wrote: >>>> Hi >>>> >>>> On 1/7/2026 12:52 PM, Dmitry Baryshkov wrote: >>>>> On Wed, 7 Jan 2026 at 09:06, Praveen Talari >>>>> wrote: >>>>>> >>>>>> Hi Dmistry, >>>>>> >>>>>> On 1/7/2026 12:24 PM, Dmitry Baryshkov wrote: >>>>>>> On Wed, 7 Jan 2026 at 08:48, Praveen Talari >>>>>>> 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 >>> >>> "QUP mode" and "FUNC mode" are tough to swallow even for an insider.. How >>> about: >>> >>> "qup_x" and "gpio" pinmux functions >> >> Yes, you are right. I am talking about "qup_x" and "gpio" pinmux functions > > => commit message, please. I hope the commit text below should be appropriate serial: qcom-geni: Fix BT failure regression on RB2 platform A regression in 6.19-rc1 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 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. Thanks, Praveen > >> >> Thanks, >> Praveen Talari >>> >>> ? >>> >>> Konrad >> >