Gitiles
Code Review Sign In
review.blissroms.org / platform_packages_modules_common / 85914d25664e40aad9959711f3522752d822292e
commit85914d25664e40aad9959711f3522752d822292e[log] [tgz]
authorSteven Liu <steveliu@google.com>Wed May 01 20:22:06 2024 +0000
committerSteven Liu <steveliu@google.com>Wed May 01 20:55:46 2024 +0000
treeabcb71dd4e3c21cd5352e0e9c0d6a9e72b894073
parentcebb84de89e62f8ee20f757dc53bd3f99a94ba4c [diff]
Add calling HAL API of channel sounding.

Apex-Size-Increase: 50k
Previous-Platform-Support: Yes
Aosp-First: Yes
Test-Info: build and verify the channel sounding function on devices.

Bug: 338259287
Test: make
Change-Id: I48703535846bbece8dc93ccb5b2742ba3268e60a
1 file changed
tree: abcb71dd4e3c21cd5352e0e9c0d6a9e72b894073
  1. build/
  2. java/
  3. javatests/
  4. proguard/
  5. proto/
  6. sdk/
  7. tools/
  8. Android.bp
  9. MODULES_OWNERS
  10. OWNERS
  11. PREBUILTS_MODULE_OWNERS
  12. PREUPLOAD.cfg
  13. README.md
README.md

packages/modules/common

This project includes mainline build and other utility code. Any library code intended for use by modules should go in frameworks/libs/modules-utils instead.

java code

This project uses a single source path for java code. All java code should go in the java directory with subdirectories corresponding to the java package. Android.bp files should go alongside the java source files, and should only include java source for a single java package to encourage good code hygiene.

Tests for java code should go in the javatests directory and follow the same structure.