On Fri, Jan 17, 2014 at 8:58 AM, Nicolas Pitre <nico@xxxxxxxxxxx> wrote: > On Fri, 17 Jan 2014, Rob Herring wrote: > >> On Thu, Jan 16, 2014 at 9:08 PM, Nicolas Pitre <nico@xxxxxxxxxxx> wrote: >> > On Thu, 16 Jan 2014, Olof Johansson wrote: >> > >> >> "for SDIO slots" is somewhat misleading; nearly all controllers only >> >> do one slot/device per controller. The designware controller can do >> >> multiple slots, and that adds a bit of driver and binding complexity >> >> for something that seemingly not a single vendor has actually >> >> implemented. >> > >> > The Marvell 8688, just to name one, does both WIFI and BlueTooth over >> > the same SDIO controller using separate functions/slots. >> >> But that is logical functions within a chip, not multiple discrete >> chips (i.e. slots) with their own reset, regulators, etc. > > OK. If that's the definition of a slot in this context then I agree. Correct -- the device that I've been doing the work in is actually the combined wifi/bluetooth module on the Samsung Chromebook, which is a Marvell 8797. It has multiple functions which still work well. 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. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
