power: Add `SetKeyboardBrightness` DBus call

Add a powerd DBus call to allow clients to set the brightness of the
keyboard backlight.

No actual implementation yet, just the DBus boilerplate and a simple
test to exercise the call.

BUG=b:254292590
TEST=`cros_workon_make --board=$BOARD --test chromeos-base/power_manager`

Change-Id: I933ef3412c025261aa63b83c19d1ad7ca114b3f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/4041771
Commit-Queue: David Greenaway <dgreenaway@google.com>
Tested-by: David Greenaway <dgreenaway@google.com>
Reviewed-by: Mengqi Guo <mqg@chromium.org>
Reviewed-by: Phil Kiossoglou <pkiossoglou@chromium.org>
NOKEYCHECK=True
GitOrigin-RevId: 20bf4f1b0258779074eeac7db0eba01f90a62bac
1 file changed
tree: a6721d6fb9cadeb0c2a28cb9b21d0b4121fae0db
  1. constants/
  2. dbus/
  3. mojo/
  4. src/
  5. switches/
  6. .gitignore
  7. BUILD.gn
  8. build.rs
  9. Cargo.toml
  10. DIR_METADATA
  11. LICENSE
  12. OWNERS
  13. README.md
  14. system_api.pc
README.md

This directory (platform2/system_api) contains constants and definitions like D-Bus service names that are shared between Chromium and Chromium OS.

This directory is only for things like headers and .proto files. No implementation should be added.

When writting a .proto file make sure to use:

option optimize_for = LITE_RUNTIME;

This will force usage of a lite protobuf instead of a full/heavy weight protobuf. The browser only links against the light version, so you will get cryptic link errors about missing parts of Message if you define a protobuf here and then try to use it in Chrome. Currently CrOS links against the full protobuffer library, but that might change in the future.

When declaring a protobuf, avoid use of required unless it is exactly what you mean. "Required is Forever" and very rarely should actually be used. Consult Protocol Buffer Basics: C++ for a detailed of this issue.