From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jorge Ramirez <jorge.ramirez@oss.qualcomm.com>
Cc: Praveen Talari <praveen.talari@oss.qualcomm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Praveen Talari <quic_ptalari@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, alexey.klimov@linaro.org,
dmitry.baryshkov@oss.qualcomm.com, 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
Subject: Re: [PATCH v2] serial: qcom_geni: Fix pinctrl deadlock on runtime resume
Date: Fri, 19 Sep 2025 09:30:48 +0900 [thread overview]
Message-ID: <641256da-e142-4a35-9089-d3833baec6fd@kernel.org> (raw)
In-Reply-To: <aMvZ10EsMif/DOP4@trex>
On 18/09/2025 19:07, Jorge Ramirez wrote:
> On 18/09/25 09:25:48, Jorge Ramirez wrote:
>>
>> let's test a bit further Praveen - we need to validate/trace the wake
>> path on a real scenairo to make sure it is not cpu intensive (although I
>> suspect the 2% was due to the storm you described more than to the code
>> path itself)
>>
>> I can then provide the tested-by on the list.
>>
>
> um bluetooh comms are broken - reverting the runtime_pm patch fixes it.
> and the proposed fix (V2) does not address this scenario.
>
> I agree with the common sentiment, I think the patch should be reverted
> in linux-next and better test definition shared.
For the record, the revert was already applied.
Any new patch here should carry some more tested-by, before it can get
applied.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-19 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 18:51 [PATCH v2] serial: qcom_geni: Fix pinctrl deadlock on runtime resume Praveen Talari
2025-09-17 23:58 ` Krzysztof Kozlowski
2025-09-18 3:55 ` Praveen Talari
2025-09-18 7:25 ` Jorge Ramirez
2025-09-18 10:07 ` Jorge Ramirez
2025-09-19 0:30 ` Krzysztof Kozlowski [this message]
2025-09-19 0:33 ` Krzysztof Kozlowski
2025-09-18 2:14 ` Bjorn Andersson
2025-09-18 4:33 ` Praveen Talari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=641256da-e142-4a35-9089-d3833baec6fd@kernel.org \
--to=krzk@kernel.org \
--cc=alexey.klimov@linaro.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=djaggi@quicinc.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=jorge.ramirez@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=praveen.talari@oss.qualcomm.com \
--cc=psodagud@quicinc.com \
--cc=quic_arandive@quicinc.com \
--cc=quic_cchiluve@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_ptalari@quicinc.com \
--cc=quic_shazhuss@quicinc.com \
--cc=quic_vtanuku@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox