From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexandre Belloni Subject: Re: How to support SDIO wifi/bt in DT Date: Mon, 20 Jan 2014 00:09:25 +0100 Message-ID: <20140119230924.GB8154@piout.net> References: <20140116133649.GV15937@n2100.arm.linux.org.uk> <3215037.8HVCjAeS8g@wuerfel> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from top.free-electrons.com ([176.31.233.9]:33502 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752172AbaASXJd (ORCPT ); Sun, 19 Jan 2014 18:09:33 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Olof Johansson Cc: Nicolas Pitre , "devicetree@vger.kernel.org" , Russell King - ARM Linux , Arnd Bergmann , "linux-mmc@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" On Sun, Jan 19, 2014 at 11:29:55AM -0800, Olof Johansson wrote : > The "multi-slot" concept I was talking about was one host controller > for several physical slots. Seems like at91 implements _and_ uses this > but nobody else. However, it seems that they allocate one mmc host per > slot, so the same model still works. > I think we need to be extra careful about the DT bindings then because adding a property in a slot is requiring handling that in the at91 driver whereas adding a common property for the various mmc hosts can be done in the core code. >>From what I remember, it would be really good to put the DT parsing for the slots in the core code but I only had a really quick look at that. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: alexandre.belloni@free-electrons.com (Alexandre Belloni) Date: Mon, 20 Jan 2014 00:09:25 +0100 Subject: How to support SDIO wifi/bt in DT In-Reply-To: References: <20140116133649.GV15937@n2100.arm.linux.org.uk> <3215037.8HVCjAeS8g@wuerfel> Message-ID: <20140119230924.GB8154@piout.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sun, Jan 19, 2014 at 11:29:55AM -0800, Olof Johansson wrote : > The "multi-slot" concept I was talking about was one host controller > for several physical slots. Seems like at91 implements _and_ uses this > but nobody else. However, it seems that they allocate one mmc host per > slot, so the same model still works. > I think we need to be extra careful about the DT bindings then because adding a property in a slot is requiring handling that in the at91 driver whereas adding a common property for the various mmc hosts can be done in the core code. >>From what I remember, it would be really good to put the DT parsing for the slots in the core code but I only had a really quick look at that. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com