[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMZdPi_SWn9a_KvfpNnKCLcq2gb+A7KmUth7zVTgWs+H-Okv=w@mail.gmail.com>
Date: Tue, 30 Mar 2021 10:03:32 +0200
From: Loic Poulain <loic.poulain@...aro.org>
To: Bhaumik Bhatt <bbhatt@...eaurora.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Hemant Kumar <hemantk@...eaurora.org>,
Jeffrey Hugo <jhugo@...eaurora.org>,
open list <linux-kernel@...r.kernel.org>,
Carl Yin(殷张成) <carl.yin@...ctel.com>,
Naveen Kumar <naveen.kumar@...ctel.com>,
abickett@...eaurora.org
Subject: Re: [PATCH v1 6/7] bus: mhi: core: Wait for MHI READY state in most scenarios
On Tue, 30 Mar 2021 at 03:28, Bhaumik Bhatt <bbhatt@...eaurora.org> wrote:
>
> When moving from SYS_ERROR transition to a different execution
> environment, MHI host relies on the BHI register read to spawn
> the next image download or wait for READY -> M0 states. The
> device can at times move the execution environment to mission
> mode when a pass through is expected, which can result in a
> stall. Initiate a wait for MHI READY and write M0 such that the
> device can proceed with state change event updates for any new
> execution environment being entered. This allows us to remove
> conditionals in handling firmware load for PBL modes and keeps
> the execution environment out of the picture as it can change at
> any time.
>
> Signed-off-by: Bhaumik Bhatt <bbhatt@...eaurora.org>
Reviewed-by: Loic Poulain <loic.poulain@...aro.org>
Powered by blists - more mailing lists