From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S934014AbcIFKqh (ORCPT <rfc822;w@1wt.eu>);
        Tue, 6 Sep 2016 06:46:37 -0400
Received: from mout.kundenserver.de ([217.72.192.74]:58989 "EHLO
        mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752779AbcIFKqe (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 6 Sep 2016 06:46:34 -0400
From: Arnd Bergmann <arnd@arndb.de>
To: Felipe Balbi <balbi@kernel.org>
Cc: Peter Chen <hzpeterchen@gmail.com>, Leo Li <pku.leo@gmail.com>,
        Grygorii Strashko <grygorii.strashko@ti.com>,
        Russell King - ARM Linux <linux@arm.linux.org.uk>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
        "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
        Sekhar Nori <nsekhar@ti.com>, lkml <linux-kernel@vger.kernel.org>,
        Stuart Yoder <stuart.yoder@nxp.com>, Scott Wood <oss@buserror.net>,
        David Fisher <david.fisher1@synopsys.com>,
        "Thang Q. Nguyen" <tqnguyen@apm.com>,
        Alan Stern <stern@rowland.harvard.edu>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent dev
Date: Tue, 06 Sep 2016 12:46:06 +0200
Message-ID: <4416687.vUjZzKWZG6@wuerfel>
User-Agent: KMail/5.1.3 (Linux/4.4.0-34-generic; KDE/5.18.0; x86_64; ; )
In-Reply-To: <87bn01o7jg.fsf@linux.intel.com>
References: <Pine.LNX.4.44L0.1604271357190.1912-100000@iolanthe.rowland.org> <20160906063529.GA22312@b29397-desktop> <87bn01o7jg.fsf@linux.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:XeDgPNUDW93ewBg7jumzXkOfk+3Lt8vAPq6dGijkHd48yy6Abxw
 bSkoS9rzh5GuRHfVmco/fHU+kiM0QdHnSZCq0OzODQrhT1KIf3O2ez6jKwPIrEqavrylcvt
 wHWZi9z66tNt54yfxeq96Q4xA+ZO58Eu2s5g/es3Q6z96eCKSrvId9pEArHy12s1e9fh7J0
 oGH6PKE6bJ3A+bBL2taVA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:S95xRkJGbuA=:QRDSr5CGbPNHF2/lcID81o
 snSk+Jzjh+FNau0SyDfzgRE2/6JYZlZFcxt8o47muiw9knFPk8oTBMjuygbsc1bIFLAaaBAWC
 q/Wj/73z+8ZDfg/KkRl5cURGRNLM5RR+r/CfL+OydMfWJaRjY/znsp45wMxyTSQiwU76rshSG
 qJ3Vy99v+cFE1elERbzKqE8ERNwkRuBJ1B7d4kC2/NIIOLgQSj5BpxPWX3XWmxWDY0+ilGUO5
 NZjykYcf/HpCTO3Wbt/0lRkRQ90Jxiv9poAlTAFLaDZx//VLR4cZ/v8KFqJFcWAxwCFSmXF4a
 TiDcAhfrYcHJ7fI9506wftWIWaH9UnLN4VdHGvyjaTiTmHk0MXQM6qjNnAT3PbJBUqyf6c7Ht
 +aD1THysYw98DquQPpVXCnUB25+r0mOgsMlYjLKm13aMNuJsEAiGIc3pwLP+EZjqNAcIWh0t2
 AmFq1WS1Nqr5OvVbxwnrvk3DIxSmWfWtjBLyztWLFl4izxCa4nUClcyqkW8I2nYwOJmXn43Gw
 dTFCnUSOtA8ON0HtRGc0dfnfh7F6qF7R6ltXIZOvWjI7zW3J7o65iH0EQ6kB8M+zK2htXYQpU
 SrtaB0uTNHm6Rzz2t+QQF0wWBWR3rypB52NutFrkpwg5eHriLkhN16/+LP2zg7Y5c+TcAKqFs
 lyxDQzEn52COCjIamh8TPI4MOnRjTxqXMQ6XpV6S/9Q41XXvoCuXFKxCql79Dwb+7LWf646Dj
 YW+kgtHxJYefjxST
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tuesday, September 6, 2016 9:40:19 AM CEST Felipe Balbi wrote:
> 
> this only solves the problem for DT devices. Legacy devices and
> PCI-based systems will still suffer from the same problem. At least for
> dwc3, I will only be taking patches that solve the problem for all
> users, not a subset of them.

I don't think legacy devices are a worry, because they wouldn't
have this problem. For the PCI case, you are right that it cannot
work, in particular for machines that have complex IOMMU setup.

Some architectures (at least arm64 and sparc) check the bus_type of
a device in order to find the correct set of dma_map_ops for that
device, so there is no real way to handle this as long as you
pass a platform_device into an API that expects a pci_device.

	Arnd