Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752457AbbKJWJr (ORCPT ); Tue, 10 Nov 2015 17:09:47 -0500 Received: from mout.kundenserver.de ([212.227.126.131]:60628 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752416AbbKJWJm (ORCPT ); Tue, 10 Nov 2015 17:09:42 -0500 From: Arnd Bergmann To: Timur Tabi Cc: Sinan Kaya , linux-arm-kernel@lists.infradead.org, Abhijit Mahajan , Nagalakshmi Nandigama , linux-scsi@vger.kernel.org, jcm@redhat.com, "James E.J. Bottomley" , linux-kernel@vger.kernel.org, Sreekanth Reddy , Praveen Krishnamoorthy , cov@codeaurora.org, linux-arm-msm@vger.kernel.org, agross@codeaurora.org, MPT-FusionLinux.pdl@avagotech.com, Hannes Reinecke Subject: Re: [PATCH V2 1/3] scsi: mptxsas: try 64 bit DMA when 32 bit DMA fails Date: Tue, 10 Nov 2015 23:08:57 +0100 Message-ID: <5480219.RxDdMdtxQU@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <564268B6.9000204@codeaurora.org> References: <1447034266-28003-1-git-send-email-okaya@codeaurora.org> <4912471.TLsW7CIyYF@wuerfel> <564268B6.9000204@codeaurora.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:ABmzgEFovi2zkOBuLXR/fZTUlLpZXbSHPXQnJGEolyOoZbCOd9/ w4E85flD8gM0BCIHofQvF84wEviUMFURxo0TnRx4zrjXAqqIdW6+IBJ7a+DYumQnXFDPuNJ bBa/CajD+ekj+cpdgBSV0aQ39sRNCYuDPPnWhSqbHmJBZkg5gSyKuI/8fCzcOimaCk5HH3w hiJiFfcfx6CjN+rGgZdDA== X-UI-Out-Filterresults: notjunk:1;V01:K0:1j9WEBe2WAY=:8txBYWiO3uf74Rvea77NJo DtRv99uYoOMuGp3v3rCnzhd1g6emMUtTL6/B/Ky92yphJLpFqo51FEBcqVq4O3KrZBvIb9N8w eBOgzsSS7q6kj3GZWO/wV2hnFhwSFMKHXNJ2ndCWFsIrKBM8+8qgxefNZOTgNHVuxGU+4t+aO /aplKiU6aZVJIMDtbzbijaP/VJTgU7s3EFSDYOEqb2aYacv5RpOPI0TF07il+bmtsoojWvySo drpgzmUKeK4AHcGg/W16Bu0/OT7C5Xcp3I0M8B7dvt4ygPB02xu590ErcXSWsOfTjo9dyAG29 A2rfC2AS0mDdCCoseqniMWpQ2uUS5/v7Pb+Cl4H9CjDYEDbbsvBr7fJCG/M4mtqCw7fF11aN8 d4N40Rzg1FsBPGZLIr+NARZyEskpDL/tw7cZy2eBAD8cp0+h4+u6fnb/b3NtjHARWQTc7ICkD TVFvbG/L0Ms2JuKhDodN3GnRszoit0a6M41nqU1ItHPTovGZhLZA0r826+NsvcjJ9IxI8CbF/ eZRziKr2eolfy6oRUO7wy6+SZK5o2w+37kGJi4o7H3IlRhEuNhkNwGNrEQHfPkO/zA6WooI0Q ZDCACCxfcmtnd2w1Z3nlqUH18fAN/LtwTxcQ4MP0xPVS+WDNexidq0vyqX53615Et3JTRY0W/ IjfAdk1EDiW1tg/ri+NpfzCGHGWl069JwFpFQ6ZqG+k9z1+fTd6QfwtxDN2aoAzIJEIC+M7r+ IKVRAymaxETNlfZp Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1153 Lines: 30 On Tuesday 10 November 2015 15:59:18 Timur Tabi wrote: > On 11/10/2015 03:54 PM, Arnd Bergmann wrote: > > >> In our drivers for 32-bit devices, we have to explicitly set the DMA > >> mask to 32-bits in order to get any DMA working. > > > > Do you mean PCI devices or platform devices? > > Platform. > > > Maybe the parent bus is lacking a dma-ranges property? > > All of this applies only on device-tree platforms. Sinan and I are > working on an ACPI server platform. So we never call > of_dma_configure(), and we don't have a dma-ranges property. ACPI must have something else to mark DMA master devices and their capabilities, right? The platform should initialize the dma_mask pointer to a per-device mask and set both the dma_mask and dma_coherent_mask to 32 bits for any DMA master device, and the device driver should override that to be an appropriate mask based on its needs later. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/