omap hsmmc init cleanup and section warning fixes for v3.4 merge window
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest4 of 7 patches 0 repliesNew
- v10 of 3 patches 0 repliesSuperseded
4 of 7 patches are in this archive. The cover letter announces 7.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 5/7 | ARM: OMAP2+: Split omap2_hsmmc_init() to properly support I2C GPIO pins | +0 | 2 replies | |
| 5/7 | ARM: OMAP2+: Split omap2_hsmmc_init() to properly support I2C GPIO pins | +0 | 0 replies | |
| 7/7 | ARM: OMAP2+: Mark omap_hsmmc_init and omap_mux related functions as __initarch/ | +4 | 1 reply | |
| 7/7 | ARM: OMAP2+: Mark omap_hsmmc_init and omap_mux related functions as __init | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/7] omap hsmmc init cleanup and section warning fixes for v3.4 merge window
Quoted 10 lines · Rajendra Nayak
Re-sending as these patches did not make it to the lists due to issues with my 'git send-email'
Hi Tony,
This is a re-spin of your series to fix up the section mismatch warnings noted by Russell with
omap2_hsmmc_init(). The previous series had an issue around multiple insmod/rmmod of the twl4030 gpio driver when built as a module as reported by Russell again.
OK, can you please rebase your patches on hsmmc branch in linux-omap at commit 0e91c8ddf0e0932da59ec1d116e34049791b0e73?
Note that at least the hardcoded GPIO numbers are no longer needed.
Quoted 6 lines
There were 2 issues, one with
gpio_requestsfailing as they were never freed on the module unload/unbind. The other was with the mmc devices being registered again. I have fixed both these issues in this series, mainly by having a .teardown hook for twl4030 gpio driver populated from all OMAP3 board files, which release all the requested gpios and also unregister the mmc omap/platform device.
Yes that's great.
Regards,
Tony