After the ltr_558als light sensor and proximity sensor probe are enabled by default, the system cannot sleep.

Looking at a bug in the past two days, other colleagues suspected that the system could not sleep due to an interruption of the light sensor every two seconds. I didn't quite trust this statement at first, because the normal gpio interruption caused the system to sleep? But it mentioned that our gpio interrupt will apply for a wake-lock .... This requires my own research. But now we have no time to carefully follow the code. Because I still have several bugs to handle. This problem will take a closer look after I have time.

This is to be continued .....

No one knows how bad the ltr_558als code is. I really want to rewrite it. To be honest, I want to repeat a lot of code, because you know that many of my friends have obsessive-compulsive disorder, most people with obsessive-compulsive disorder have Jie Li, and most people with obsessive-compulsive disorder are pursuing absolute perfection, brother occupies all of these resources. I almost dropped the door handle when I closed the door.

I have already found out that when the system is turned on, the upper layer will turn on the light sensor, even if I have chosen not to adjust the brightness automatically! I don't know where smart white will use light sensors, but the upper layer will turn on the light sensor every time it starts up, but this has nothing to do with my driver, the driver just provides him with a method to open it. If you love to open it, let him open it.

Then, when I press the power key, the system starts to sleep, and I also see the upper layer closing light sensor action, which is good, indicating that the upper layer logic is correct.

Another problem is that the system is sleep. After the system is connected to BP, BP wants to periodically wake up the system and then scan the network .... This seems to have a gross relationship with AP. What is the relationship between the scan network and the AP. Why have you woken up the AP ???

This is xuanjicang... The AP and BP of other machines have two independent CPUs, so when the BP scans the network, the relationship between the AP and the AP will be gone, and the AP will sleep, however, our machine only has one CPU, so we have to wake up...

At this time, the system is awakened. Then ltr_558als also followed suit... But at this time, the screen was not bright, and the process of Android could not go any further. No one turned off 558 now .... So the system cannot sleep ..

What should we do? Do not enable probe 558 by default and disable it. In this way, only the upper layer can be opened or closed. 558 you can no longer secretly run it...

Solve the problem.