platform_system_core/init/sysprop/InitProperties.sysprop
Nikita Ioffe 663cd35030 Make init.userspace_reboot.is_supported a rw property
General recommendation is to avoid read-only properties, and instead control
"read-onlines" by only allowing init/vendor_init to set the property.

Since ro.init.userspace_reboot.is_supported was added in this release, and
nobody outside of the platform is querying it directly, it should be fine to
simply rename it.

Test: adb shell getprop init.userspace_reboot.is_supported
Test: atest CtsUserspaceRebootHostSideTestCases
Bug: 152803929
Change-Id: I7552d5ccc6e9b750a6081947eef8fcb027be13e1
2020-03-30 23:40:45 +01:00

36 lines
1.2 KiB
Text

# Copyright (C) 2019 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
owner: Platform
module: "android.sysprop.InitProperties"
# Serves as a signal to all processes that userspace reboot is happening.
prop {
api_name: "userspace_reboot_in_progress"
type: Boolean
scope: Public
access: ReadWrite
prop_name: "sys.init.userspace_reboot.in_progress"
integer_as_bool: true
}
# Shows whenever the device supports userspace reboot or not.
prop {
api_name: "is_userspace_reboot_supported"
type: Boolean
scope: Public
access: Readonly
prop_name: "init.userspace_reboot.is_supported"
integer_as_bool: true
}