From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753631AbcIBNLM (ORCPT ); Fri, 2 Sep 2016 09:11:12 -0400 Received: from mout.kundenserver.de ([212.227.126.134]:52429 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751280AbcIBNLK (ORCPT ); Fri, 2 Sep 2016 09:11:10 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Robin Murphy , Felipe Balbi , Leo Li , Grygorii Strashko , Russell King - ARM Linux , Catalin Marinas , Yoshihiro Shimoda , "linux-usb@vger.kernel.org" , Sekhar Nori , lkml , Stuart Yoder , Scott Wood , David Fisher , "Thang Q. Nguyen" , Alan Stern , Greg Kroah-Hartman Subject: Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev Date: Fri, 02 Sep 2016 15:10:34 +0200 Message-ID: <5224196.iEv3ICfjjt@wuerfel> User-Agent: KMail/5.1.3 (Linux/4.4.0-34-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: <956cf653-973a-3bfd-9aaa-bdc922995ea6@arm.com> References: <87eg528te7.fsf@linux.intel.com> <956cf653-973a-3bfd-9aaa-bdc922995ea6@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:EyhhxhUVOr/G1R9NPmtyFVvCfLe5uZW0AVksOMANNBxgvNAivna r5+dPDNcxi35Yzly6LHos5phZbW6lniHytyQNyWaXHeMHYpZQNDI9Njc9wH+k+5XzjLTCCQ 16tP/IMmAoA2E/e6AffEtsO0Fm98ewtb8zI3x/kQf/PbYeS3Q1iGAaGc7RTdJMoD+lnS4rk w9wt+becyNDyIR5WvgOBQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:eBBbG5ClZ/o=:F878ZZ8TkudaxcbPyaTHbI ZUrFvA0PFAooU2HkYf5PDqK5lC7mIiyhVJDTjyC2tZo2HZNmb1Rh4rMmVZgOm3w/E9asALr40 NEzP/gKnoWFLXcxYAJX2JJXYK4EE19wVElDLnsi+SLUIEMqtb3NDmJEi7lwC+kOscLdMxhMid tCJwvgU/oWLZ/1aW0gkZt2MGPf5kzxR8hc2RyB7VlXcXLo7/alz+/AaDy1LbG8hAfEjpXqlIW ZX4ubMy6oMVQCflyI3w/iYPSbf+3QqDXRbcnt7n0+Uol0/EczPlQGXbNV1lNYK/6HLeiLY0O2 y6fzNbtYmifn8GGLEBR2CHLVQwhs1hPYxQ9MIzwfsSAmeWwF1Tijh4VUWTYq2etUBq8q17IYd GyFBgwvk/tSzvnLmO2Mez/j0PUK/JEA2Cr7Y/iApdf8uU83k7BFB1wGSgqK6u5t0H2VcnH15S FVjPKSEIFPLTNq+cdWdMusoNW0EL8vx3v/K8PeWG5MKDxDJqR9qO4C/GsL8kezASvhQssuWk4 3cMsEV5xYwTi+Lo75dQOV2eYXMu7wLCZTwrHCFN3OQBJsPJolUO64Mk3sNW3nu9uJ75SpLexN a2s4pSmwEJ6ikUkZfnpNofuSeud2MjBzTLszy6NwnLyO8mxeqmb4ZknaJ27OmoO4OKxA+0cQb /DleaSW9TUUJrJrHSJ70jbjZkBqQmN+26j8vV7lbEhqxzwq/kINzN58So8EctWXhP0yH12l49 l6VXUBTWTvzuT+85 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday, September 2, 2016 12:55:33 PM CEST Robin Murphy wrote: > > Huh? There's only no DMA description in DT if the device can be assumed > to be happy with the defaults. Anything else should be using > "dma-ranges", "dma-coherent", etc. to describe non-default integration > aspects. For devices with an inherent fixed addressing capability !=32 > bits, then it's down to the driver to call dma_set_mask() appropriately > to override the default 32-bit mask (which is not unique to OF-probed > devices either). The iommu configuration would be the main other one worth mentioning. Note that there is a known bug with dma_set_mask(), which always succeeds at the moment, even if the dma-ranges limit the possible addresses in a way that should fail. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Fri, 02 Sep 2016 15:10:34 +0200 Subject: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev In-Reply-To: <956cf653-973a-3bfd-9aaa-bdc922995ea6@arm.com> References: <87eg528te7.fsf@linux.intel.com> <956cf653-973a-3bfd-9aaa-bdc922995ea6@arm.com> Message-ID: <5224196.iEv3ICfjjt@wuerfel> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Friday, September 2, 2016 12:55:33 PM CEST Robin Murphy wrote: > > Huh? There's only no DMA description in DT if the device can be assumed > to be happy with the defaults. Anything else should be using > "dma-ranges", "dma-coherent", etc. to describe non-default integration > aspects. For devices with an inherent fixed addressing capability !=32 > bits, then it's down to the driver to call dma_set_mask() appropriately > to override the default 32-bit mask (which is not unique to OF-probed > devices either). The iommu configuration would be the main other one worth mentioning. Note that there is a known bug with dma_set_mask(), which always succeeds at the moment, even if the dma-ranges limit the possible addresses in a way that should fail. Arnd