From: Florian Fainelli <f.fainelli@gmail•com>
To: Jim Quinlan <james.quinlan@broadcom•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
abhimanyu.saini@nxp•com, Ioana Ciornei <ioana.ciornei@nxp•com>,
Fabio Estevam <festevam@gmail•com>
Cc: Naresh Kamboju <naresh.kamboju@linaro•org>,
Joerg Roedel <joro@8bytes•org>,
Robin Murphy <robin.murphy@arm•com>,
Poonam Aggrwal <poonam.aggrwal@nxp•com>,
Rob Herring <robh@kernel•org>, Joerg Roedel <jroedel@suse•de>,
Arnd Bergmann <arnd@arndb•de>,
Richard Weinberger <richard@nod•at>,
open list <linux-kernel@vger•kernel.org>,
lkft-triage@lists•linaro.org,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
linux-mtd@lists•infradead.org,
Miquel Raynal <miquel.raynal@bootlin•com>,
Suram Suram <suram@nxp•com>,
masonccyang@mxic•com.tw, Will Deacon <will@kernel•org>,
"Z.Q. Hou" <Zhiqiang.Hou@nxp•com>, Christoph Hellwig <hch@lst•de>
Subject: Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables
Date: Sun, 11 Oct 2020 14:59:02 -0700 [thread overview]
Message-ID: <c7e7b9ab-95a8-625f-7988-7f7397a0749f@gmail.com> (raw)
In-Reply-To: <CA+-6iNwpFeJaa7CisS-DD2q45uaV8Jz6YU0kPucqpZAAK3ojuQ@mail.gmail.com>
+Abhimanyu, Ioana, Fabio
On 10/11/2020 1:36 PM, Jim Quinlan wrote:
> On Sat, Oct 10, 2020 at 2:53 PM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>>
>> Hi Naresh,
>>
>> Just adding Christoph and Jim to cc]
>>
>> On Fri, 9 Oct 2020 19:26:24 +0530 Naresh Kamboju <naresh.kamboju@linaro•org> wrote:
>>>
>>> On Fri, 9 Oct 2020 at 19:24, Naresh Kamboju <naresh.kamboju@linaro•org> wrote:
>>>>
>>>>
>>>>
>>>> On Thu, 24 Sep 2020 at 15:26, Joerg Roedel <joro@8bytes•org> 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
>
> Hi,
>
> I'm having a hard time coming up with a theory regarding how a commit
> concerning DMA offsets can affect the operation of a NAND driver that
> appears not to use DMA or the dma-ranges property. Does anyone else
> have some ideas, or is there perhaps someone familiar with this test
> configuration that I can correspond with to get to the bottom of the
> warning?
I believe you are given only a partial warning and just a glimpse of the
thread here which is why understanding the connection to the dma ranges
parsing is not clear. The start of the thread can be found here:
https://lore.kernel.org/lkml/CA+G9fYvuq58q+GsWnzni0sKSHbubuQz-UaK3TASX26V_a7yBVw@mail.gmail.com/
Robin indicated that the IOMMU probe failure was fixed with:
https://lore.kernel.org/linux-iommu/daedc9364a19dc07487e4d07b8768b1e5934abd4.1600700881.git.robin.murphy@arm.com/T/#u
which is confirmed with the new log from Naresh:
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20201009/testrun/3284876/suite/linux-log-parser/test/check-kernel-warning-92014/log
however the NAND warning still remains. Someone else familiar with these
NXP development boards should fix the DTS so as to provide the require
ECC strength property.
--
Florian
next prev parent reply other threads:[~2020-10-11 21:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 13:20 arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables Naresh Kamboju
2020-09-21 14:51 ` Robin Murphy
2020-09-24 9:03 ` Joerg Roedel
2020-09-24 9:08 ` Robin Murphy
2020-09-24 9:25 ` Joerg Roedel
2020-09-24 9:36 ` Robin Murphy
2020-09-24 9:56 ` Joerg Roedel
2020-10-09 13:54 ` Naresh Kamboju
2020-10-09 13:56 ` Naresh Kamboju
2020-10-10 18:53 ` Stephen Rothwell
2020-10-11 20:36 ` Jim Quinlan
2020-10-11 21:59 ` Florian Fainelli [this message]
2020-10-14 12:28 ` Fabio Estevam
2020-10-14 12:58 ` Miquel Raynal
2020-10-15 7:48 ` Christoph Hellwig
2020-10-15 18:17 ` Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c7e7b9ab-95a8-625f-7988-7f7397a0749f@gmail.com \
--to=f.fainelli@gmail$(echo .)com \
--cc=Zhiqiang.Hou@nxp$(echo .)com \
--cc=abhimanyu.saini@nxp$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=festevam@gmail$(echo .)com \
--cc=hch@lst$(echo .)de \
--cc=ioana.ciornei@nxp$(echo .)com \
--cc=james.quinlan@broadcom$(echo .)com \
--cc=joro@8bytes$(echo .)org \
--cc=jroedel@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=masonccyang@mxic$(echo .)com.tw \
--cc=miquel.raynal@bootlin$(echo .)com \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=poonam.aggrwal@nxp$(echo .)com \
--cc=richard@nod$(echo .)at \
--cc=robh@kernel$(echo .)org \
--cc=robin.murphy@arm$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=suram@nxp$(echo .)com \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox