From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx114.postini.com [74.125.245.114]) by kanga.kvack.org (Postfix) with SMTP id F1F0C6B0044 for ; Fri, 30 Mar 2012 03:14:59 -0400 (EDT) Received: by pbcup15 with SMTP id up15so1566095pbc.14 for ; Fri, 30 Mar 2012 00:14:59 -0700 (PDT) Message-ID: <4F755D67.5020802@gmail.com> Date: Fri, 30 Mar 2012 12:44:47 +0530 From: Subash Patel MIME-Version: 1.0 Subject: Re: [PATCHv7 9/9] ARM: dma-mapping: add support for IOMMU mapper References: <1330527862-16234-1-git-send-email-m.szyprowski@samsung.com> <1330527862-16234-10-git-send-email-m.szyprowski@samsung.com> <4F688B2D.20808@gmail.com> <4F6B304E.5010402@gmail.com> In-Reply-To: <4F6B304E.5010402@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: KyongHo Cho Cc: Marek Szyprowski , linux-arm-kernel@lists.infradead.org, linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-samsung-soc@vger.kernel.org, iommu@lists.linux-foundation.org, Shariq Hasnain , Arnd Bergmann , Benjamin Herrenschmidt , Krishna Reddy , Kyungmin Park , Andrzej Pietrasiewicz , Russell King - ARM Linux , Chunsang Jeong Hi KyongHo, On 03/22/2012 07:29 PM, Subash Patel wrote: > Hi KyongHo, > > On 03/21/2012 05:26 AM, KyongHo Cho wrote: >> On Tue, Mar 20, 2012 at 10:50 PM, Subash Patel wrote: >>> Sorry for digging this very late. But as part of integrating dma_map v7& >>> sysmmu v12 on 3.3-rc5, I am facing below issue: >>> >>> a) By un-selecting IOMMU in menu config, I am able to allocate memory in >>> vb2-dma-contig >>> >>> b) When I enable SYSMMU support for the IP's, I am receiving below >>> fault: >>> >>> Unhandled fault: external abort on non-linefetch (0x818) at 0xb6f55000 >>> >>> I think this has something to do with the access to the SYSMMU >>> registers for >>> writing the page table. Has anyone of you faced this issue while testing >>> these(dma_map+iommu) patches on kernel mentioned above? This must be >>> something related to recent changes, as I didn't have issues with these >>> patches on 3.2 kernel. >>> >> >> 0xb6f55000 is not an address of SYSMMU register if your kernel starts >> at 0xc0000000. >> >> Can you tell me any detailed information or situation? > I hate to say this, but I am not able to catch the fault location even > with JTAG. Once the fault comes, the debugger looses all control over. I > think now possible method is reproduction at your end :) Thanks to you, Issue is now figured out. This was due to generic Power Domain code added recently. SYSMMU registers were not getting enabled due to this. I reverted the PD changes from the machine to architecture specific, and voila, SYSMMU is back into action using the dma-mapping-v7. I will have to see how the same would behave when the complete PD changes comes to mainline from maintainers for-next in future. >> >> Regards, >> >> KyongHo. > Regards, > Subash Regards, Subash -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org