Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756170Ab1BOTuN (ORCPT ); Tue, 15 Feb 2011 14:50:13 -0500 Received: from wolverine01.qualcomm.com ([199.106.114.254]:20989 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755353Ab1BOTuL (ORCPT ); Tue, 15 Feb 2011 14:50:11 -0500 X-IronPort-AV: E=McAfee;i="5400,1158,6258"; a="74579298" Subject: Re: [PATCH 1/3] msm: iommu: Create a Kconfig item for the IOMMU driver From: Daniel Walker To: David Brown Cc: Stepan Moskovchenko , linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org In-Reply-To: <8yar5b9850l.fsf@huya.qualcomm.com> References: <1297456098-3241-1-git-send-email-stepanm@codeaurora.org> <1297456729.4852.9.camel@m0nster> <8yar5b9850l.fsf@huya.qualcomm.com> Content-Type: text/plain; charset="UTF-8" Date: Tue, 15 Feb 2011 11:49:33 -0800 Message-ID: <1297799373.7088.5.camel@c-dwalke-linux.qualcomm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1594 Lines: 42 On Tue, 2011-02-15 at 11:35 -0800, David Brown wrote: > On Fri, Feb 11 2011, Daniel Walker wrote: > > > On Fri, 2011-02-11 at 12:28 -0800, Stepan Moskovchenko wrote: > >> +config MSM_IOMMU > >> + bool "MSM IOMMU Support" > >> + depends on ARCH_MSM8X60 > >> + select IOMMU_API > >> + default n > >> + help > >> + Support for the IOMMUs found on certain Qualcomm SOCs. > >> + These IOMMUs allow virtualization of the address space used by most > >> + cores within the multimedia subsystem. > >> + > >> + If unsure, say N here. > > > > I think you should just make this a hidden option, unless there is a > > good reason why any given users might want to turn this off. > > In this particular case, the driver is optional, even devices that use > it will be able to work both with and without it. It makes sense to be > able to decide whether to have it or not. 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. Daniel -- Sent by a consultant 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/