linux-kernel - Re: [PATCH v3 2/7] bus: mhi: core: Allow channel to be disabled from stopped state

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0759bdc2-1c25-acde-5d1b-451c6f6e73d7@codeaurora.org>
Date:   Wed, 2 Dec 2020 16:17:59 -0800
From:   Hemant Kumar <hemantk@...eaurora.org>
To:     Bhaumik Bhatt <bbhatt@...eaurora.org>,
        manivannan.sadhasivam@...aro.org
Cc:     linux-arm-msm@...r.kernel.org, loic.poulain@...aro.org,
        jhugo@...eaurora.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/7] bus: mhi: core: Allow channel to be disabled from
 stopped state



On 12/2/20 3:40 PM, Bhaumik Bhatt wrote:
> If a channel was explicitly stopped but not reset, allow it to
> move to a disabled state so the channel context can be cleaned
> up. As the channel remained in a stopped state, its context was
> not reset and cleared, which needs to be done if a client driver
> module is unloaded or a device crash occurs.
> 
> Signed-off-by: Bhaumik Bhatt <bbhatt@...eaurora.org>
> ---

Reviewed-by: Hemant Kumar <hemantk@...eaurora.org>
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project