Merge "Updated HVAC property docs with go/revising-hvac-additional-rule" into udc-dev

This commit is contained in:
Shrikar Amirisetty
2023-02-28 21:22:28 +00:00
committed by Android (Google) Code Review
3 changed files with 29 additions and 8 deletions

View File

@@ -829,10 +829,10 @@ enum VehicleProperty : int32_t {
/*
* HVAC Properties
*
* Additional rules for mapping a zoned HVAC property (except
* HVAC_MAX_DEFROST_ON) to AreaIDs:
* - Every seat in VehicleAreaSeat that is available in the car, must be
* part of an AreaID in the AreaID array.
* Additional rules for mapping non-GLOBAL VehicleArea type HVAC properties
* to AreaIDs:
* - Every “area” for a specific VehicleArea type that is affected by the
* property, must be included in an area ID for that property.
*
* Example 1: A car has two front seats (ROW_1_LEFT, ROW_1_RIGHT) and three
* back seats (ROW_2_LEFT, ROW_2_CENTER, ROW_2_RIGHT). There are two
@@ -860,6 +860,16 @@ enum VehicleProperty : int32_t {
* - ROW_1_LEFT
* - ROW_1_RIGHT
* - ROW_2_LEFT | ROW_2_CENTER | ROW_2_RIGHT | ROW_3_LEFT | ROW_3_CENTER | ROW_3_RIGHT
*
* Example 3: A car has two front seats (ROW_1_LEFT, ROW_1_RIGHT) and three
* back seats (ROW_2_LEFT, ROW_2_CENTER, ROW_2_RIGHT). Suppose the car
* supports HVAC_AUTO_ON for just the two front seats.
* - A valid mapping set of AreaIDs for HVAC_AUTO_ON would be:
* - ROW_1_LEFT | ROW_1_RIGHT
* - If HVAC_AUTO_ON had two separate control units for the driver side
* and passenger side, an alternative mapping would be:
* - ROW_1_LEFT
* - ROW_1_RIGHT
*/
/**

View File

@@ -619,10 +619,10 @@ enum VehicleProperty {
/**
* HVAC Properties
*
* Additional rules for mapping a zoned HVAC property (except
* HVAC_MAX_DEFROST_ON) to AreaIDs:
* - Every seat in VehicleAreaSeat that is available in the car, must be
* part of an AreaID in the AreaID array.
* Additional rules for mapping non-GLOBAL VehicleArea type HVAC properties
* to AreaIDs:
* - Every “area” for a specific VehicleArea type that is affected by the
* property, must be included in an area ID for that property.
*
* Example 1: A car has two front seats (ROW_1_LEFT, ROW_1_RIGHT) and three
* back seats (ROW_2_LEFT, ROW_2_CENTER, ROW_2_RIGHT). There are two
@@ -651,6 +651,16 @@ enum VehicleProperty {
* - ROW_1_RIGHT
* - ROW_2_LEFT | ROW_2_CENTER | ROW_2_RIGHT | ROW_3_LEFT | ROW_3_CENTER | ROW_3_RIGHT
*
* Example 3: A car has two front seats (ROW_1_LEFT, ROW_1_RIGHT) and three
* back seats (ROW_2_LEFT, ROW_2_CENTER, ROW_2_RIGHT). Suppose the car
* supports HVAC_AUTO_ON for just the two front seats.
* - A valid mapping set of AreaIDs for HVAC_AUTO_ON would be:
* - ROW_1_LEFT | ROW_1_RIGHT
* - If HVAC_AUTO_ON had two separate control units for the driver side
* and passenger side, an alternative mapping would be:
* - ROW_1_LEFT
* - ROW_1_RIGHT
*
*
* Fan speed setting
*

View File

@@ -935,5 +935,6 @@ b7ce2d87841585551b082fca6d099622e63b7099e0d8013f687ea1a1dc35c4dc android.hardwar
4f1a02d21a22104c734f71cdbba19b6f7e93d4ee107ff79f0dbdd171a8430e0e android.hardware.automotive.vehicle@2.0::types
a2fbd9747fbb9ceb8c1090b5a24138312246502d5af0654a8c2b603a9bf521fc android.hardware.gnss@1.0::IGnssCallback
889b59e3e7a59afa67bf19882a44f51a2f9e43b6556ec52baa9ec3efd1ef7fbe android.hardware.camera.device@3.2::types
db37a1c757e2e69b1ec9c75a981a6987bd87a131d92ab6acc00e04d19f374281 android.hardware.automotive.vehicle@2.0::types
# There will be no more HIDL HALs. Use AIDL instead.