Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755452AbcKNE3O (ORCPT ); Sun, 13 Nov 2016 23:29:14 -0500 Received: from mga14.intel.com ([192.55.52.115]:65179 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752517AbcKNE3M (ORCPT ); Sun, 13 Nov 2016 23:29:12 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,488,1473145200"; d="scan'208";a="1059099629" Date: Mon, 14 Nov 2016 10:08:34 +0530 From: Vinod Koul To: Niklas Cassel Cc: robh+dt@kernel.org, mark.rutland@arm.com, dan.j.williams@intel.com, dmaengine@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Niklas Cassel Subject: Re: [PATCH] dmaengine: nbpfaxi: add optional max-burst property for memory reads/writes Message-ID: <20161114043834.GP3000@localhost> References: <1477315755-4783-1-git-send-email-niklass@axis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1477315755-4783-1-git-send-email-niklass@axis.com> 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 Content-Length: 791 Lines: 19 On Mon, Oct 24, 2016 at 03:29:15PM +0200, Niklas Cassel wrote: > From: Niklas Cassel > > Due to a hardware bug, reading memory (from the Accelerator Coherency Port) > with a burst size equal to the maximum burst size allowed by the DMA > hardware's buffer size will cause a hardware hang on the ARTPEC-6 SoC, > where the only solution is a manual power cycle. > On ARTPEC-6, this hardware bug does not trigger when writing memory (to the > Accelerator Coherency Port) with a burst size equal to the maximum burst > size allowed by the DMA hardware's buffer size. > > To avoid this hardware hang, introduce a new optional max-burst property > for memory reads. For completeness, also introduce a max-burst property for > memory writes. Applied, thanks -- ~Vinod