[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6790d212-5980-39bd-ac4c-1176225604fd@codeaurora.org>
Date: Fri, 26 Feb 2021 14:06:36 -0800
From: Hemant Kumar <hemantk@...eaurora.org>
To: Bhaumik Bhatt <bbhatt@...eaurora.org>,
manivannan.sadhasivam@...aro.org
Cc: linux-arm-msm@...r.kernel.org, jhugo@...eaurora.org,
linux-kernel@...r.kernel.org, loic.poulain@...aro.org,
carl.yin@...ctel.com, naveen.kumar@...ctel.com
Subject: Re: [PATCH v6 1/4] bus: mhi: core: Destroy SBL devices when moving to
mission mode
On 2/24/21 3:23 PM, Bhaumik Bhatt wrote:
> Currently, client devices are created in SBL or AMSS (mission
> mode) and only destroyed after power down or SYS ERROR. When
> moving between certain execution environments, such as from SBL
> to AMSS, no clean-up is required. This presents an issue where
> SBL-specific channels are left open and client drivers now run in
> an execution environment where they cannot operate. Fix this by
> expanding the mhi_destroy_device() to do an execution environment
> specific clean-up if one is requested. Close the gap and destroy
> devices in such scenarios that allow SBL client drivers to clean
> up once device enters mission mode.
>
> Signed-off-by: Bhaumik Bhatt <bbhatt@...eaurora.org>
It make sense to clean up previous execution env related resources.
Reviewed-by: Hemant Kumar <hemantk@...eaurora.org>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
Powered by blists - more mailing lists