Update BLIND_SPOT_WARNING_ENABLED documentation in HAL
An implementation of BLIND_SPOT_WARNING_ENABLED should return false when
there's an issue with the ADAS system and it cannot retrieve the
property. It should not return NOT_AVAILABLE.
Bug: 264946039
Test: atest VtsHalAutomotiveVehicle_TargetTest
Change-Id: I3f8765b9bbaa96931dd2ae0bab1c8fbc913b261c
diff --git a/automotive/vehicle/aidl_property/android/hardware/automotive/vehicle/VehicleProperty.aidl b/automotive/vehicle/aidl_property/android/hardware/automotive/vehicle/VehicleProperty.aidl
index 6c3ce88..a19eab2 100644
--- a/automotive/vehicle/aidl_property/android/hardware/automotive/vehicle/VehicleProperty.aidl
+++ b/automotive/vehicle/aidl_property/android/hardware/automotive/vehicle/VehicleProperty.aidl
@@ -3508,6 +3508,10 @@
* Set true to enable BSW and false to disable BSW. When BSW is enabled, the ADAS system in the
* vehicle should be turned on and monitoring for objects in the vehicle’s blind spots.
*
+ * If BSW is not available, IVehicle#get must not return any NOT_AVAILABLE value in StatusCode.
+ * Other StatusCode values like TRY_AGAIN may still be used as needed. For example, if BSW is
+ * not available because the vehicle speed is too low, IVehicle#get must return false.
+ *
* This property is defined as read_write, but OEMs have the option to implement it as read
* only.
*