Hi Mani,
On 5/13/20 12:04 AM, Manivannan Sadhasivam wrote:
On Tue, May 12, 2020 at 05:28:45PM -0700, Hemant Kumar wrote:
Hi Mani,
On 5/11/20 11:53 PM, Manivannan Sadhasivam wrote:
On Mon, May 11, 2020 at 07:03:07PM -0700, Hemant Kumar wrote:
Driver continues handling of BHI interrupt even if
On Mon, May 11, 2020 at 07:03:07PM -0700, Hemant Kumar wrote:
> Driver continues handling of BHI interrupt even if MHI register access
> is not allowed. By doing so it calls the status call back and performs
> early notification for the MHI client. This is not needed when MHI
> register access is n
On Tue, May 12, 2020 at 05:28:45PM -0700, Hemant Kumar wrote:
> Hi Mani,
>
> On 5/11/20 11:53 PM, Manivannan Sadhasivam wrote:
> > On Mon, May 11, 2020 at 07:03:07PM -0700, Hemant Kumar wrote:
> > > Driver continues handling of BHI interrupt even if MHI register access
> > > is not allowed. By doi
Hi Mani,
On 5/11/20 11:53 PM, Manivannan Sadhasivam wrote:
On Mon, May 11, 2020 at 07:03:07PM -0700, Hemant Kumar wrote:
Driver continues handling of BHI interrupt even if MHI register access
is not allowed. By doing so it calls the status call back and performs
early notification for the MHI c
On Mon, May 11, 2020 at 07:03:07PM -0700, Hemant Kumar wrote:
> Driver continues handling of BHI interrupt even if MHI register access
> is not allowed. By doing so it calls the status call back and performs
> early notification for the MHI client. This is not needed when MHI
> register access is n
Driver continues handling of BHI interrupt even if MHI register access
is not allowed. By doing so it calls the status call back and performs
early notification for the MHI client. This is not needed when MHI
register access is not allowed. Hence skip the handling in this case and
return. Also add
6 matches
Mail list logo