All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Olof Johansson <olof@lixom.net>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: How to support SDIO wifi/bt in DT
Date: Fri, 17 Jan 2014 15:47:54 +0100	[thread overview]
Message-ID: <201401171547.55384.arnd@arndb.de> (raw)
In-Reply-To: <alpine.LFD.2.10.1401162204560.28907@knanqh.ubzr>

On Friday 17 January 2014, Nicolas Pitre 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.
> 
> Or maybe I'm misunderstanding you?
> 

I wasn't aware of this but I just checked (in mmc_attach_sdio) that
there can be multiple functions on a slot. I assume the sd8688 has
a single slot with two functions, so that potentially extends the
problem space if we need to supply clocks and regulators per
function rather than just per slot.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: How to support SDIO wifi/bt in DT
Date: Fri, 17 Jan 2014 15:47:54 +0100	[thread overview]
Message-ID: <201401171547.55384.arnd@arndb.de> (raw)
In-Reply-To: <alpine.LFD.2.10.1401162204560.28907@knanqh.ubzr>

On Friday 17 January 2014, Nicolas Pitre 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.
> 
> Or maybe I'm misunderstanding you?
> 

I wasn't aware of this but I just checked (in mmc_attach_sdio) that
there can be multiple functions on a slot. I assume the sd8688 has
a single slot with two functions, so that potentially extends the
problem space if we need to supply clocks and regulators per
function rather than just per slot.

	Arnd

  reply	other threads:[~2014-01-17 14:48 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 13:36 How to support SDIO wifi/bt in DT Russell King - ARM Linux
2014-01-16 13:51 ` Chen-Yu Tsai
2014-01-16 14:02 ` Arnd Bergmann
2014-01-16 17:15   ` Olof Johansson
2014-01-16 17:15     ` Olof Johansson
2014-01-16 19:58     ` Russell King - ARM Linux
2014-01-16 19:58       ` Russell King - ARM Linux
2014-01-16 20:00       ` Olof Johansson
2014-01-16 20:00         ` Olof Johansson
2014-01-16 20:03         ` Russell King - ARM Linux
2014-01-16 20:03           ` Russell King - ARM Linux
2014-01-17  9:39         ` Alexandre Belloni
2014-01-17  9:39           ` Alexandre Belloni
2014-01-17 10:06           ` Chen-Yu Tsai
2014-01-17 10:06             ` Chen-Yu Tsai
2014-01-17 10:14             ` Alexandre Belloni
2014-01-17 10:14               ` Alexandre Belloni
2014-01-17 10:44           ` Andrew Lunn
2014-01-17 10:44             ` Andrew Lunn
2014-02-05 17:11             ` Mark Brown
2014-02-05 17:11               ` Mark Brown
2014-01-16 21:46     ` Arnd Bergmann
2014-01-16 21:46       ` Arnd Bergmann
2014-01-16 21:52       ` Olof Johansson
2014-01-16 21:52         ` Olof Johansson
2014-01-16 22:14       ` Marcel Holtmann
2014-01-16 22:14         ` Marcel Holtmann
2014-01-17  3:08     ` Nicolas Pitre
2014-01-17  3:08       ` Nicolas Pitre
2014-01-17 14:47       ` Arnd Bergmann [this message]
2014-01-17 14:47         ` Arnd Bergmann
     [not found]       ` <alpine.LFD.2.10.1401162204560.28907-fMhRO7WWcppj+hNMo8g0rg@public.gmane.org>
2014-01-17 15:14         ` Rob Herring
2014-01-17 15:14           ` Rob Herring
2014-01-17 16:58           ` Nicolas Pitre
2014-01-17 16:58             ` Nicolas Pitre
2014-01-19 19:29             ` Olof Johansson
2014-01-19 19:29               ` Olof Johansson
2014-01-19 20:28               ` Arnd Bergmann
2014-01-19 20:28                 ` Arnd Bergmann
2014-01-19 23:26                 ` Olof Johansson
2014-01-19 23:26                   ` Olof Johansson
2014-01-19 23:09               ` Alexandre Belloni
2014-01-19 23:09                 ` Alexandre Belloni
2014-01-19 23:30                 ` Olof Johansson
2014-01-19 23:30                   ` Olof Johansson
2014-01-20  3:57                   ` Olof Johansson
2014-01-20  3:57                     ` Olof Johansson
2014-01-17  9:02     ` Alexandre Belloni
2014-01-17  9:02       ` Alexandre Belloni
2014-01-17  9:38       ` Nicolas Ferre
2014-01-17  9:38         ` Nicolas Ferre
2014-01-16 14:08 ` Alexandre Belloni
2014-01-16 14:34   ` Russell King - ARM Linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201401171547.55384.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nico@fluxnic.net \
    --cc=olof@lixom.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.