[PATCH 1/3] mmc: add support for power-on sequencing through DT

Tomasz Figa tomasz.figa at gmail.com
Sat Feb 15 08:22:30 EST 2014

On 15.02.2014 14:09, Arnd Bergmann wrote:
> On Saturday 15 February 2014 12:27:33 Russell King - ARM Linux wrote:
>> On Sat, Feb 15, 2014 at 01:18:02PM +0100, Arnd Bergmann wrote:
>>> If a wlan adapter has both SPI and SDIO front-ends, the external
>>> dependencies (reset, clock, voltage, ...) will be the same, and
>>> from the kernel perspective the main difference is that SPI cannot
>>> be probed at all, while SDIO can be probed as long as the device
>>> is powered on already.
>> Remember that MMC/SD/SDIO cards can be driven by either a MMC host
>> interface, or a SPI interface.  Both are probe-able.
> I knew about MMC/SD cards being required to understand simple SPI,
> I wasn't sure about SDIO. My understanding however is that you
> have to use the mmc_spi host driver to actually use MMC/SD devices
> as a block device, and that requires having either a DT description
> for the host or an spi_board_info, which I would not consider
> discoverable.
> For spi-mode SDIO devices I'm assuming it's similar, except that
> you'd describe the actual SDIO device in the board info rather than
> create a fake SDIO controller. Still not discoverable unless I'm
> missing your point.

I'm not sure if we should assume that SPI = MMC over SPI. I believe 
there might be a custom protocol involved as well.

Stepping aside from SPI, I already gave an example of a WLAN chip that 
supports multiple control busses [1]. In addition to the commonly used 
SDIO, it supports USB and HSIC as well:

[1] http://www.marvell.com/wireless/assets/marvell_avastar_88w8797.pdf

Moreover, some of Samsung boards use HSIC to communicate with modem 
chips, which have exactly the same problem as we're trying to solve here 
- they need to be powered on to be discovered.

So I really don't think we should be limiting this to MMC alone by any 

Now I don't really know why we want that badly to represent low level 
control parts of such devices as children of control buses of their 
enumerable parts. Could you tell me what benefits it has to justify the 
added complexity of having to instantiate fake devices in respective 
devices, even though they can be fully detected later?

Best regards,

More information about the linux-arm-kernel mailing list