From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <broonie@kernel.org>, <vkoul@kernel.org>,
<akashast@codeaurora.org>, <dianders@chromium.org>,
<linux-arm-msm@vger.kernel.org>, <linux-spi@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] spi: spi-geni-qcom: Fix missing undo runtime PM changes at driver exit time
Date: Fri, 6 Sep 2024 11:50:26 +0800 [thread overview]
Message-ID: <a314d448-abb7-1a9c-5c45-7fce9aa69362@huawei.com> (raw)
In-Reply-To: <CAA8EJppbuMGjo3PHBnmHF5yXFOBUon50ZSKKzWFqGs3qgFmR3g@mail.gmail.com>
On 2024/9/6 11:43, Dmitry Baryshkov wrote:
> On Fri, 6 Sept 2024 at 06:41, Jinjie Ruan <ruanjinjie@huawei.com> wrote:
>>
>>
>>
>> On 2024/9/6 11:36, Dmitry Baryshkov wrote:
>>> On Fri, 6 Sept 2024 at 06:31, Jinjie Ruan <ruanjinjie@huawei.com> wrote:
>>>>
>>>>
>>>>
>>>> On 2024/9/6 11:15, Dmitry Baryshkov wrote:
>>>>> On Fri, Sep 06, 2024 at 11:13:45AM GMT, Jinjie Ruan wrote:
>>>>>> It's important to undo pm_runtime_use_autosuspend() with
>>>>>> pm_runtime_dont_use_autosuspend() at driver exit time unless driver
>>>>>> initially enabled pm_runtime with devm_pm_runtime_enable()
>>>>>> (which handles it for you).
>>>>>>
>>>>>> Hence, call pm_runtime_dont_use_autosuspend() at driver exit time
>>>>>> to fix it.
>>>>>>
>>>>>> Fixes: cfdab2cd85ec ("spi: spi-geni-qcom: Set an autosuspend delay of 250 ms")
>>>>>> ---
>>>>>> v2:
>>>>>> - Fix it directly instead of use devm_pm_runtime_enable().
>>>>>
>>>>> Why?
>>>>
>>>> The devm* sequence will have some problem, which will not consistent
>>>> with the former.
>>>>
>>>> Link:
>>>> https://lore.kernel.org/all/CAD=FV=VyDk-e2KNiuiBcACFAdrQmihOH6X6BSpGB+T1MsgsiKw@mail.gmail.com/
>>>
>>> That comment was for devm_request_irq(), not devm_pm_runtime_enable().
>>
>>
>> In the very least, ** parch #2 needs to come before this one and that
>> would help, but it won't fix everything **. Specifically in order to
>> keep the order proper you'll need to use devm_add_action_or_reset() to
>> "devm-ize" the freeing of the DMA channels.
>
> This is patch #2. so I don't understand your comment. Moreover you
> don't have to use devm for each and every possible item. However I
> think it makes sense for pm_runtime in this case.
You are right, only use devm_pm_runtime_enable() here, there is no
change for the resource release sequence, but I have a cleanup patch
ready to replace all these with devm*, which depends on the 2 fix patch.
>
>>
>>
>>>
>>>>
>>>>>
>>>>>> ---
>>>>>> drivers/spi/spi-geni-qcom.c | 2 ++
>>>>>> 1 file changed, 2 insertions(+)
>>>>>>
>>>>>> diff --git a/drivers/spi/spi-geni-qcom.c b/drivers/spi/spi-geni-qcom.c
>>>>>> index fc2819effe2d..38857edbc785 100644
>>>>>> --- a/drivers/spi/spi-geni-qcom.c
>>>>>> +++ b/drivers/spi/spi-geni-qcom.c
>>>>>> @@ -1158,6 +1158,7 @@ static int spi_geni_probe(struct platform_device *pdev)
>>>>>> spi_geni_release_dma:
>>>>>> spi_geni_release_dma_chan(mas);
>>>>>> spi_geni_probe_runtime_disable:
>>>>>> + pm_runtime_dont_use_autosuspend(dev);
>>>>>> pm_runtime_disable(dev);
>>>>>> return ret;
>>>>>> }
>>>>>> @@ -1174,6 +1175,7 @@ static void spi_geni_remove(struct platform_device *pdev)
>>>>>>
>>>>>> spi_geni_release_dma_chan(mas);
>>>>>>
>>>>>> + pm_runtime_dont_use_autosuspend(&pdev->dev);
>>>>>> pm_runtime_disable(&pdev->dev);
>>>>>> }
>>>>>>
>>>>>> --
>>>>>> 2.34.1
>>>>>>
>>>>>
>>>
>>>
>>>
>
>
>
next prev parent reply other threads:[~2024-09-06 3:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 3:13 [PATCH v2 0/2] spi: geni-qcom: Fix incorrect free_irq() sequence Jinjie Ruan
2024-09-06 3:13 ` [PATCH v2 1/2] " Jinjie Ruan
2024-09-06 4:27 ` Mukesh Kumar Savaliya
2024-09-06 6:47 ` Jinjie Ruan
2024-09-06 10:57 ` Mukesh Kumar Savaliya
2024-09-06 3:13 ` [PATCH v2 2/2] spi: spi-geni-qcom: Fix missing undo runtime PM changes at driver exit time Jinjie Ruan
2024-09-06 3:15 ` Dmitry Baryshkov
2024-09-06 3:31 ` Jinjie Ruan
2024-09-06 3:36 ` Dmitry Baryshkov
2024-09-06 3:40 ` Jinjie Ruan
2024-09-06 3:43 ` Dmitry Baryshkov
2024-09-06 3:50 ` Jinjie Ruan [this message]
2024-09-06 3:52 ` Dmitry Baryshkov
2024-09-06 4:01 ` Jinjie Ruan
2024-09-06 4:03 ` Dmitry Baryshkov
2024-09-06 6:50 ` Jinjie Ruan
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=a314d448-abb7-1a9c-5c45-7fce9aa69362@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=akashast@codeaurora.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=vkoul@kernel.org \
/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