[PATCH 0/3] omap hsmmc init cleanup and section warning fixes for v3.4 merge window

[Russell King - ARM Linux]

On Thu, Feb 16, 2012 at 01:51:51PM +0000, Russell King - ARM Linux wrote:
> On Thu, Feb 16, 2012 at 06:45:50PM +0530, Rajendra Nayak wrote:
> > On Thursday 16 February 2012 06:04 PM, Rajendra Nayak wrote:
> >>> Can you test something with these patches?
> >>>
> >>> 1. Build the gpio-twl4030.c as a module, but with HSMMC support built in
> >>> 2. Boot on the 4430SDP
> >>
> >> twl4030 gpio is used for card detect on OMAP3, so I tried this
> >> on my Beagle instead of 4430SDP.
> >> The kernel boots up but does not detect/enumerate the mmc card.
> >>
> >>> 3. Load the gpio-twl4030 module
> >>
> >> I was expecting this to now detect the card, but I instead got
> >> this error which seems to tell gpio-twl4030 has problems
> >> when built/used as a module, outside of the mmc issues.
> >
> > Looks like I was mislead with the errors and though the twl4030
> > gpio probe was bailing out with errors, which its not.
> > It does seem to go ahead, does a mmc late init which registers
> > the mmc omap_device and hence does a platform_device_add, but the
> > device never seem to get probed. mmc driver is built in and
> > registered.
> >
> >>
> >> # insmod gpio-twl4030.ko
> >> [   16.217864] twl4030_gpio twl4030_gpio: can't dispatch IRQs from modules
> >> [   16.242004] gpiochip_add: registered GPIOs 192 to 211 on device: twl4030
> >>
> >>
> >>> 4. Remove the gpio-twl4030 module
> >>> 5. Re-load the gpio-twl4030.ko module
> >>>
> >>> and report back what you get.  Thanks.
> >
> 
> (4) and (5) are the key bits of what I was asking you to do.

Okay, so that was a total waste of time and effort, because you didn't do
what I asked.

Tony: I think there's a bug here - if the gpio-twl4030 module is inserted,
removed and re-inserted, I think we'll end up creating the devices for MMC
twice with the same name, resulting in sysfs complaining very loudly.