From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753219AbbC1NYl (ORCPT <rfc822;w@1wt.eu>);
	Sat, 28 Mar 2015 09:24:41 -0400
Received: from mout.kundenserver.de ([212.227.17.10]:51249 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751396AbbC1NYj (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sat, 28 Mar 2015 09:24:39 -0400
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 2/4] mfd: lubbock_cplds: add lubbock IO board
Date: Sat, 28 Mar 2015 14:24:02 +0100
User-Agent: KMail/1.12.2 (Linux/3.19.0-10-generic; KDE/4.3.2; x86_64; ; )
Cc: Robert Jarzmik <robert.jarzmik@free.fr>,
        Nicolas Pitre <nicolas.pitre@linaro.org>,
        Mark Rutland <mark.rutland@arm.com>,
        "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
        Samuel Ortiz <sameo@linux.intel.com>, Pawel Moll <pawel.moll@arm.com>,
        Ian Campbell <ijc+devicetree@hellion.org.uk>,
        "Dmitry Eremin-Solenikov" <dbaryshkov@gmail.com>,
        "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
        linux-kernel@vger.kernel.org,
        Haojian Zhuang <haojian.zhuang@gmail.com>, devicetree@vger.kernel.org,
        Rob Herring <robh+dt@kernel.org>, Kumar Gala <galak@codeaurora.org>,
        Grant Likely <grant.likely@linaro.org>,
        Lee Jones <lee.jones@linaro.org>, Daniel Mack <daniel@zonque.org>
References: <20150216130549.GF14545@x1> <201503280335.16280.arnd@arndb.de> <87fv8pwmm0.fsf@free.fr>
In-Reply-To: <87fv8pwmm0.fsf@free.fr>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201503281424.02583.arnd@arndb.de>
X-Provags-ID: V03:K0:+rhUnEWACZSoK001Il3dufCokC+WlsexneDJluspvdIq5yukDpp
 02eksVyN5Zgcjyhr6AwwMduwU/1mAmlaVMSD8CL3wQ9fccgMhWnSDDtR89LJAHemRPcx7Ne
 pJ2GTMUhHrThruIZL1q8qAvsMuNrv+QUTFHYSQSfoFOdjbpwFKk6BN51wGTL5sgk5045PRE
 Gs/94DiyNIoKg4fldCBKg==
X-UI-Out-Filterresults: notjunk:1;
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Saturday 28 March 2015, Robert Jarzmik wrote:
> It's not as much a problem as a generic question : does a driver belong to
> arch/* ?
> 
> Personaly it would have been far simpler for me to have it through the pxa tree,
> but I want to be sure it's the right place. Others will follow, pxa mainstone is
> such a candidate.
> 
> I was thinking so far that arch/arm/mach-* was for machine description,
> ie. wirings, interconnections, initial setup etc ... The "driver" part, ie. code
> really driving dynamics in IPs was as per my understanding in drivers/...
> 
> Now I can create arch/arm/mach-pxa/lubbock_cplds.c, that won't make any
> difference to me, provided that it's the right thing to do.

If we had a lot of these, we would probably put them somewhere under drivers.
and find a maintainer for them. Given that this is an exceptional case for
an older machine, my feeling is that leaving the code in mach-pxa is the least
effort for now.

	Arnd