Re: [PATCH] MMC - CONFIG_HOTPLUG support

[Russell King - ARM Linux <linux@arm.linux.org.uk>]

On Mon, Dec 26, 2005 at 03:46:58PM -0300, Anderson.Briglia@indt.org.br wrote:
> > This is already implemented.  The MMC block driver will be called via
> > mmc_blk_probe() when a card is inserted, and via mmc_blk_remove()
> > when it is removed.
> 
> Yes, it's right. But if the MMC block driver is compiled as a module,
> it's not loaded automatically by the MMC core driver.

That's not a kernel problem - the userspace tools (module-utils) do not
know how to interpret the MMC hotplug information to determine which
modules need loading.

However, it's quite likely that even if they did, we'll need to change
the way that the MMC drivers are bound to the MMC devices - it's possible
that a MMC device could be driven by more than one driver.

> Another problem is a bug on mmc omap driver: if a card is released,
> the sysfs and /dev entries are not removed (I'm using udev).

Which sysfs entries?  Could be that the omap driver doesn't detect
card removals correctly - or is asking the MMC subsystem to re-detect
cards before the card has actually disconnected from the bus.