| commit | 8c63d554e18687669b1a0fbefc3aaf9b1db6c855 | |
| author | Anand Gadiyar <gadiyar@ti.com> | |
| Mon, 12 Oct 2009 16:17:27 +0000 (12 09:17 -0700) | ||
| committer | Tony Lindgren <tony@atomide.com> | |
| Mon, 12 Oct 2009 18:19:21 +0000 (12 11:19 -0700) | ||
| tree | 2e8878b843347c0119fdd9906fe8fe5910f9ffef | treesnapshot (tar.gz zip) |
| parent | f19e31748e6f43acf34e196209a7c90d5a451164 | commitdiff |
omap: ehci: remove DPLL5 programming
DPLL5 programming should be taken care of by the clock framework.
The driver should not need to worry about programming this
explicitly.
Also, the DPLL5 m and n values used were valid only for a
specific value of the system clock. So they would not work
correctly for other input frequencies anyway.
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
DPLL5 programming should be taken care of by the clock framework.
The driver should not need to worry about programming this
explicitly.
Also, the DPLL5 m and n values used were valid only for a
specific value of the system clock. So they would not work
correctly for other input frequencies anyway.
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
| drivers/usb/host/ehci-omap.c | diffblobblamehistory |