diff options
| author | Sergei Shtylyov <sshtylyov@ru.mvista.com> | 2011-03-13 20:06:59 +0000 |
|---|---|---|
| committer | Kevin Hilman <khilman@ti.com> | 2011-03-15 08:17:23 -0700 |
| commit | 60d97a840175d3becb2e6de36537a5cdfc0ec3a9 (patch) | |
| tree | 6cbdb324a563050736f15388418300a54dd0bba5 /arch/arm/mach-s5pv310/setup-i2c7.c | |
| parent | f6e5306ecf269cac52cb06a2f356431f63640595 (diff) | |
| download | blackbird-op-linux-60d97a840175d3becb2e6de36537a5cdfc0ec3a9.tar.gz blackbird-op-linux-60d97a840175d3becb2e6de36537a5cdfc0ec3a9.zip | |
davinci: DM644x EVM: register MUSB device earlier
The MUSB driver doesn't see its platform device on DM644x EVM board anymore
since commit 73b089b052a69020b953312a624a6e1eb5b81fab (usb: musb: split davinci
to its own platform_driver) because the new probe is called as subsys_initcall()
now, and the device is registered later than that by the board code. Move the
registration to davinci_evm_init() -- it's safe to do so because the MUSB core
device still gets initialized as fs_initcall() -- which is late enough for the
I2C GPIO expander (which controls VBUS) to be initialized.
Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Acked-by: Felipe Balbi <balbi@ti.com>
Tested-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
Diffstat (limited to 'arch/arm/mach-s5pv310/setup-i2c7.c')
0 files changed, 0 insertions, 0 deletions
