From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754796Ab3KTS7i (ORCPT ); Wed, 20 Nov 2013 13:59:38 -0500 Received: from mo1.mail-out.ovh.net ([178.32.228.1]:34997 "EHLO mo1.mail-out.ovh.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754424Ab3KTS7h (ORCPT ); Wed, 20 Nov 2013 13:59:37 -0500 Message-ID: <528CE3E6.1040802@overkiz.com> Date: Wed, 20 Nov 2013 17:31:34 +0100 From: boris brezillon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Jean-Christophe PLAGNIOL-VILLARD CC: Rob Herring , Pawel Moll , Mark Rutland , Stephen Warren , Ian Campbell , Russell King , Nicolas Ferre , Joachim Eastwood , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 8/9] ARM: at91/dt: add new at91rm9200ek_mmc board References: <1377687640-10529-1-git-send-email-b.brezillon@overkiz.com> <1377693456-11133-1-git-send-email-b.brezillon@overkiz.com> <20131120150255.GH14627@ns203013.ovh.net> In-Reply-To: <20131120150255.GH14627@ns203013.ovh.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Ovh-Tracer-Id: 16435886841158793388 X-Ovh-Remote: 80.245.18.66 () X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-OVH-SPAMSTATE: OK X-OVH-SPAMSCORE: -100 X-OVH-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeeiledrjedvucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd X-Spam-Check: DONE|U 0.5/N X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeeiledrjedvucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/11/2013 16:02, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 14:37 Wed 28 Aug , Boris BREZILLON wrote: >> Add a new at91rm9200ek_mmc board (based on at91rm9200ek board) which enables >> mmc0/slot0. > no for multiple dts > > this need to handle at user space level You mean, by controlling the regulator using the sysfs interface, or by loading only the appropriate driver ? What if both drivers are loaded (or not compiled as modules) ? This will lead to one device being unusable (and maybe even worst)... Please explain what you had in mind ? > > Best Regards, > J. >> Signed-off-by: Boris BREZILLON >> --- >> arch/arm/boot/dts/at91rm9200ek_mmc.dts | 23 +++++++++++++++++++++++ >> 1 file changed, 23 insertions(+) >> create mode 100644 arch/arm/boot/dts/at91rm9200ek_mmc.dts >> >> diff --git a/arch/arm/boot/dts/at91rm9200ek_mmc.dts b/arch/arm/boot/dts/at91rm9200ek_mmc.dts >> new file mode 100644 >> index 0000000..c87a861 >> --- /dev/null >> +++ b/arch/arm/boot/dts/at91rm9200ek_mmc.dts >> @@ -0,0 +1,23 @@ >> +/* >> + * at91rm9200ek.dts - Device Tree file for Atmel AT91RM9200 evaluation kit with >> + * an MMC slot >> + * >> + * Copyright (C) 2013 Boris BREZILLON >> + * >> + * Licensed under GPLv2 only >> + */ >> +/dts-v1/; >> +#include "at91rm9200ek.dts" >> + >> +/ { >> + model = "Atmel AT91RM9200 evaluation kit with MMC slot"; >> + compatible = "atmel,at91rm9200ek-mmc", "atmel,at91rm9200ek", "atmel,at91rm9200"; >> + >> + ahb { >> + apb { >> + mmc0: mmc@fffb4000 { >> + status = "okay"; >> + }; >> + }; >> + }; >> +}; >> -- >> 1.7.9.5 >>