From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 18 Jan 2018 16:23:40 +0100 (CET) Received: from verein.lst.de ([213.95.11.211]:52600 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S23992956AbeARPXeJdvm0 (ORCPT ); Thu, 18 Jan 2018 16:23:34 +0100 Received: by newverein.lst.de (Postfix, from userid 2407) id 5537468DB6; Thu, 18 Jan 2018 16:23:31 +0100 (CET) Date: Thu, 18 Jan 2018 16:23:31 +0100 From: Christoph Hellwig To: Florian Fainelli Cc: Christoph Hellwig , Rob Herring , Jim Quinlan , "linux-kernel@vger.kernel.org" , Bjorn Helgaas , Catalin Marinas , Will Deacon , Brian Norris , Russell King , Robin Murphy , 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: <20180118152331.GA24461@lst.de> References: <1516058925-46522-1-git-send-email-jim2101024@gmail.com> <1516058925-46522-5-git-send-email-jim2101024@gmail.com> <20180118073123.GA15766@lst.de> 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: 62234 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 Thu, Jan 18, 2018 at 07:09:23AM -0800, Florian Fainelli wrote: > >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. > > Care to explain what should be done instead? Override phys_to_dma and dma_to_phys as mips and x86 do for similar situations. Bonous points of finding some generic way of doing it instead of hiding it in arch code. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Date: Thu, 18 Jan 2018 16:23:31 +0100 From: Christoph Hellwig To: Florian Fainelli Subject: Re: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic Message-ID: <20180118152331.GA24461@lst.de> References: <1516058925-46522-1-git-send-email-jim2101024@gmail.com> <1516058925-46522-5-git-send-email-jim2101024@gmail.com> <20180118073123.GA15766@lst.de> MIME-Version: 1.0 In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Lorenzo Pieralisi , Linux-MIPS , linux-pci@vger.kernel.org, Catalin Marinas , Kevin Cernekee , Will Deacon , "linux-kernel@vger.kernel.org" , Rob Herring , Russell King , Jim Quinlan , bcm-kernel-feedback-list@broadcom.com, Ralf Baechle , Gregory Fong , Jonas Gorski , Bjorn Helgaas , Brian Norris , Robin Murphy , Christoph Hellwig , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" Content-Type: text/plain; charset="us-ascii" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+bjorn=helgaas.com@lists.infradead.org List-ID: On Thu, Jan 18, 2018 at 07:09:23AM -0800, Florian Fainelli wrote: > >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. > > Care to explain what should be done instead? Override phys_to_dma and dma_to_phys as mips and x86 do for similar situations. Bonous points of finding some generic way of doing it instead of hiding it in arch code. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel From mboxrd@z Thu Jan 1 00:00:00 1970 From: hch@lst.de (Christoph Hellwig) Date: Thu, 18 Jan 2018 16:23:31 +0100 Subject: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic In-Reply-To: References: <1516058925-46522-1-git-send-email-jim2101024@gmail.com> <1516058925-46522-5-git-send-email-jim2101024@gmail.com> <20180118073123.GA15766@lst.de> Message-ID: <20180118152331.GA24461@lst.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Jan 18, 2018 at 07:09:23AM -0800, Florian Fainelli wrote: > >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. > > Care to explain what should be done instead? Override phys_to_dma and dma_to_phys as mips and x86 do for similar situations. Bonous points of finding some generic way of doing it instead of hiding it in arch code. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic Date: Thu, 18 Jan 2018 16:23:31 +0100 Message-ID: <20180118152331.GA24461@lst.de> References: <1516058925-46522-1-git-send-email-jim2101024@gmail.com> <1516058925-46522-5-git-send-email-jim2101024@gmail.com> <20180118073123.GA15766@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Florian Fainelli Cc: Christoph Hellwig , Rob Herring , Jim Quinlan , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Bjorn Helgaas , Catalin Marinas , Will Deacon , Brian Norris , Russell King , Robin Murphy , Jonas Gorski , Lorenzo Pieralisi , Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux-MIPS , linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Kevin Cernekee , Ralf Baechle b List-Id: devicetree@vger.kernel.org On Thu, Jan 18, 2018 at 07:09:23AM -0800, Florian Fainelli wrote: > >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. > > Care to explain what should be done instead? Override phys_to_dma and dma_to_phys as mips and x86 do for similar situations. Bonous points of finding some generic way of doing it instead of hiding it in arch code. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html