[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171017081422.GA19475@lst.de>
Date: Tue, 17 Oct 2017 10:14:22 +0200
From: Christoph Hellwig <hch@....de>
To: Robin Murphy <robin.murphy@....com>
Cc: Jim Quinlan <jim2101024@...il.com>, linux-kernel@...r.kernel.org,
Mark Rutland <mark.rutland@....com>, linux-mips@...ux-mips.org,
Florian Fainelli <f.fainelli@...il.com>,
devicetree@...r.kernel.org, linux-pci@...r.kernel.org,
Kevin Cernekee <cernekee@...il.com>,
Will Deacon <will.deacon@....com>,
Ralf Baechle <ralf@...ux-mips.org>,
Rob Herring <robh+dt@...nel.org>,
bcm-kernel-feedback-list@...adcom.com,
Gregory Fong <gregory.0xf0@...il.com>,
Catalin Marinas <catalin.marinas@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Brian Norris <computersforpeace@...il.com>,
linux-arm-kernel@...ts.infradead.org,
Christoph Hellwig <hch@....de>,
Marek Szyprowski <m.szyprowski@...sung.com>,
iommu@...ts.linux-foundation.org
Subject: Re: [PATCH 5/9] PCI: host: brcmstb: add dma-ranges for inbound
traffic
Just took a quick look over this and I basically agree with the comments
from Robin.
What I don't understand is why you're even trying to do all these
hacky things.
It seems like the controller should simply set dma_pfn_offset for
each device hanging off it, and all the supported architectures
should be updated to obey that if they don't do so yet, and
you're done without needing this giant mess.
Powered by blists - more mailing lists