summaryrefslogtreecommitdiff
path: root/sound/oss/hex2hex.c
diff options
context:
space:
mode:
authorMartin Schwidefsky <schwidefsky@de.ibm.com>2013-11-22 11:04:18 (GMT)
committerJiri Slaby <jslaby@suse.cz>2014-03-12 08:42:16 (GMT)
commitccb738e88b60ec21a96f8f5e11a1857236deb518 (patch)
tree3c0b7d775b1cea96d388a21ba0a6f06a732479bd /sound/oss/hex2hex.c
parente1a6db9c9503479d7c28c2662b3895b68a7e96ed (diff)
downloadlinux-fsl-qoriq-ccb738e88b60ec21a96f8f5e11a1857236deb518.tar.xz
s390,time: revert direct ktime path for s390 clockevent device
commit 8adbf78ec4839c1dc4ff20c9a1f332a7bc99e6e6 upstream. Git commit 4f37a68cdaf6dea833cfdded2a3e0c47c0f006da "s390: Use direct ktime path for s390 clockevent device" makes use of the CLOCK_EVT_FEAT_KTIME clockevent option to avoid the delta calculation with ktime_get() in clockevents_program_event and the get_tod_clock() in s390_next_event. This is based on the assumption that the difference between the internal ktime and the hardware clock is reflected in the wall_to_monotonic delta. But this is not true, the ntp corrections are applied via changes to the tk->mult multiplier and this is not reflected in wall_to_monotonic. In theory this could be solved by using the raw monotonic clock but it is simpler to switch back to the standard clock delta calculation. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Diffstat (limited to 'sound/oss/hex2hex.c')
0 files changed, 0 insertions, 0 deletions