Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752100Ab2HTSB7 (ORCPT ); Mon, 20 Aug 2012 14:01:59 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:57494 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751732Ab2HTSBz (ORCPT ); Mon, 20 Aug 2012 14:01:55 -0400 Message-ID: <50327B8F.3050503@gmail.com> Date: Mon, 20 Aug 2012 20:01:51 +0200 From: Sebastian Hesselbarth User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.5) Gecko/20120624 Icedove/10.0.5 MIME-Version: 1.0 To: Thomas Petazzoni CC: Linus Walleij , Grant Likely , Rob Herring , Rob Landley , Russell King , Lior Amsalem , Andrew Lunn , Gregory CLEMENT , Ben Dooks , devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Stephen Warren Subject: Re: [PATCH 04/11] pinctrl: mvebu: add pinctrl driver for Armada 370 References: <1344689809-6223-1-git-send-email-sebastian.hesselbarth@gmail.com> <1344689809-6223-5-git-send-email-sebastian.hesselbarth@gmail.com> <50326A60.1070007@gmail.com> <20120820193622.4e539451@skate> In-Reply-To: <20120820193622.4e539451@skate> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1276 Lines: 32 On 08/20/2012 07:36 PM, Thomas Petazzoni wrote: > In order to keep the consistency with other SoC families, maybe we can > split the 370 and XP options in two separate MACH_ARMADA_370 and > MACH_ARMADA_XP. So, in the ideal world, once all Marvell EBU SoCs are > converted to DT+mach-mvebu, we should have: > > *) arch/arm/Kconfig defines MACH_MVEBU > > *) arch/arm/mach-mvebu/Kconfig defines MACH_KIRKWOOD, MACH_DOVE, > MACH_MX78X00, MACH_ARMADA_370, MACH_ARMADA_XP, MACH_ORION5X > > Then, an user is free to build a single kernel image that supports all, > or a selection of the supported Marvell EBU SoCs. > > Would that be ok with you? Yes! > If that's fine with you, then I would prefer if we keep the single > MACH_ARMADA_370_XP symbol for now, so that your pinctrl set of patches > does not depend on something else. We would do the small Kconfig option > refactoring as a follow-up set of patches. Thoughts? Despite any objections, I will remove all arch/arm/*/Kconfig patches from pinctrl patch set. Sebastian -- 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/