drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
android_frameworks_base/libs/common_time/Android.mk

37 lines
727 B
Makefile
Raw Normal View History

Upintegrate the common_time service from ics-aah. Move the common_time service developed in the ics-aah branch back into master. The common_time service is a small service build to synchronize an arbitrary timeline amongst peers on a local sub-net. While running and configured, the service will elect a master from the set of available devices within the subnet, define a relationship between the common_time timeline the local time timeline (provided by the local time HAL), and then attempt to maintain synchronization between common and local time by controlling the frequency of the local time clock via the HAL, or by disciplining local time in the digital domain if the local time HAL implementation does not support HW slewing. On its own, the native common time service will do nothing until it is configured. The CommonTimeManagementService (running out of the system server process) is responsible for implementing policy regarding configuration and operation of the common_time service and will be added in a subsequent CL. Change-Id: I71292f9b9b1797665865689c4572c9d3a0552f64 Signed-off-by: John Grossman <johngro@google.com>
2011-08-15 11:59:47 -07:00
LOCAL_PATH:= $(call my-dir)
#
# common_time_service
#
include $(CLEAR_VARS)
LOCAL_SRC_FILES := \
common_clock_service.cpp \
common_time_config_service.cpp \
common_time_server.cpp \
common_time_server_api.cpp \
common_time_server_packets.cpp \
clock_recovery.cpp \
common_clock.cpp \
Fix for bug 6691452 Hand merge from ics-aah > Fix for bug 6691452 : DO NOT MERGE > > As it so happens, there seem to be panels out there who disapprove of > sudden changes in their HDMI clock rate. In particular, Sony LCD > panels made from around 2010-2011 (including the Sony GTV panel) seem > to dislike this behavior. When exposed to a large jump in the clock > rate (say from -100pmm to +100ppm in about 30mSec), they seem to > panic, blank their audio and video, and then resync. The whole > panic process takes about 2 seconds. > > The HDMI spec says that its clock jitter requirements are defined by > their differential signalling eye diagram requirements relative to an > "Ideal Recovery Clock" (see section 4.2.3.1 of the HDMI 1.3a spec). > Basically, if you pass the eye diagram tests, you pass the clock > jitter requirements. We have determined in lab that even being > extremely aggressive in our VCXO rate changes does not come even close > to violating the HDMI eye diagrams. Its just this era of Sony panels > which seem to be upset by this behavior. > > One way or the other, experiments which the GTV devices have seemed to > indicate that a full range sweep of the VCXO done in 10mSec steps over > anything faster than 190mSec can cause trouble. Adding a healthy > degree of margin to this finding, the fix is to limit the rate of VCXO > control change such that it never goes at a rate faster than > FullRange/300mSec. > > Change flagged as do not merge due to the code structure changes to master. > This will need to be merged by hand. > > Signed-off-by: John Grossman <johngro@google.com> > Change-Id: Ibfd361fe1cc2cbd4909489e3317fb12e005c6a75 Change-Id: If62f791c826f1145262a6b546b1dc1f9776c37d8 Signed-off-by: John Grossman <johngro@google.com>
2012-06-26 12:50:28 -07:00
main.cpp \
utils.cpp
Upintegrate the common_time service from ics-aah. Move the common_time service developed in the ics-aah branch back into master. The common_time service is a small service build to synchronize an arbitrary timeline amongst peers on a local sub-net. While running and configured, the service will elect a master from the set of available devices within the subnet, define a relationship between the common_time timeline the local time timeline (provided by the local time HAL), and then attempt to maintain synchronization between common and local time by controlling the frequency of the local time clock via the HAL, or by disciplining local time in the digital domain if the local time HAL implementation does not support HW slewing. On its own, the native common time service will do nothing until it is configured. The CommonTimeManagementService (running out of the system server process) is responsible for implementing policy regarding configuration and operation of the common_time service and will be added in a subsequent CL. Change-Id: I71292f9b9b1797665865689c4572c9d3a0552f64 Signed-off-by: John Grossman <johngro@google.com>
2011-08-15 11:59:47 -07:00
New clock sync control loop. Change clock sync control to velicity form PI loop. Tuned for office LAN and WiFi conditions, will probably perform better in clean environments. Improve packet filtering to prevent clock sync on bad rtt. Changed diag interface to take rtt times, P, I, D are no longer supported. Change-Id: Iad2b26eb44cd222ec5f219b49669e2d6baec9d1c
2012-02-13 16:24:29 -08:00
# Uncomment to enable vesbose logging and debug service.
#TIME_SERVICE_DEBUG=true
Upintegrate the common_time service from ics-aah. Move the common_time service developed in the ics-aah branch back into master. The common_time service is a small service build to synchronize an arbitrary timeline amongst peers on a local sub-net. While running and configured, the service will elect a master from the set of available devices within the subnet, define a relationship between the common_time timeline the local time timeline (provided by the local time HAL), and then attempt to maintain synchronization between common and local time by controlling the frequency of the local time clock via the HAL, or by disciplining local time in the digital domain if the local time HAL implementation does not support HW slewing. On its own, the native common time service will do nothing until it is configured. The CommonTimeManagementService (running out of the system server process) is responsible for implementing policy regarding configuration and operation of the common_time service and will be added in a subsequent CL. Change-Id: I71292f9b9b1797665865689c4572c9d3a0552f64 Signed-off-by: John Grossman <johngro@google.com>
2011-08-15 11:59:47 -07:00
ifeq ($(TIME_SERVICE_DEBUG), true)
LOCAL_SRC_FILES += diag_thread.cpp
LOCAL_CFLAGS += -DTIME_SERVICE_DEBUG
endif
LOCAL_SHARED_LIBRARIES := \
libbinder \
libcommon_time_client \
Add liblog Bug: 8580410 Change-Id: I746aa8258866508c3a725d0773faf4518096548f
2013-04-09 21:54:12 -07:00
libutils \
liblog
Upintegrate the common_time service from ics-aah. Move the common_time service developed in the ics-aah branch back into master. The common_time service is a small service build to synchronize an arbitrary timeline amongst peers on a local sub-net. While running and configured, the service will elect a master from the set of available devices within the subnet, define a relationship between the common_time timeline the local time timeline (provided by the local time HAL), and then attempt to maintain synchronization between common and local time by controlling the frequency of the local time clock via the HAL, or by disciplining local time in the digital domain if the local time HAL implementation does not support HW slewing. On its own, the native common time service will do nothing until it is configured. The CommonTimeManagementService (running out of the system server process) is responsible for implementing policy regarding configuration and operation of the common_time service and will be added in a subsequent CL. Change-Id: I71292f9b9b1797665865689c4572c9d3a0552f64 Signed-off-by: John Grossman <johngro@google.com>
2011-08-15 11:59:47 -07:00
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE := common_time
include $(BUILD_EXECUTABLE)
Reference in New Issue Copy Permalink