| commit | 4ed084e489fd1a4b5776715538979d3e921969f0 | [log] [tgz] |
|---|---|---|
| author | Jerry Zhang <zhangjerry@google.com> | Mon Jan 08 16:25:30 2018 -0800 |
| committer | Jerry Zhang <zhangjerry@google.com> | Wed Jan 10 18:37:54 2018 +0000 |
| tree | 3c12e383756210dcbfc75f48d5dcd06cb59add52 | |
| parent | e8f5f841b764b2ef3e1209ebf03fdb8ff1354773 [diff] |
Move CONFIG_AIO to android-base. CONFIG_AIO has legitimate use for the functionfs driver, which is used with adb and mtp. It is now required to be enabled for better performance with those services. Bug: 37916658 Test: None Change-Id: Ic9adb3340f6b3230798653e0bb08bbafdd550efd Signed-off-by: Jerry Zhang <zhangjerry@google.com>
The files in these directories are meant to be used as a base for an Android kernel config. All devices must have the options in android-base.cfg configured as specified. If an android-base-ARCH.cfg file exists for the architecture of your device, the options in that file must be configured as specified also.
While not mandatory, the options in android-recommended.cfg enable advanced Android features.
Assuming you already have a minimalist defconfig for your device, a possible way to enable these options would be to use the merge_config.sh script in the kernel tree. From the root of the kernel tree:
ARCH=<arch> scripts/kconfig/merge_config.sh <...>/<device>_defconfig <...>/android-base.cfg <...>/android-base-<arch>.cfg <...>/android-recommended.cfg
This will generate a .config that can then be used to save a new defconfig or compile a new kernel with Android features enabled.
Because there is no tool to consistently generate these config fragments, lets keep them alphabetically sorted instead of random.