Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables

2020-10-09 Thread Naresh Kamboju
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: >

Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables

2020-10-09 Thread Naresh Kamboju
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

arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables

2020-09-21 Thread Naresh Kamboju
arm64 Freescale Layerscape 2088A RDB Board boot failed with linux-next 5.9.0-rc5-next-20200921 kernel tag version. The kernel warning and then kernel panic happened. Reported-by: Naresh Kamboju metadata: git branch: master git repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next

Re: [Freedreno] arm64: Internal error: Oops: qcom_iommu_tlb_inv_context free_io_pgtable_ops on db410c

2020-07-20 Thread Naresh Kamboju
On Mon, 20 Jul 2020 at 21:27, Rob Clark wrote: > > On Mon, Jul 20, 2020 at 4:28 AM Robin Murphy wrote: > > > > On 2020-07-20 08:17, Arnd Bergmann wrote: > > > On Mon, Jul 20, 2020 at 8:36 AM Naresh Kamboju > > > wrote: <> > > >> [5.44412

Re: [PATCH] iommu/qcom: Use domain rather than dev as tlb cookie

2020-07-20 Thread Naresh Kamboju
nline master and boot test PASS on db410c. The reported problem got fixed. > > [1] https://lkml.org/lkml/2020/7/20/104 > > Signed-off-by: Rob Clark Reported-by: Naresh Kamboju Tested-by: Naresh Kamboju > --- > Note I don't have a good setup to test this atm, but

arm64: Internal error: Oops: qcom_iommu_tlb_inv_context free_io_pgtable_ops on db410c

2020-07-19 Thread Naresh Kamboju
This kernel oops while boot linux mainline kernel on arm64 db410c device. metadata: git branch: master git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git commit: f8456690ba8eb18ea4714e68554e242a04f65cff git describe: v5.8-rc5-48-gf8456690ba8e make_kernelver

drivers/iommu/qcom_iommu.c:348 qcom_iommu_domain_free+0x5c/0x70

2020-02-18 Thread Naresh Kamboju
We have noticed these kernel warnings on APQ 8016 SBC (dragonboard 410c ) running stable rc 5.5, 5.4 branches and linux mainline and linux-next master branches. This warning started happening from linux mainline 5.3 onwards (2019-08-29) [5.488128] [ cut here ] [5.

Re: dma-direct: don't check swiotlb=force in dma_direct_map_resource

2020-01-07 Thread Naresh Kamboju
Following build error on stable-rc 5.4.9-rc1 for arm architecture. dma/direct.c: In function 'dma_direct_possible': dma/direct.c:329:3: error: too many arguments to function 'dma_capable' dma_capable(dev, dma_addr, size, true); ^~~ In file included from /srv/oe/build/tmp-lkft-glibc/w