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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 3120FC433E7 for ; Fri, 9 Oct 2020 13:56:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EBF07222B9 for ; Fri, 9 Oct 2020 13:56:37 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="Hlz0T0HY" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387733AbgJIN4h (ORCPT ); Fri, 9 Oct 2020 09:56:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48228 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731374AbgJIN4g (ORCPT ); Fri, 9 Oct 2020 09:56:36 -0400 Received: from mail-il1-x144.google.com (mail-il1-x144.google.com [IPv6:2607:f8b0:4864:20::144]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 848E7C0613D5 for ; Fri, 9 Oct 2020 06:56:36 -0700 (PDT) Received: by mail-il1-x144.google.com with SMTP id t18so9203821ilo.12 for ; Fri, 09 Oct 2020 06:56:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:from:date:message-id:subject:to:cc; bh=6o6qPP8lMx7cYOKA/MqaKbaqIjCjGnaiLWr14rPl5P0=; b=Hlz0T0HYpcI1RmYPyeOF014dP7wq6mto4JOO5AQX3su3fh95zbsrdvX+wsqbFQFmuk o56RJq7SGR5KyYMNTqsQjirLof/hnJtOBvvKEwO9b1+TN3p0b4gl92toDcBj7VMPnn7/ 8tY2NMUR4+quoUAFnkcxw7tVy93kHmwxgOPAcTX7m1Uo+ZCdjtmxau9fhNb4E82Tq5ot B5nJJa8LIH8PryvenpUGFLf4m8Kd88gjuibR7FbKT1TrjSS9oz09MR1uncgkH+1kLLzz /FVRczFb6cSO2chHkoCGBoFXPEzehWoc1SQrPGaGcYlVCO8j83PhHkDjqmQt2j07l4cf 0s7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:from:date:message-id :subject:to:cc; bh=6o6qPP8lMx7cYOKA/MqaKbaqIjCjGnaiLWr14rPl5P0=; b=nv6QhUJoUGswRg5ktkKa5On+AULRbr9y7Uqb/pA+zfthWqhkRpYqNMaLFebBP6VihN ZM2Ly4mjig48qjZNoM78SNUVg1Clcxki8WDx5NX8VO0fcMBCP1e1zdNBTZMnuRbEZf5B SKD4OGt8H6WlJOsaL9OmzeQlq7LEWpoFaimE42XuhDPFTl1Mf7uPd1TisIrWdsmDiy14 pBMUWpPygfx1H0FMDRphrASWUdeYJ4pjNf+CFQ4ED3eF0ihkT+CKd7YZbSJWwoyvszAd BBdsWmZ6J+DBRTFGlS0S2tm4II3btr+2ZqDUn5InTmjJal/zHjL9hQFkZelhPOQTBC8Y nSpQ== X-Gm-Message-State: AOAM532mysdMCv6tlhAJPJUb7ENUb4oIOUmy/8atfidVleL4Tn5s9Kz5 Ud3l/wAA7owYVY+PhjahJk4iilHE+jfTyPWbSf4icA== X-Google-Smtp-Source: ABdhPJzUkvbAvYEa3k1BsUYozC/xotWpIsogjry89hwi8FrKRfRA/5IIZf6URsj+bAxUF2s9ybtiMe1E4JF5+OFqUys= X-Received: by 2002:a05:6e02:664:: with SMTP id l4mr11033643ilt.81.1602251795786; Fri, 09 Oct 2020 06:56:35 -0700 (PDT) MIME-Version: 1.0 References: <20200924090349.GF27174@8bytes.org> <20200924092546.GJ27174@8bytes.org> <20200924095629.GL27174@8bytes.org> From: Naresh Kamboju Date: Fri, 9 Oct 2020 19:26:24 +0530 Message-ID: Subject: Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables To: Joerg Roedel Cc: Robin Murphy , Poonam Aggrwal , Rob Herring , Joerg Roedel , Arnd Bergmann , Richard Weinberger , open list , lkft-triage@lists.linaro.org, "open list:IOMMU DRIVERS" , Linux-Next Mailing List , linux-mtd@lists.infradead.org, Miquel Raynal , Suram Suram , masonccyang@mxic.com.tw, Will Deacon , "Z.Q. Hou" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 9 Oct 2020 at 19:24, Naresh Kamboju wrote: > > > > On Thu, 24 Sep 2020 at 15:26, Joerg Roedel wrote: > > > > On Thu, Sep 24, 2020 at 10:36:47AM +0100, Robin Murphy wrote: > > > Yes, the issue was introduced by one of the changes in "dma-mapping: > > > introduce DMA range map, supplanting dma_pfn_offset", so it only existed in > > > the dma-mapping/for-next branch anyway. > FYI, The reported problem still exists on 5.9.0-rc8-next-20201009. [ 1.843814] Driver must set ecc.strength when using hardware ECC [ 1.849847] WARNING: CPU: 4 PID: 1 at drivers/mtd/nand/raw/nand_base.c:5687 nand_scan_with_ids+0x1450/0x1470 [ 1.859676] Modules linked in: [ 1.862730] CPU: 4 PID: 1 Comm: swapper/0 Not tainted 5.9.0-rc8-next-20201009 #1 [ 1.870125] Hardware name: Freescale Layerscape 2088A RDB Board (DT) [ 1.876478] pstate: 40000005 (nZcv daif -PAN -UAO -TCO BTYPE=--) [ 1.882483] pc : nand_scan_with_ids+0x1450/0x1470 [ 1.887183] lr : nand_scan_with_ids+0x1450/0x1470 full test log, https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20201009/testrun/3284876/suite/linux-log-parser/test/check-kernel-warning-92014/log > > > > Okay, alright then. > > - Naresh