Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754754Ab3JHCUZ (ORCPT ); Mon, 7 Oct 2013 22:20:25 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:36062 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754060Ab3JHCUV (ORCPT ); Mon, 7 Oct 2013 22:20:21 -0400 Date: Mon, 7 Oct 2013 19:19:41 -0700 From: Greg Kroah-Hartman To: Rohit Vaswani Cc: Olof Johansson , linux-arm-msm@vger.kernel.org, Russell King - ARM Linux , Linux Kernel list , "linux-arm-kernel@lists.infradead.org" , Kumar Gala Subject: Re: Use of drivers/platform and matching include? Message-ID: <20131008021941.GA9427@kroah.com> References: <20131004114128.GL12758@n2100.arm.linux.org.uk> <20131004132209.GB23923@kroah.com> <20131005171323.GB5780@kroah.com> <52535151.2000508@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52535151.2000508@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1754 Lines: 38 On Mon, Oct 07, 2013 at 05:26:57PM -0700, Rohit Vaswani wrote: > On 10/5/2013 10:13 AM, Greg Kroah-Hartman wrote: > > On Fri, Oct 04, 2013 at 09:48:41AM -0700, Olof Johansson wrote: > >> On Fri, Oct 4, 2013 at 6:22 AM, Greg Kroah-Hartman > >> wrote: > >>> On Fri, Oct 04, 2013 at 12:41:28PM +0100, Russell King - ARM Linux wrote: > >>>> So, no, there will be no new drivers under arch/arm. They must be in the > >>>> drivers subtree somewhere. > >>> I have no objection with this, and encourage it. > >> Ok, so these are some of the requirements as far as I see it: > >> > >> * No per-vendor driver dumping ground under drivers/* (i.e. no > >> drivers/platform//) > > Yes. > > We agree that there is no need for a dump *all* drivers under > arm/mach-foo in drivers/platform/foo/. The msm bus driver would be added > under drivers/bus/. But, we still have some drivers which are quite SoC > specific and not in the general category of the sub-directories present > under drivers. > As Kumar mentioned earlier - > > An example driver would be the means we utilize to communicate memory > regions between various HW blocks on the SoC. So a video/media core > driver might need access to a header/functions from the memory region > driver. > > Would drivers/misc/qcom-* or drivers/misc/qcom/* be a reasonable place > to add them ? and the headers could go into include/linux/qcom-*.h That seems reasonable, but I'd have to see the code to verify this. greg k-h -- 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/