From: Bhaumik Bhatt <bbhatt@codeaurora.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Hemant Kumar <hemantk@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Jeffrey Hugo <jhugo@codeaurora.org>
Subject: Re: [PATCH v3] mhi: pci_generic: Ensure device readiness before starting MHI
Date: Tue, 16 Feb 2021 09:37:05 -0800 [thread overview]
Message-ID: <d09e57132b03431964633f1d53b5a24d@codeaurora.org> (raw)
In-Reply-To: <CAMZdPi_rWc93B+e_P9cKvtx8v83AW18+r7HXYxn3fxALSp_1+Q@mail.gmail.com>
On 2021-02-14 11:30 PM, Loic Poulain wrote:
> Hi Bhaumik,
>
> On Fri, 12 Feb 2021 at 02:41, Bhaumik Bhatt <bbhatt@codeaurora.org>
> wrote:
>>
>> Hi Loic,
>>
>> On 2021-02-11 11:25 AM, Loic Poulain wrote:
>> > The PCI device may have not been bound from cold boot and be in
>> > undefined state, or simply not yet ready for MHI operations. This
>> > change ensures that the MHI layer is reset to initial state and
>> > ready for MHI initialization and power up.
>> >
>> > Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
> [...]
>> > +
>> > err = mhi_sync_power_up(mhi_cntrl);
>> > if (err) {
>> > dev_err(&pdev->dev, "failed to power up MHI controller\n");
>>
>> Can you share logs of what you're seeing as it is not clear why you
>> would need
>> this patch.
>>
>> We have a mechanism in place that Jeff added a while back [1], to
>> check
>> if device
>> is in SYS_ERROR state and do the same: issue reset and later, wait for
>> ready from
>> within mhi_sync_power_up() API.
>>
>> Note that the MHI_IN_PBL() macro includes EDL and Pass Through modes
>> as
>> well and
>> we do expect an MHI READY state move after Pass Through.
>
> I think this is a mix of several issues, that could be fixed by latest
> Jeffrey's patch and
> this one: "mhi: core: Move to polling method to wait for MHI ready".
>
> I assume it would be easier if you send this last one as standalone
> fix, for review and merge.
>
Will do.
> Regards,
> Loic
Thanks,
Bhaumik
---
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2021-02-16 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 19:25 [PATCH v3] mhi: pci_generic: Ensure device readiness before starting MHI Loic Poulain
2021-02-11 19:48 ` Bhaumik Bhatt
2021-02-12 1:41 ` Bhaumik Bhatt
2021-02-15 7:30 ` Loic Poulain
2021-02-16 17:37 ` Bhaumik Bhatt [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=d09e57132b03431964633f1d53b5a24d@codeaurora.org \
--to=bbhatt@codeaurora.org \
--cc=hemantk@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@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).