Otpvondoiats commented on PR #18266:
URL: https://github.com/apache/nuttx/pull/18266#issuecomment-3845172446

   > @Otpvondoiats please take a look for example here #18171 there is a clear 
example on how the time 64s before change and 25s after change improves things 
by ~2.5x factor. Very short but enough to prove the numbers.
   > 
   > Descriptions dont have to be long but on point. I know you as the author 
know all of the details, but it is also good habit and skill to present the 
details to others. This really can help everyone in understanding changes 
introduced. Especially the changes are breaking and not marked described and 
discussed properly too.
   > 
   > Marking breaking changes here are very important because we all are tired 
of everything changing and have no stable tools to work with. We want NuttX to 
provide such self-compatible stable and reliable environment. It is author 
responsibility to prove that presented improvement is worth breaking project 
for everyone else.
   > 
   > We need to find a common language and working methods please.
   
   I have some questions regarding the specific power saving data and logs you 
requested. Are you familiar with the sensor framework? Do you know where its 
power consumption occurs? I answered this question above: the specific power 
consumption data depends on your application scenario. Do you know how much 
power consumption the new Xiaomi Watch 5, with its large-core Android and 
small-core MCU chip, consumes after the small core wakes up the large core? I 
can tell you about a bug: when the small core continuously wakes up the large 
core, the device's standby time drops from 4-5 days to less than 16 hours. Do I 
need to post all these testing and verification procedures for you?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to