OSDN Git Service

Give clear distinction between active source/active routing path
authorJinsuk Kim <jinsukkim@google.com>
Thu, 24 Jul 2014 00:15:35 +0000 (09:15 +0900)
committerJinsuk Kim <jinsukkim@google.com>
Mon, 28 Jul 2014 05:48:29 +0000 (14:48 +0900)
commit72b7d738d5b9254594726304cdb1777b54d95631
treeae8cd788149790f3e1de2f87e14e1b259065876b
parent5438e4e173c756a24061da38bfe9142765c56f9d
Give clear distinction between active source/active routing path

Previously in HdmiControlSerivce, active routing path was mixed with
the physical address of the active source, but these two concepts needs
clearer distinction.

Defined a new variable for active source that contains both logical/physical
address to keep active routing path separate. This change makes it possible
to write the flow more closely to the guideline.

Also added to this CL is flag notifyInputChange, which allows the device/
routing change triggered by external event to trigger InputChangeListener
to get TIF notified. For routing control, the device info passed to TIF
has the path information in the field mPhysicalAddress (other fields are
invalid).

Bug: 16519939
Change-Id: I8b400bc48e874b0866500655773aea38ab945fe4
services/core/java/com/android/server/hdmi/ActiveSourceHandler.java
services/core/java/com/android/server/hdmi/DeviceSelectAction.java
services/core/java/com/android/server/hdmi/HdmiCecLocalDevice.java
services/core/java/com/android/server/hdmi/HdmiCecLocalDeviceTv.java
services/core/java/com/android/server/hdmi/HdmiControlService.java
services/core/java/com/android/server/hdmi/NewDeviceAction.java
services/core/java/com/android/server/hdmi/RoutingControlAction.java