Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <eff55b55-cef0-2931-c8e5-95a9230c9d27@quicinc.com>
Date:   Mon, 18 Apr 2022 07:53:24 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.0
Subject: Re: [PATCH v3] bus: mhi: host: Wait for ready state after reset
Content-Language: en-US
To:     Manivannan Sadhasivam <mani@kernel.org>
CC:     <quic_hemantk@quicinc.com>, <quic_bbhatt@quicinc.com>,
        <mhi@lists.linux.dev>, <linux-arm-msm@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>
References: <1649875946-32516-1-git-send-email-quic_jhugo@quicinc.com>
 <20220418062645.GI7431@thinkpad>
From:   Jeffrey Hugo <quic_jhugo@quicinc.com>
In-Reply-To: <20220418062645.GI7431@thinkpad>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 4/18/2022 12:26 AM, Manivannan Sadhasivam wrote:
> On Wed, Apr 13, 2022 at 12:52:26PM -0600, Jeffrey Hugo wrote:
>> From: Jeffrey Hugo <jhugo@codeaurora.org>
>>
>> After the device has signaled the end of reset by clearing the reset bit,
>> it will automatically reinit MHI and the internal device structures.  Once
>> That is done, the device will signal it has entered the ready state.
>>
>> Signaling the ready state involves sending an interrupt (MSI) to the host
>> which might cause IOMMU faults if it occurs at the wrong time.
>>
>> If the controller is being powered down, and possibly removed, then the
>> reset flow would only wait for the end of reset.  At which point, the host
>> and device would start a race.  The host may complete its reset work, and
>> remove the interrupt handler, which would cause the interrupt to be
>> disabled in the IOMMU.  If that occurs before the device signals the ready
>> state, then the IOMMU will fault since it blocked an interrupt.  While
>> harmless, the fault would appear like a serious issue has occurred so let's
>> silence it by making sure the device hits the ready state before the host
>> completes its reset processing.
>>
>> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
>> Reviewed-by: Hemant Kumar <hemantk@codeaurora.org>
>> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> 
> I was about to apply this patch but wanted to check with you on using the
> double signed-off by tags. If the patch get's handed over between multiple
> developers then multiple signed-off by's make sense. But since it is you that
> handled the earlier patch also, I think one tag is enough with your new domain.
> 
> One more thing is, using codeaurora domain will bounce now. So, please use the
> quicinc domain for Hemant also.

I'm aware of the bouncing.  Git send-email however is not, and its 
default behavior can be a bit annoying in this edge case.

I've seen the dual SoB by the same developer elsewhere in the community, 
but if you want things "cleaned up" to the new quic ids, I'll do that.