From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 18 Jan 2018 08:31:34 +0100 (CET) Received: from verein.lst.de ([213.95.11.211]:50311 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S23990425AbeARHbXzEMkU (ORCPT ); Thu, 18 Jan 2018 08:31:23 +0100 Received: by newverein.lst.de (Postfix, from userid 2407) id 1F36068DB6; Thu, 18 Jan 2018 08:31:23 +0100 (CET) Date: Thu, 18 Jan 2018 08:31:23 +0100 From: Christoph Hellwig To: Rob Herring Cc: Jim Quinlan , "linux-kernel@vger.kernel.org" , Bjorn Helgaas , Catalin Marinas , Will Deacon , Brian Norris , Russell King , Robin Murphy , Christoph Hellwig , Florian Fainelli , Jonas Gorski , Lorenzo Pieralisi , Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux-MIPS , linux-pci@vger.kernel.org, Kevin Cernekee , Ralf Baechle , bcm-kernel-feedback-list@broadcom.com, Gregory Fong , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Subject: Re: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic Message-ID: <20180118073123.GA15766@lst.de> References: <1516058925-46522-1-git-send-email-jim2101024@gmail.com> <1516058925-46522-5-git-send-email-jim2101024@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 62231 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: hch@lst.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Wed, Jan 17, 2018 at 08:15:33PM -0600, Rob Herring wrote: > > (a) overriding/redefining the dma_to_phys() and phys_to_dma() calls > > that are used by the dma_ops routines. This is the approach of > > > > arch/mips/cavium-octeon/dma-octeon.c > > MIPS is rarely an example to follow. :) But in this case it actually is the example to follow as told previously. NAK again for these chained dma ops that only create problems. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de ([213.95.11.211]:50311 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S23990425AbeARHbXzEMkU (ORCPT ); Thu, 18 Jan 2018 08:31:23 +0100 Date: Thu, 18 Jan 2018 08:31:23 +0100 From: Christoph Hellwig Subject: Re: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic Message-ID: <20180118073123.GA15766@lst.de> References: <1516058925-46522-1-git-send-email-jim2101024@gmail.com> <1516058925-46522-5-git-send-email-jim2101024@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Return-Path: Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-subscribe: List-owner: List-post: List-archive: To: Rob Herring Cc: Jim Quinlan , "linux-kernel@vger.kernel.org" , Bjorn Helgaas , Catalin Marinas , Will Deacon , Brian Norris , Russell King , Robin Murphy , Christoph Hellwig , Florian Fainelli , Jonas Gorski , Lorenzo Pieralisi , Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux-MIPS , linux-pci@vger.kernel.org, Kevin Cernekee , Ralf Baechle , bcm-kernel-feedback-list@broadcom.com, Gregory Fong , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Message-ID: <20180118073123.URIl7WGBBANBWSCSUQh7hDs7FFcMdoUbatvpCsAWZYY@z> On Wed, Jan 17, 2018 at 08:15:33PM -0600, Rob Herring wrote: > > (a) overriding/redefining the dma_to_phys() and phys_to_dma() calls > > that are used by the dma_ops routines. This is the approach of > > > > arch/mips/cavium-octeon/dma-octeon.c > > MIPS is rarely an example to follow. :) But in this case it actually is the example to follow as told previously. NAK again for these chained dma ops that only create problems.