From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935133AbcJROzK (ORCPT ); Tue, 18 Oct 2016 10:55:10 -0400 Received: from mga01.intel.com ([192.55.52.88]:16923 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933629AbcJROzC (ORCPT ); Tue, 18 Oct 2016 10:55:02 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,362,1473145200"; d="scan'208";a="21252981" Date: Tue, 18 Oct 2016 20:33:53 +0530 From: Vinod Koul To: Sinan Kaya Cc: dmaengine@vger.kernel.org, timur@codeaurora.org, cov@codeaurora.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] dmaengine: qcom_hidma: prevent disable in error Message-ID: <20161018150353.GC2467@localhost> References: <1475782394-27887-1-git-send-email-okaya@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1475782394-27887-1-git-send-email-okaya@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 06, 2016 at 03:33:14PM -0400, Sinan Kaya wrote: > When an error is observed, we try to disable the channel and prevent > further accesses from the client. > > Depending on the type of error, transitioning into disabled state might > not be possible. Adding a check to make sure that HW is in enabled/running > state before the disable transition happens. Applied, thanks -- ~Vinod