From: Vikash Garodia <quic_vgarodia@quicinc.com>
To: Jorge Ramirez <jorge.ramirez@oss.qualcomm.com>
Cc: <quic_dikshita@quicinc.com>, <bryan.odonoghue@linaro.org>,
<loic.poulain@oss.qualcomm.com>, <mchehab@kernel.org>,
<hans.verkuil@cisco.com>, <linux-media@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: venus: hfi: explicitly release IRQ during teardown
Date: Mon, 16 Jun 2025 20:14:36 +0530 [thread overview]
Message-ID: <1bdf289b-5eec-d5de-a08b-6c7a772e15a3@quicinc.com> (raw)
In-Reply-To: <aFAVTvsDc8xvwBme@trex>
Hi Jorge,
On 6/16/2025 6:29 PM, Jorge Ramirez wrote:
> On 16/06/25 17:26:24, Vikash Garodia wrote:
>>
>> On 6/12/2025 1:59 PM, Jorge Ramirez-Ortiz wrote:
>>> Ensure the IRQ is released before dismantling the ISR handler and
>>> clearing related pointers.
>>>
>>> This prevents any possibility of the interrupt triggering after the
>>> handler context has been invalidated.
>>>
>>> Fixes: d96d3f30c0f2 ("[media] media: venus: hfi: add Venus HFI files")
>>> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>
>>> ---
>>> drivers/media/platform/qcom/venus/hfi_venus.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/drivers/media/platform/qcom/venus/hfi_venus.c b/drivers/media/platform/qcom/venus/hfi_venus.c
>>> index b5f2ea879950..d9d62d965bcf 100644
>>> --- a/drivers/media/platform/qcom/venus/hfi_venus.c
>>> +++ b/drivers/media/platform/qcom/venus/hfi_venus.c
>>> @@ -1678,6 +1678,7 @@ void venus_hfi_destroy(struct venus_core *core)
>>> venus_interface_queues_release(hdev);
>>> mutex_destroy(&hdev->lock);
>>> kfree(hdev);
>>> + devm_free_irq(core->dev, core->irq, core);
>> Could you please check and add the handling here [1] as well ?
>>
>> [1]
>> https://elixir.bootlin.com/linux/v6.16-rc1/source/drivers/media/platform/qcom/venus/core.c#L427
>
> hi Vikash, sorry I dont get your point - what do you mean?
IRQ need to be freed even for error cases during venus_probe().
Regards,
Vikash
>
>>
>> Regards,
>> Vikash
>>> core->ops = NULL;
>>> }
>>>
next prev parent reply other threads:[~2025-06-16 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 8:29 [PATCH] media: venus: hfi: explicitly release IRQ during teardown Jorge Ramirez-Ortiz
2025-06-16 11:56 ` Vikash Garodia
2025-06-16 12:59 ` Jorge Ramirez
2025-06-16 14:44 ` Vikash Garodia [this message]
2025-06-16 15:32 ` Jorge Ramirez
2025-06-18 7:07 ` Jorge Ramirez
2025-06-18 11:08 ` Bryan O'Donoghue
2025-06-18 13:13 ` Jorge Ramirez
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=1bdf289b-5eec-d5de-a08b-6c7a772e15a3@quicinc.com \
--to=quic_vgarodia@quicinc.com \
--cc=bryan.odonoghue@linaro.org \
--cc=hans.verkuil@cisco.com \
--cc=jorge.ramirez@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mchehab@kernel.org \
--cc=quic_dikshita@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