Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756668Ab1BYAMI (ORCPT ); Thu, 24 Feb 2011 19:12:08 -0500 Received: from wolverine02.qualcomm.com ([199.106.114.251]:10023 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756632Ab1BYAMH (ORCPT ); Thu, 24 Feb 2011 19:12:07 -0500 X-IronPort-AV: E=McAfee;i="5400,1158,6267"; a="76336209" From: David Brown To: Daniel Walker Cc: Stepan Moskovchenko , linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] msm: iommu: Create a Kconfig item for the IOMMU driver In-Reply-To: <1297799373.7088.5.camel@c-dwalke-linux.qualcomm.com> (Daniel Walker's message of "Tue, 15 Feb 2011 11:49:33 -0800") References: <1297456098-3241-1-git-send-email-stepanm@codeaurora.org> <1297456729.4852.9.camel@m0nster> <8yar5b9850l.fsf@huya.qualcomm.com> <1297799373.7088.5.camel@c-dwalke-linux.qualcomm.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-Hashcash: 1:20:110225:dwalker@fifo99.com::QQvzxIamwIRxTd2F:00000000000000000000000000000000000000000001T3n X-Hashcash: 1:20:110224:linux-arm-kernel@lists.infradead.org::AM3du73FOAuBHT3u:00000000000000000000000000MPY X-Hashcash: 1:20:110224:stepanm@codeaurora.org::moB1CHSIksNKaIG6:0000000000000000000000000000000000000000bPE X-Hashcash: 1:20:110224:linux-arm-msm@vger.kernel.org::zavbmY+iQzPPIvOx:000000000000000000000000000000001Fba X-Hashcash: 1:20:110224:linux-kernel@vger.kernel.org::07+1Esf7nmw8eTjD:0000000000000000000000000000000001CTB Date: Thu, 24 Feb 2011 16:12:06 -0800 Message-ID: <8yay655c6qx.fsf@huya.qualcomm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2014 Lines: 48 On Tue, Feb 15 2011, Daniel Walker wrote: > Typically we include everything the SoC has regardless of if drivers use > the hardware or not . For instance there could be modules that use the > hardware .. > > Regardless of this point, I've nacked the whole series. It looks like > there was very little thought put into this. I want to try to resolve this particular series. I had originally pulled the series in because I thought everything had been addressed, you followed this with a generic NAK. You raised a couple of issues: - Should this be configurable? I responded that our iommu is optional. Drivers will work whether the iommu is enabled or not. Other architectures have configurable iommu drivers (and some are selected). For example: arm/plat-s5p, powerpc/pasemi, as well x86. One reason to disable may be for building a slimmed kernel for kexec. - Should the iommu driver be under arch/arm/mach-msm. As discussed in , iommu drivers fall into kind of a grey area. Currently, most platform iommu drivers are in arch specific directories. - The renaming of the device file. At this point, the two MSM chips that have an IOMMU have an identical IOMMU configuration. The patches reflect this by removing the soc name from the file. Future chips will probably have iommu hardware that differs, but it isn't possible to predict what the differences will be, so that will have to be addressed then. I can certainly back out the changes if necessary. Please let me know if you have any specific concerns. David -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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/