Re: [android-kernel] Sensors

you have to modify the kconfig and the Makefile and the source code to the directory D.Where D is the directory of any existing proximity sensor module. One such location is : Linux /drivers /staging

Re: [android-kernel] Using SCHED_DEADLINE for Android services

Dear Claudio, Thanks a lot for the pointers. Will surely study and experiment with this new scheduling policy in Linux Kernel from Android Service perspective. Looking forward to more updates from you on this. Warm Regards, Anil On Thu, Aug 27, 2015 at 2:12 PM, wrote: > Dear developers, > > st

[android-kernel] Using SCHED_DEADLINE for Android services

Dear developers, starting from release 3.14, every Linux kernel has an additional CPU scheduling policy called *SCHED_DEADLINE* [1, 2]. This email is to encourage you in evaluating the benefits that such a policy could bring when scheduling the Android services. The policy allows to assign ea

[android-kernel] Sensors

My kernel's defconfig includes a certain proximity sensor to build but doesn't build it and I'm not sure where to define it to be built for the device I'm building. -- -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel --- You re

[android-kernel] Android memory cgroup topic

>From android version, we see that Android plan to use memory cgroup to manage process. In system/core/rootdir/init.rc # Create cgroup mount point for memory mount tmpfs none /sys/fs/cgroup mode=0750,uid=0,gid=1000 mkdir /sys/fs/cgroup/memory 0750 root system mount cgroup none /s