diff options
| author | Viresh Kumar <viresh.kumar@linaro.org> | 2014-06-02 23:41:46 +0530 |
|---|---|---|
| committer | Gary S. Robertson <gary.robertson@linaro.org> | 2015-01-19 08:46:45 -0600 |
| commit | 2f64784c22b73fd369011a4da1ceb54edc4ba801 (patch) | |
| tree | 50e740835249f84994ffc0a3187581d077513988 /fs | |
| parent | ef25dd3c07d94bfc5f1292f64204bac0af2127e8 (diff) | |
clockevent: drivers: don't disable events for unsupported modes
'->set_dev_mode()' callback of clockevent drivers gets called when core tries to
change 'mode' of a clockevent device. Clockevent drivers should change to the
requested mode unless mode isn't supported by driver.
Ideally, drivers shouldn't change state/mode of clockevent devices when the
requested mode isn't supported by driver and the clockevent device should
continue to work as if nothing happened.
But, few clockevent drivers are always disabling events from their
->set_dev_mode() callbacks and they stay disabled for 'default case' (we reach
here for unsupported modes only) as well.
For these drivers, clockevents core wouldn't be sure about state/mode of
clockevent device once ->set_dev_mode() failed and we *may* see some strange
behavior as the clockevent device isn't configured to the right mode by kernel
again.
This patch tries to make sure such drivers don't left events disabled for
unsupported modes.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Santosh Shukla <santosh.shukla@linaro.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions