From: mansur@codeaurora.org
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: stanimir.varbanov@linaro.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, vgarodia@codeaurora.org,
linux-arm-msm-owner@vger.kernel.org
Subject: Re: [PATCH] venus: core: add shutdown callback for venus
Date: Thu, 06 Aug 2020 09:17:30 +0530 [thread overview]
Message-ID: <eb92618f22fd5350ab7e4565d54e86a5@codeaurora.org> (raw)
In-Reply-To: <7223de0f80de73835238abe13a79d1bc@codeaurora.org>
Hi Sai,
> On 2020-06-24 12:17, Sai Prakash Ranjan wrote:
>> Hi Mansur,
>>
>> On 2020-06-13 16:03, Mansur Alisha Shaik wrote:
>>> After the SMMU translation is disabled in the
>>> arm-smmu shutdown callback during reboot, if
>>> any subsystem are still alive then IOVAs they
>>> are using will become PAs on bus, which may
>>> lead to crash.
>>>
>>> Below are the consumers of smmu from venus
>>> arm-smmu: consumer: aa00000.video-codec supplier=15000000.iommu
>>> arm-smmu: consumer: video-firmware.0 supplier=15000000.iommu
>>>
>>> So implemented shutdown callback, which detach iommu maps.
>>>
>>> Change-Id: I0f0f331056e0b84b92f1d86f66618d4b1caaa24a
>>> Signed-off-by: Mansur Alisha Shaik <mansur@codeaurora.org>
>>> ---
>>> drivers/media/platform/qcom/venus/core.c | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>>
>>> diff --git a/drivers/media/platform/qcom/venus/core.c
>>> b/drivers/media/platform/qcom/venus/core.c
>>> index 30d4b9e..acf798c 100644
>>> --- a/drivers/media/platform/qcom/venus/core.c
>>> +++ b/drivers/media/platform/qcom/venus/core.c
>>> @@ -371,6 +371,14 @@ static int venus_remove(struct platform_device
>>> *pdev)
>>> return ret;
>>> }
>>>
>>> +static void venus_core_shutdown(struct platform_device *pdev)
>>> +{
>>> + int ret;
>>> +
>>> + ret = venus_remove(pdev);
>>> + WARN_ON(ret < 0);
>>
>> I don't think you should warn here, its shutdown path and you can't
>> do anything with this WARN unlike remove callback where you have
>> to be sure to cleanup properly so that you are able to reload module.
>> But if you still want a hint about this failure, then just add a
>> dev_err()
>> to indicate the failure instead of a big stack trace spamming kernel
>> log.
>>
posted V2 version by adding dev_warn during shutdown failure instead of
WARN_ON.
V2 version : https://lore.kernel.org/patchwork/patch/1284693/
>> Thanks,
>> Sai
---
Thanks,
Mansur
prev parent reply other threads:[~2020-08-06 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 10:33 [PATCH] venus: core: add shutdown callback for venus Mansur Alisha Shaik
2020-06-13 12:13 ` Stanimir Varbanov
2020-06-22 4:24 ` mansur
2020-06-24 6:47 ` Sai Prakash Ranjan
2020-08-06 3:47 ` mansur [this message]
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=eb92618f22fd5350ab7e4565d54e86a5@codeaurora.org \
--to=mansur@codeaurora.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=stanimir.varbanov@linaro.org \
--cc=vgarodia@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.