Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1016448pxk; Fri, 18 Sep 2020 01:17:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxdn2XqYlsxOxqLr1BGXTZPpWtdkdFK5K9ycrROlklNxko+wl9aPTY+922XxTR27vki1DCE X-Received: by 2002:a17:906:9245:: with SMTP id c5mr36928866ejx.54.1600417036874; Fri, 18 Sep 2020 01:17:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600417036; cv=none; d=google.com; s=arc-20160816; b=exwozKIiWyETrKdeYPccxk8WE1HExTGmQ6jm6/exU7UKxw6nkPZ0nyfm3gVCaF6+DL bnKEEMF0xef88vG8ynBgnEaxomlybxViI+SgWfCXamzIqMvi8MvY0BsBmcShKEyFyY07 0bbaIBYMGmQAs4L1raRkaGaKMhxd6//ONJ2MG49s584pLxN7eH5MyFv19bBVFnGZMMny BoSVzDKUpbTL8fZTgU6yWlOAC5HFYxhoNhGXg5OLqITzcFTKYsnMb8IbBl1q3GV52tmn mgcP9t4xN96NsYk0TIPivJlSb6Fmwy2Tgy/doMVsNfMZW2iLEPpiWhay7orlVIBs917r tCsQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=KjpK/t90NrMKbP3acpXH4K5nUxGc/z97PFlct56yIP4=; b=fLlZwoxsmqs445rMGg02dPtqVXcX5KJ3BPS59XbcfgOC75XwOYEHIqOc0ngxLJ2LlQ OMJVCavZua2xTcXdIdCuRiu6jZwRdzrCopeG7rps2oFwEVyea0euOeSCD8nY+B3ItTND tmZQaPRxSNGDPt9+8SEba5dsLvKV12yN9qPKwiIk6WMVXRNBBcwR/h3dTsMinDAQyrLv EKxB+MtpHfaxm4Kmnb3p6ORKeniAWwa4V5/mJYKYo/tZaibRPdjYDhz7+Vc097uGj9N5 NnShG3VusB9L8aIKtPxhw7hREyG4qTObk6HmKZjMKFy6gvZz4z/S2oKn249h4CSoZAfJ vRew== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=tEZ+KEuD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j10si1535456edy.0.2020.09.18.01.16.53; Fri, 18 Sep 2020 01:17:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=tEZ+KEuD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726690AbgIRHgs (ORCPT + 99 others); Fri, 18 Sep 2020 03:36:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:60494 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726199AbgIRHgr (ORCPT ); Fri, 18 Sep 2020 03:36:47 -0400 Received: from localhost (unknown [136.185.124.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 67993208C3; Fri, 18 Sep 2020 07:36:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1600414607; bh=tMJIGp6t8urEiQ2aBUoOKPVUceqzRsigcnMd9YF0FSo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tEZ+KEuD3hZrmbk53MT3WkYUZ9D1Ogv5S65S4pQb9gtOHaOmFSs+TcVWHG1e0/PK6 zDWVIzHc81iurFyMFWs3HjGuWrS2JuCmn+eDR4GXQVNWXGh4IdgtfW4AcMgIxTkyRb +EQVhc1QbK5YWPeBvPXr7nWrO2+ul9LTxdrdqBLM= Date: Fri, 18 Sep 2020 13:06:43 +0530 From: Vinod Koul To: Grygorii Strashko Cc: Peter Ujfalusi , dmaengine@vger.kernel.org, Sekhar Nori , linux-kernel@vger.kernel.org, Vignesh Raghavendra Subject: Re: [PATCH v2] dmaengine: ti: k3-udma-glue: fix channel enable functions Message-ID: <20200918073643.GM2968@vkoul-mobl> References: <20200916120955.7963-1-grygorii.strashko@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200916120955.7963-1-grygorii.strashko@ti.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 16-09-20, 15:09, Grygorii Strashko wrote: > Now the K3 UDMA glue layer enable functions perform RMW operation on UDMA > RX/TX RT_CTL registers to set EN bit and enable channel, which is > incorrect, because only EN bit has to be set in those registers to enable > channel (all other bits should be cleared 0). > More over, this causes issues when bootloader leaves UDMA channel RX/TX > RT_CTL registers in incorrect state - TDOWN bit set, for example. As > result, UDMA channel will just perform teardown right after it's enabled. > > Hence, fix it by writing correct values (EN=1) directly in UDMA channel > RX/TX RT_CTL registers in k3_udma_glue_enable_tx/rx_chn() functions. Applied, thanks -- ~Vinod