From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bhaumik Bhatt <bbhatt@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, hemantk@codeaurora.org,
carl.yin@quectel.com, naveen.kumar@quectel.com,
jhugo@codeaurora.org, linux-kernel@vger.kernel.org,
loic.poulain@linaro.org
Subject: Re: [PATCH v2 1/3] bus: mhi: core: Clear devices when moving execution environments
Date: Thu, 21 Jan 2021 13:20:22 +0530 [thread overview]
Message-ID: <20210121075022.GA30041@thinkpad> (raw)
In-Reply-To: <1610651795-31287-2-git-send-email-bbhatt@codeaurora.org>
On Thu, Jan 14, 2021 at 11:16:33AM -0800, Bhaumik Bhatt wrote:
> When moving from SBL to mission mode execution environment, there
> is no remove callback notification to MHI client drivers which
> operate on SBL mode only. Client driver devices are being created
> in SBL or AMSS(mission mode) and only destroyed after power down
> or SYS_ERROR. If there exist any SBL-specific channels, those are
> left open and client drivers are thus unaware of the new execution
> environment where those channels cannot operate. Close the gap and
> issue remove callbacks to SBL-specific client drivers once device
> enters mission mode.
>
What are the SBL specific channels and the client drivers operating on them?
If this is something going to come in future, then this patch can come later.
Thanks,
Mani
next prev parent reply other threads:[~2021-01-21 7:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 19:16 [PATCH v2 0/3] Serialize execution environment changes for MHI Bhaumik Bhatt
2021-01-14 19:16 ` [PATCH v2 1/3] bus: mhi: core: Clear devices when moving execution environments Bhaumik Bhatt
2021-01-15 17:45 ` Hemant Kumar
2021-01-21 7:50 ` Manivannan Sadhasivam [this message]
2021-02-04 23:52 ` Bhaumik Bhatt
2021-01-14 19:16 ` [PATCH v2 2/3] bus: mhi: core: Download AMSS image from appropriate function Bhaumik Bhatt
2021-01-15 18:58 ` Hemant Kumar
2021-01-14 19:16 ` [PATCH v2 3/3] bus: mhi: core: Process execution environment changes serially Bhaumik Bhatt
2021-01-15 19:02 ` Hemant Kumar
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=20210121075022.GA30041@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bbhatt@codeaurora.org \
--cc=carl.yin@quectel.com \
--cc=hemantk@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=naveen.kumar@quectel.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;
as well as URLs for NNTP newsgroup(s).