EAS consists of a number of different components which are being developed to bring together energy efficient scheduling under the Linux scheduler.
A detailed introduction to EAS is available from Linaro: http://www.linaro.org/blog/energy-aware-scheduling-eas-progress-update/
EAS is currently in active development and testing, and work is taking place in two codelines:
EAS mainline development
The upstream development takes place on Linux Kernel Mailing List (LKML) where enhancements and patches are proposed and discussed with the Linux kernel community. EAS has been developed previously as a set of large patchsets (e.g. EAS RFCv5), but this has transitioned to smaller standalone patches.
A snapshot of current proposed patchsets is available on linux-arm.org/git (see resources). Please note it is minimally tested, liable to change as scheduler development evolves, and should be used by advanced developers only.
For full details on the upstream development please see EAS Mainline Development
Product test development codeline
For product use, a version of EAS is available as part of AOSP common kernel. This contains a full implementation with additional enhancements which may not been posted upstream yet, and is the recommended release for product deployment based on Arm big.LITTLE or DynamIQ technology. This kernel is intended for Android and ChromeOS device testing, and the Android common kernel can be applied to other Linux-based systems as well.
Until June-2018, Arm released AOSP versions of EAS according to a quarterly release schedule: EAS r1.2, ... r1.5
From June-2018, Arm is targeting closer alignment with mainline Linux, with one major release per year (soon after android common kernel release). For full details please see Contributing to EAS. The first release will be based on android-4.19.
All work on the product codeline is now being done on AOSP common kernel, and development takes place in the open. Experimental proposed patches will be submitted to AOSP gerrit for code reviews, and developers should subscribe to eas-dev mailing list for email discussions.
Arm has a document discussing how EAS can be used to support DynamIQ flexible microarchitecture: DynamIQ_design_specification_v1.1