From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bhaumik Bhatt <bbhatt@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, hemantk@codeaurora.org,
jhugo@codeaurora.org, loic.poulain@linaro.org,
kvalo@codeaurora.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/6] bus: mhi: core: Allow receiving a STOP channel command response
Date: Sat, 21 Nov 2020 22:46:01 +0530 [thread overview]
Message-ID: <20201121171601.GB2343@thinkpad> (raw)
In-Reply-To: <616fe76b6757e8d545cfaaba1ab3ab50@codeaurora.org>
On Mon, Nov 16, 2020 at 09:36:09AM -0800, Bhaumik Bhatt wrote:
> Hi Mani,
>
> On 2020-11-15 23:13, Manivannan Sadhasivam wrote:
> > On Wed, Nov 11, 2020 at 11:21:08AM -0800, Bhaumik Bhatt wrote:
> > > Add support to receive the response to a STOP channel command to the
> > > MHI bus. If a client would like to STOP a channel instead of issuing
> > > a RESET to it, this would provide support for it.
> > >
> > > Signed-off-by: Bhaumik Bhatt <bbhatt@codeaurora.org>
> > > ---
> > > drivers/bus/mhi/core/init.c | 5 +++--
> > > drivers/bus/mhi/core/main.c | 5 +++++
> > > 2 files changed, 8 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/bus/mhi/core/init.c b/drivers/bus/mhi/core/init.c
> > > index 8cefa35..4d34d62 100644
> > > --- a/drivers/bus/mhi/core/init.c
> > > +++ b/drivers/bus/mhi/core/init.c
> > > @@ -1267,8 +1267,9 @@ static int mhi_driver_remove(struct device *dev)
> > >
> > > mutex_lock(&mhi_chan->mutex);
> > >
> > > - if (ch_state[dir] == MHI_CH_STATE_ENABLED &&
> > > - !mhi_chan->offload_ch)
> > > + if ((ch_state[dir] == MHI_CH_STATE_ENABLED ||
> > > + ch_state[dir] == MHI_CH_STATE_STOP) &&
> >
> > This enum is not defined in this patch so it'll break. Please add a
> > separate
> > patch which introduces the new state enums alone and then have patches
> > 1/2
> > as a followup.
> >
> It is actually already defined and present in internal.h as enum
> mhi_ch_state.
>
> The old set of enums has MHI_CH_STATE_STOP from enum mhi_ch_state and the
> new
> enum I introduced is MHI_CH_STATE_TYPE_STOP from enum enum
> mhi_ch_state_type.
>
> If it seems confusing, suggestions to renaming them are welcome.
>
Ah, sorry. I got confused with MHI_CH_STATE_TYPE_STOP and MHI_CH_STATE_STOP.
Ignore my previous comment.
Thanks,
Mani
> > Also this change is not belonging to this commit I believe.
> >
> I included this change here because, a channel can be in "stopped" state and
> a user module could be unloaded or a crash could force a driver remove
> leading
> us to come this check.
>
> If you think I should move it as a separate patch, let me know.
> > Thanks,
> > Mani
> >
> > > + !mhi_chan->offload_ch)
> > > mhi_deinit_chan_ctxt(mhi_cntrl, mhi_chan);
> > >
> > > mhi_chan->ch_state = MHI_CH_STATE_DISABLED;
> > > diff --git a/drivers/bus/mhi/core/main.c b/drivers/bus/mhi/core/main.c
> > > index f953e2a..ad881a1 100644
> > > --- a/drivers/bus/mhi/core/main.c
> > > +++ b/drivers/bus/mhi/core/main.c
> > > @@ -1194,6 +1194,11 @@ int mhi_send_cmd(struct mhi_controller
> > > *mhi_cntrl,
> > > cmd_tre->dword[0] = MHI_TRE_CMD_RESET_DWORD0;
> > > cmd_tre->dword[1] = MHI_TRE_CMD_RESET_DWORD1(chan);
> > > break;
> > > + case MHI_CMD_STOP_CHAN:
> > > + cmd_tre->ptr = MHI_TRE_CMD_STOP_PTR;
> > > + cmd_tre->dword[0] = MHI_TRE_CMD_STOP_DWORD0;
> > > + cmd_tre->dword[1] = MHI_TRE_CMD_STOP_DWORD1(chan);
> > > + break;
> > > case MHI_CMD_START_CHAN:
> > > cmd_tre->ptr = MHI_TRE_CMD_START_PTR;
> > > cmd_tre->dword[0] = MHI_TRE_CMD_START_DWORD0;
> > > --
> > > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
> > > Forum,
> > > a Linux Foundation Collaborative Project
> > >
>
> Thanks,
> Bhaumik
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2020-11-21 17:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 19:21 [PATCH v2 0/6] Updates to MHI channel handling Bhaumik Bhatt
2020-11-11 19:21 ` [PATCH v2 1/6] bus: mhi: core: Allow receiving a STOP channel command response Bhaumik Bhatt
2020-11-16 7:13 ` Manivannan Sadhasivam
2020-11-16 17:36 ` Bhaumik Bhatt
2020-11-21 17:16 ` Manivannan Sadhasivam [this message]
2020-11-24 0:23 ` Bhaumik Bhatt
2020-11-11 19:21 ` [PATCH v2 2/6] bus: mhi: core: Improvements to the channel handling state machine Bhaumik Bhatt
2020-11-16 10:22 ` Manivannan Sadhasivam
2020-11-11 19:21 ` [PATCH v2 3/6] bus: mhi: core: Add support to stop or start channel data transfers Bhaumik Bhatt
2020-11-16 12:43 ` Manivannan Sadhasivam
2020-11-16 20:56 ` Bhaumik Bhatt
2020-11-21 17:05 ` Manivannan Sadhasivam
2020-11-24 0:45 ` Bhaumik Bhatt
2020-11-11 19:21 ` [PATCH v2 4/6] bus: mhi: core: Check execution environment for channel before issuing reset Bhaumik Bhatt
2020-11-11 19:21 ` [PATCH v2 5/6] bus: mhi: core: Remove __ prefix for MHI channel unprepare function Bhaumik Bhatt
2020-11-16 12:47 ` Manivannan Sadhasivam
2020-11-11 19:21 ` [PATCH v2 6/6] bus: mhi: Improve documentation on channel transfer setup APIs Bhaumik Bhatt
2020-11-16 12:50 ` Manivannan Sadhasivam
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=20201121171601.GB2343@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bbhatt@codeaurora.org \
--cc=hemantk@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.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 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).