| commit | ed625b9143ee53fe610320908c89e22635ee6e87 | |
| author | Omar Ramirez Luna <omar.ramirez@ti.com> | |
| Fri, 18 Nov 2011 22:18:54 +0000 (18 16:18 -0600) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Wed, 14 Dec 2011 00:12:06 +0000 (13 16:12 -0800) | ||
| tree | af583ca87a18c133d2e5bdf52e22f06b270b6bd2 | treesnapshot (tar.gz zip) |
| parent | 0a7e22e61e07a2ea479511f9620858be2f1507e8 | commitdiff |
staging: tidspbridge: request dmtimer clocks on init
Given that dm timer framework doesn't support request of clocks
by soft | hard irqs because some recent changes, tidspbridge needs
to request its clocks on init and enable/disable them on demand.
This was first seen on 3.2-rc1.
Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Given that dm timer framework doesn't support request of clocks
by soft | hard irqs because some recent changes, tidspbridge needs
to request its clocks on init and enable/disable them on demand.
This was first seen on 3.2-rc1.
Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/staging/tidspbridge/core/dsp-clock.c | diffblobblamehistory |