a5b7414970c85217e88015e78ecbc5ba093dead3 - platform_frameworks_base

commit	a5b7414970c85217e88015e78ecbc5ba093dead3	[log] [tgz]
author	Jungshik Jang <jayjang@google.com>	Mon Jun 23 18:03:10 2014 +0900
committer	Jungshik Jang <jayjang@google.com>	Tue Jun 24 16:14:05 2014 +0900
tree	2b3ebd51c08ae0e8a61f09f40db58c008418e850
parent	d4c115435395165b562f6ca2279d2418f9c0b26d [diff]

Introduce @ServiceThreadOnly and @IothreadOnly to HdmiControlService

Many of hdmi service modules assumes that it runs on
service thread without any lock. But it's a bit
hard to distinguish whether a method runs on
service thread or not even though there is run-time
assertion (runOnServiceThread()) is top of method.
@ServiceThreadOnly interface documents that a method should
run on service thread while @IoThreadOnly documents
that a method should run on io thread.

Change-Id: Ia4a6a48675d2302fb2cb7a8a807fcf112da5d4e7

services/core/java/com/android/server/hdmi/HdmiAnnotations.java[Added - diff]
services/core/java/com/android/server/hdmi/HdmiCecController.java[diff]
services/core/java/com/android/server/hdmi/HdmiCecLocalDevice.java[diff]
services/core/java/com/android/server/hdmi/HdmiCecLocalDevicePlayback.java[diff]
services/core/java/com/android/server/hdmi/HdmiCecLocalDeviceTv.java[diff]
services/core/java/com/android/server/hdmi/HdmiControlService.java[diff]

6 files changed

tree: 2b3ebd51c08ae0e8a61f09f40db58c008418e850