From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E289EC3A5A1 for ; Wed, 28 Aug 2019 12:24:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B45A02339E for ; Wed, 28 Aug 2019 12:24:48 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=nifty.com header.i=@nifty.com header.b="uqNGtZWn" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726444AbfH1MYr (ORCPT ); Wed, 28 Aug 2019 08:24:47 -0400 Received: from conssluserg-03.nifty.com ([210.131.2.82]:61706 "EHLO conssluserg-03.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726413AbfH1MYr (ORCPT ); Wed, 28 Aug 2019 08:24:47 -0400 Received: from mail-ua1-f42.google.com (mail-ua1-f42.google.com [209.85.222.42]) (authenticated) by conssluserg-03.nifty.com with ESMTP id x7SCOKYn007536; Wed, 28 Aug 2019 21:24:21 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com x7SCOKYn007536 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1566995061; bh=QGwpmYKpkBfkJkR52bVEAkpX4zw0mwzUiEGIdCDkwxA=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=uqNGtZWnszkj+EI17b6cYBIkgLT1pNqqjZ5vvXHhv3nOtkGhMLE3vL239iHJx8xOz TSdYOHpkebqzZFAStQTcerRGirstT0XYJoVthR/5RvSg8EwIXbfT0K4YHHjnM2D9df JXXCqO9Sr2ZFEdHKD7gxA7eX9ABdy7xMFqUuoAjc4LZbh1oHbeSw+NQJ4Ce2UY37OL 1txXvkAUycDvn0IT3BeWg+7kqZstKdDcVVmHGUVKjLtz+pcmN6rubDhCpA5S2OJHzV Tbrl68C67rXttDBFRWfYe+B8o+XbJ2QlQQ11l4eNvd1Y5ZXbdFZLM/YI9cfIW6ibm1 bz9Dqz+XAfrPw== X-Nifty-SrcIP: [209.85.222.42] Received: by mail-ua1-f42.google.com with SMTP id k7so752114uao.6; Wed, 28 Aug 2019 05:24:21 -0700 (PDT) X-Gm-Message-State: APjAAAW009682rJRH8tQEgv1Esk44krWyPnCSSItIdEAEpNfL4gr+Dv4 stBJkAS+9IfqSqP8HOJvw3ng6jijQ1SL4k4NYfA= X-Google-Smtp-Source: APXvYqzOQYU2Q+Xq/DN7mTcKzBb0P1kiiE+ggL4N1BaGeuzN90KCZ6nzT8nGJkbkDhur/ilmD52mrtpqBPxR1Kulykg= X-Received: by 2002:ab0:442:: with SMTP id 60mr1554937uav.109.1566995060173; Wed, 28 Aug 2019 05:24:20 -0700 (PDT) MIME-Version: 1.0 References: <20190506223334.1834-1-nicoleotsuka@gmail.com> <20190506223334.1834-3-nicoleotsuka@gmail.com> <20190825011025.GA23410@lst.de> <20190826073320.GA11712@lst.de> <20190827075021.GA953@lst.de> <20190827115541.GB5921@lst.de> In-Reply-To: From: Masahiro Yamada Date: Wed, 28 Aug 2019 21:23:43 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 2/2] dma-contiguous: Use fallback alloc_pages for single pages To: Christoph Hellwig Cc: Nicolin Chen , linux-mmc , Ulf Hansson , Adrian Hunter , Robin Murphy , Marek Szyprowski , vdumpa@nvidia.com, Russell King , Catalin Marinas , Will Deacon , Chris Zankel , Max Filippov , Joerg Roedel , David Woodhouse , Tony Lindgren , Andrew Morton , Stephen Rothwell , Thierry Reding , Kees Cook , iamjoonsoo.kim@lge.com, Wolfram Sang , linux-arm-kernel , Linux Kernel Mailing List , linux-xtensa@linux-xtensa.org, iommu@lists.linux-foundation.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 28, 2019 at 7:53 PM Masahiro Yamada wrote: > > Hi Christoph, > > On Tue, Aug 27, 2019 at 8:55 PM Christoph Hellwig wrote: > > > > On Tue, Aug 27, 2019 at 06:03:14PM +0900, Masahiro Yamada wrote: > > > Yes, this makes my driver working again > > > when CONFIG_DMA_CMA=y. > > > > > > > > > If I apply the following, my driver gets back working > > > irrespective of CONFIG_DMA_CMA. > > > > That sounds a lot like the device simply isn't 64-bit DMA capable, and > > previously always got CMA allocations under the limit it actually > > supported. I suggest that you submit this quirk to the mmc maintainers. > > > I tested v5.2 and my MMC host controller works with > dma_address that exceeds 32-bit physical address. > > So, I believe my MMC device is 64-bit DMA capable. > > I am still looking into the code > to find out what was changed. I retract this comment. Prior to bd2e75633c8012fc8a7431c82fda66237133bf7e, the descriptor table for ADMA is placed within the 32-bit phys address range, not exceeds the 32-bit limit. Probably, my device is not 64-bit capable. I will talk to the hardware engineer, and check the hardware spec just in case. Thanks. -- Best Regards Masahiro Yamada From mboxrd@z Thu Jan 1 00:00:00 1970 From: Masahiro Yamada Subject: Re: [PATCH v2 2/2] dma-contiguous: Use fallback alloc_pages for single pages Date: Wed, 28 Aug 2019 21:23:43 +0900 Message-ID: References: <20190506223334.1834-1-nicoleotsuka@gmail.com> <20190506223334.1834-3-nicoleotsuka@gmail.com> <20190825011025.GA23410@lst.de> <20190826073320.GA11712@lst.de> <20190827075021.GA953@lst.de> <20190827115541.GB5921@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Christoph Hellwig Cc: Ulf Hansson , Tony Lindgren , Catalin Marinas , Will Deacon , Linux Kernel Mailing List , Max Filippov , Marek Szyprowski , Stephen Rothwell , Joerg Roedel , Russell King , Thierry Reding , linux-xtensa@linux-xtensa.org, Kees Cook , Nicolin Chen , Andrew Morton , linux-arm-kernel , Chris Zankel , Wolfram Sang , David Woodhouse , linux-mmc , Adrian Hunter , iommu@lists.linux-foundation.org, iamjoo List-Id: linux-mmc@vger.kernel.org On Wed, Aug 28, 2019 at 7:53 PM Masahiro Yamada wrote: > > Hi Christoph, > > On Tue, Aug 27, 2019 at 8:55 PM Christoph Hellwig wrote: > > > > On Tue, Aug 27, 2019 at 06:03:14PM +0900, Masahiro Yamada wrote: > > > Yes, this makes my driver working again > > > when CONFIG_DMA_CMA=y. > > > > > > > > > If I apply the following, my driver gets back working > > > irrespective of CONFIG_DMA_CMA. > > > > That sounds a lot like the device simply isn't 64-bit DMA capable, and > > previously always got CMA allocations under the limit it actually > > supported. I suggest that you submit this quirk to the mmc maintainers. > > > I tested v5.2 and my MMC host controller works with > dma_address that exceeds 32-bit physical address. > > So, I believe my MMC device is 64-bit DMA capable. > > I am still looking into the code > to find out what was changed. I retract this comment. Prior to bd2e75633c8012fc8a7431c82fda66237133bf7e, the descriptor table for ADMA is placed within the 32-bit phys address range, not exceeds the 32-bit limit. Probably, my device is not 64-bit capable. I will talk to the hardware engineer, and check the hardware spec just in case. Thanks. -- Best Regards Masahiro Yamada From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A458BC3A5A1 for ; Wed, 28 Aug 2019 12:24:56 +0000 (UTC) Received: from mail.linuxfoundation.org (mail.linuxfoundation.org [140.211.169.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 68BAD20856 for ; Wed, 28 Aug 2019 12:24:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=nifty.com header.i=@nifty.com header.b="fIzFW8bg" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 68BAD20856 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=socionext.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=iommu-bounces@lists.linux-foundation.org Received: from mail.linux-foundation.org (localhost [127.0.0.1]) by mail.linuxfoundation.org (Postfix) with ESMTP id 313362D7C; Wed, 28 Aug 2019 12:24:56 +0000 (UTC) Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1315E2D12 for ; Wed, 28 Aug 2019 12:24:37 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from conssluserg-06.nifty.com (conssluserg-06.nifty.com [210.131.2.91]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4E8398BC for ; Wed, 28 Aug 2019 12:24:36 +0000 (UTC) Received: from mail-vk1-f173.google.com (mail-vk1-f173.google.com [209.85.221.173]) (authenticated) by conssluserg-06.nifty.com with ESMTP id x7SCOLCG011134 for ; Wed, 28 Aug 2019 21:24:22 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-06.nifty.com x7SCOLCG011134 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1566995062; bh=QGwpmYKpkBfkJkR52bVEAkpX4zw0mwzUiEGIdCDkwxA=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=fIzFW8bgi8hLSJgmQBbOSUOLIa7CJMZyUJ8KYrwFi+QR8+2VLIWz8WUCiF0uHxCqJ NDlOLKYE+pIP9kvY4eP1Cf1N+zG+K/Z5egByhE5ywEY+MwiIT7X7smpgfyN5H2CpgQ OmDbS5xeEkkoGVbAWsK7sXSLSumlSSjs+MJHmxzCOk9n6csZ8O92BHxYUTx3F1p5M4 f+LqJ/1xJVheohby2PU1O8Nw7v88Hnx7F6zCTRQwBloI1uwQtl8DHmvZu12e0PyoqD u26s3Wc4v+dph34ijUwypiud4S3EifSgcGpo27MVDJ6oQhmaJu5p9QmgMCpQspwZo1 2+UrwxWshbpwQ== X-Nifty-SrcIP: [209.85.221.173] Received: by mail-vk1-f173.google.com with SMTP id b11so561788vkk.10 for ; Wed, 28 Aug 2019 05:24:22 -0700 (PDT) X-Gm-Message-State: APjAAAUKRI0IDWw7f4LVbGISqX16tq+hC3UM/E4dSxHx/Xrml1w5/QCW t6YvbmkFhIHHZPtDUnEOG3bbD5e1S31X6+FBS4U= X-Google-Smtp-Source: APXvYqzOQYU2Q+Xq/DN7mTcKzBb0P1kiiE+ggL4N1BaGeuzN90KCZ6nzT8nGJkbkDhur/ilmD52mrtpqBPxR1Kulykg= X-Received: by 2002:ab0:442:: with SMTP id 60mr1554937uav.109.1566995060173; Wed, 28 Aug 2019 05:24:20 -0700 (PDT) MIME-Version: 1.0 References: <20190506223334.1834-1-nicoleotsuka@gmail.com> <20190506223334.1834-3-nicoleotsuka@gmail.com> <20190825011025.GA23410@lst.de> <20190826073320.GA11712@lst.de> <20190827075021.GA953@lst.de> <20190827115541.GB5921@lst.de> In-Reply-To: From: Masahiro Yamada Date: Wed, 28 Aug 2019 21:23:43 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 2/2] dma-contiguous: Use fallback alloc_pages for single pages To: Christoph Hellwig Cc: Ulf Hansson , Tony Lindgren , Catalin Marinas , Will Deacon , Linux Kernel Mailing List , Max Filippov , Stephen Rothwell , Russell King , Thierry Reding , linux-xtensa@linux-xtensa.org, Kees Cook , Nicolin Chen , Andrew Morton , linux-arm-kernel , Chris Zankel , Wolfram Sang , David Woodhouse , linux-mmc , Adrian Hunter , iommu@lists.linux-foundation.org, iamjoonsoo.kim@lge.com, Robin Murphy X-BeenThere: iommu@lists.linux-foundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Development issues for Linux IOMMU support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: iommu-bounces@lists.linux-foundation.org Errors-To: iommu-bounces@lists.linux-foundation.org On Wed, Aug 28, 2019 at 7:53 PM Masahiro Yamada wrote: > > Hi Christoph, > > On Tue, Aug 27, 2019 at 8:55 PM Christoph Hellwig wrote: > > > > On Tue, Aug 27, 2019 at 06:03:14PM +0900, Masahiro Yamada wrote: > > > Yes, this makes my driver working again > > > when CONFIG_DMA_CMA=y. > > > > > > > > > If I apply the following, my driver gets back working > > > irrespective of CONFIG_DMA_CMA. > > > > That sounds a lot like the device simply isn't 64-bit DMA capable, and > > previously always got CMA allocations under the limit it actually > > supported. I suggest that you submit this quirk to the mmc maintainers. > > > I tested v5.2 and my MMC host controller works with > dma_address that exceeds 32-bit physical address. > > So, I believe my MMC device is 64-bit DMA capable. > > I am still looking into the code > to find out what was changed. I retract this comment. Prior to bd2e75633c8012fc8a7431c82fda66237133bf7e, the descriptor table for ADMA is placed within the 32-bit phys address range, not exceeds the 32-bit limit. Probably, my device is not 64-bit capable. I will talk to the hardware engineer, and check the hardware spec just in case. Thanks. -- Best Regards Masahiro Yamada _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 29A0CC3A5A1 for ; Wed, 28 Aug 2019 12:24:42 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id F01B320856 for ; Wed, 28 Aug 2019 12:24:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="ZTIGWwuU"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=nifty.com header.i=@nifty.com header.b="uqNGtZWn" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org F01B320856 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=socionext.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=9DiYvkfs9foF9oXGZfj/9JmnweuWi75HelZocBRieEs=; b=ZTIGWwuU10m6Ku y9wZMpEXBVyi/YzRScOXGidSN8/ntGMMZYk2+vCxue0oyp9s2cE2VCXJW8wQVUdONz/OLLkukqhA7 z01u3BZU1CblB+HVsL22zktSAHHpFuvo7a5IwHCIu1F8LaDbXsgWfQxfC1DWTVrj+b7l+/gbULB8m WooIqThXiTdZRfHCj2zrfT2gZdJmB7JK4F2wu6mohcgRmZFiehpBjlQ1WfYFnnsgfuV6uRRxh6gUP HvTxGaF5S6+PmjAvuEgiFOVUArymv4cEvn9hhMj9QskCCoIMY883shMF68J/j5SqxhzlK1nekH1Ri P8sj2BnYpx0lbjguTDnA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1i2x0D-0000ln-5r; Wed, 28 Aug 2019 12:24:41 +0000 Received: from conssluserg-05.nifty.com ([210.131.2.90]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1i2x09-0000lP-Dj for linux-arm-kernel@lists.infradead.org; Wed, 28 Aug 2019 12:24:39 +0000 Received: from mail-ua1-f54.google.com (mail-ua1-f54.google.com [209.85.222.54]) (authenticated) by conssluserg-05.nifty.com with ESMTP id x7SCOKsN031422 for ; Wed, 28 Aug 2019 21:24:21 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com x7SCOKsN031422 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1566995061; bh=QGwpmYKpkBfkJkR52bVEAkpX4zw0mwzUiEGIdCDkwxA=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=uqNGtZWnszkj+EI17b6cYBIkgLT1pNqqjZ5vvXHhv3nOtkGhMLE3vL239iHJx8xOz TSdYOHpkebqzZFAStQTcerRGirstT0XYJoVthR/5RvSg8EwIXbfT0K4YHHjnM2D9df JXXCqO9Sr2ZFEdHKD7gxA7eX9ABdy7xMFqUuoAjc4LZbh1oHbeSw+NQJ4Ce2UY37OL 1txXvkAUycDvn0IT3BeWg+7kqZstKdDcVVmHGUVKjLtz+pcmN6rubDhCpA5S2OJHzV Tbrl68C67rXttDBFRWfYe+B8o+XbJ2QlQQ11l4eNvd1Y5ZXbdFZLM/YI9cfIW6ibm1 bz9Dqz+XAfrPw== X-Nifty-SrcIP: [209.85.222.54] Received: by mail-ua1-f54.google.com with SMTP id x2so748501uar.8 for ; Wed, 28 Aug 2019 05:24:21 -0700 (PDT) X-Gm-Message-State: APjAAAVaRbYmIyzCDx/75J3mb9vv4Fh8Tqo3R9EnuuecKF5r0RMoDhVJ L8TwDYeMXORP36Tp09Jf+2IxyLST9405WHN0AFw= X-Google-Smtp-Source: APXvYqzOQYU2Q+Xq/DN7mTcKzBb0P1kiiE+ggL4N1BaGeuzN90KCZ6nzT8nGJkbkDhur/ilmD52mrtpqBPxR1Kulykg= X-Received: by 2002:ab0:442:: with SMTP id 60mr1554937uav.109.1566995060173; Wed, 28 Aug 2019 05:24:20 -0700 (PDT) MIME-Version: 1.0 References: <20190506223334.1834-1-nicoleotsuka@gmail.com> <20190506223334.1834-3-nicoleotsuka@gmail.com> <20190825011025.GA23410@lst.de> <20190826073320.GA11712@lst.de> <20190827075021.GA953@lst.de> <20190827115541.GB5921@lst.de> In-Reply-To: From: Masahiro Yamada Date: Wed, 28 Aug 2019 21:23:43 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 2/2] dma-contiguous: Use fallback alloc_pages for single pages To: Christoph Hellwig X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190828_052437_797438_B02B213D X-CRM114-Status: GOOD ( 18.49 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Ulf Hansson , Tony Lindgren , Catalin Marinas , Will Deacon , Linux Kernel Mailing List , Max Filippov , Marek Szyprowski , Stephen Rothwell , Joerg Roedel , Russell King , Thierry Reding , linux-xtensa@linux-xtensa.org, Kees Cook , Nicolin Chen , Andrew Morton , linux-arm-kernel , Chris Zankel , Wolfram Sang , David Woodhouse , linux-mmc , Adrian Hunter , iommu@lists.linux-foundation.org, iamjoonsoo.kim@lge.com, Robin Murphy Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Aug 28, 2019 at 7:53 PM Masahiro Yamada wrote: > > Hi Christoph, > > On Tue, Aug 27, 2019 at 8:55 PM Christoph Hellwig wrote: > > > > On Tue, Aug 27, 2019 at 06:03:14PM +0900, Masahiro Yamada wrote: > > > Yes, this makes my driver working again > > > when CONFIG_DMA_CMA=y. > > > > > > > > > If I apply the following, my driver gets back working > > > irrespective of CONFIG_DMA_CMA. > > > > That sounds a lot like the device simply isn't 64-bit DMA capable, and > > previously always got CMA allocations under the limit it actually > > supported. I suggest that you submit this quirk to the mmc maintainers. > > > I tested v5.2 and my MMC host controller works with > dma_address that exceeds 32-bit physical address. > > So, I believe my MMC device is 64-bit DMA capable. > > I am still looking into the code > to find out what was changed. I retract this comment. Prior to bd2e75633c8012fc8a7431c82fda66237133bf7e, the descriptor table for ADMA is placed within the 32-bit phys address range, not exceeds the 32-bit limit. Probably, my device is not 64-bit capable. I will talk to the hardware engineer, and check the hardware spec just in case. Thanks. -- Best Regards Masahiro Yamada _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel