From mboxrd@z Thu Jan 1 00:00:00 1970 From: olof@lixom.net (Olof Johansson) Date: Sun, 19 Jan 2014 15:30:08 -0800 Subject: How to support SDIO wifi/bt in DT In-Reply-To: <20140119230924.GB8154@piout.net> References: <20140116133649.GV15937@n2100.arm.linux.org.uk> <3215037.8HVCjAeS8g@wuerfel> <20140119230924.GB8154@piout.net> Message-ID: <20140119233008.GA4867@quad.lixom.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Jan 20, 2014 at 12:09:25AM +0100, Alexandre Belloni wrote: > 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. The patches I have here do it all in the core per host with common bindings. I hope to post them tonight. They should fit the at91 model just fine as well, since they do each slot as a mmc_host, not as a separate slot with a shared host controller. (Some drivers don't seem to call mmc_of_parse(), which they will need to do to take advantage of the common implementation. But that can be addressed driver by driver as someone has a chance to test it). -Olof