From dacd5b0512c6b9b7aa406b2b379f9fb722a95c75 Mon Sep 17 00:00:00 2001 From: Aaqib Ismail Date: Thu, 9 Feb 2023 10:17:08 -0800 Subject: [PATCH] Update BLIND_SPOT_WARNING_ENABLED documentation in HAL Temporary errors should be conveyed through ErrorState values in the STATE property. Bug: 264946039 Test: presubmit Change-Id: I06092b1571aaa63ab165a8e2a2d04f9d57eccb64 --- .../hardware/automotive/vehicle/VehicleProperty.aidl | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) 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 92dc8a7b55..1b02510022 100644 --- a/automotive/vehicle/aidl_property/android/hardware/automotive/vehicle/VehicleProperty.aidl +++ b/automotive/vehicle/aidl_property/android/hardware/automotive/vehicle/VehicleProperty.aidl @@ -3538,9 +3538,10 @@ enum VehicleProperty { * 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. + * In general, BLIND_SPOT_WARNING_ENABLED should always return true or false. If the feature is + * not available due to some temporary state, such as the vehicle speed being too low, that + * information must be conveyed through the ErrorState values in the BLIND_SPOT_WARNING_STATE + * property. * * This property is defined as read_write, but OEMs have the option to implement it as read * only.