From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753481Ab3KUIoQ (ORCPT ); Thu, 21 Nov 2013 03:44:16 -0500 Received: from eusmtp01.atmel.com ([212.144.249.242]:19267 "EHLO eusmtp01.atmel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750941Ab3KUIoO (ORCPT ); Thu, 21 Nov 2013 03:44:14 -0500 Message-ID: <528DC7D8.6000003@atmel.com> Date: Thu, 21 Nov 2013 09:44:08 +0100 From: Nicolas Ferre Organization: atmel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Jean-Christophe PLAGNIOL-VILLARD , boris brezillon CC: Rob Herring , Pawel Moll , Mark Rutland , Stephen Warren , Ian Campbell , Russell King , Joachim Eastwood , , , 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> <528CE3E6.1040802@overkiz.com> <20131120172722.GJ14627@ns203013.ovh.net> In-Reply-To: <20131120172722.GJ14627@ns203013.ovh.net> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.161.30.18] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/11/2013 18:27, Jean-Christophe PLAGNIOL-VILLARD : > On 17:31 Wed 20 Nov , boris brezillon wrote: >> 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 ? > load the partial dts via userspace Right, but Jean-Christophe, we know that DT fragments are not available in mainline yet (even if the effort is ongoing). So what should we do in the meantime? >> What if both drivers are loaded (or not compiled as modules) ? >> This will lead to one device being unusable (and maybe even worst)... >> > this will never be the case Can you please elaborate? It is a bit frustrating to have to ask you again and again to explain more your thoughts... Bye, > Best Regards, > J. >> 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 >>>> >> > -- Nicolas Ferre