Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758062Ab2ECR6f (ORCPT ); Thu, 3 May 2012 13:58:35 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:33344 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754345Ab2ECR6d (ORCPT ); Thu, 3 May 2012 13:58:33 -0400 Message-ID: <4FA2C746.5080000@wwwdotorg.org> Date: Thu, 03 May 2012 11:58:30 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.28) Gecko/20120313 Thunderbird/3.1.20 MIME-Version: 1.0 To: Hiroshi DOYU CC: linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Joerg Roedel , Thierry Reding , linux-kernel@vger.kernel.org Subject: Re: [PATCHv3 3/4] iommu/tegra: smmu: Refrain from accessing to AHB References: <1336061147-10245-1-git-send-email-hdoyu@nvidia.com> <1336061147-10245-3-git-send-email-hdoyu@nvidia.com> <4FA2C4E9.2080509@wwwdotorg.org> In-Reply-To: <4FA2C4E9.2080509@wwwdotorg.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1578 Lines: 34 On 05/03/2012 11:48 AM, Stephen Warren wrote: > On 05/03/2012 10:05 AM, Hiroshi DOYU wrote: >> Use "tegra_ahb_enable_smmu()" to inform AHB that SMMU is >> ready, instead of directly aceessing AHB registers. Oh, that should be "accessing". >> @@ -911,14 +899,16 @@ static int tegra_smmu_probe(struct platform_device *pdev) > >> + smmu->ahb = of_parse_phandle(pdev->dev.of_node, "ahb", 0); > > Hmm, "ahb" should probably be "nvidia,ahb". > > I see that neither this patch nor the next patch include binding > documentation that describe this property. Can you please add documentation. Oh, the next patch is just adding the entry to the .dtsi file for the AHB, so no surprise it doesn't add a binding document for the SMMU! I see that with this patch, the driver still expects the DMA window to be represented as a reg property (IORESOURCE_MEM), so if we add a binding document to this patch it won't be very consistent either:-( And then, there's the issue of whether the SMMU should be it's own device or a child of some MC device, since there's non-SMMU functionality in these registers too. This makes all the SMMU rework need a little more thought. So, I propose dropping this patch from this series, since this series is all about adding the AHB driver. We should move this patch to a series relating to the SMMU driver. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/