Shutdown process?

Post Reply
pmprog
Posts: 74
Joined: Thu Oct 18, 2018 4:01 am
languages_spoken: english
ODROIDs: ODROID-GO
Has thanked: 19 times
Been thanked: 1 time
Contact:

Shutdown process?

Unread post by pmprog » Sun Dec 29, 2019 7:17 am

Just seen this device, and sounds like a neat upgrade, especially with the potential to support NeoGeo Pocket Color.

I was curious though, that as it's now running a Linux system, if you flick the power switch off, does it have to enter a shutdown routine? or can it power off immediately?
I've got a RetroFlag GPI case, and when I flick the switch, nothing can happen for several seconds (especially when inside an emulator), and even though I "know" the software is polling GPIO pins, it really throws me, and I flick the switch several more times.

crashoverride
Posts: 4836
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 246 times
Contact:

Re: Shutdown process?

Unread post by crashoverride » Sun Dec 29, 2019 7:39 am

pmprog wrote:
Sun Dec 29, 2019 7:17 am
with the potential to support NeoGeo Pocket Color.
Both NeoGeo and NeoGeo Pocket Color (libretro port) performed well with limited testing. I expect both systems to be provided in the future pending community testing/feedback.
pmprog wrote:
Sun Dec 29, 2019 7:17 am
if you flick the power switch off, does it have to enter a shutdown routine?
The power switch is exposed as a linux input device. It generates a button event when pressed. As currently configured, it triggers systemd to shutdown the system the same as a "shutdown -h now" command would.
These users thanked the author crashoverride for the post (total 2):
pmprog (Sun Dec 29, 2019 5:04 pm) • crait (Thu Jan 09, 2020 5:28 am)

crashoverride
Posts: 4836
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 246 times
Contact:

Re: Shutdown process?

Unread post by crashoverride » Sun Dec 29, 2019 7:45 am

I should clarify that it is a push button and not a slide switch.
These users thanked the author crashoverride for the post (total 2):
pmprog (Sun Dec 29, 2019 5:04 pm) • crait (Thu Jan 09, 2020 5:28 am)

pmprog
Posts: 74
Joined: Thu Oct 18, 2018 4:01 am
languages_spoken: english
ODROIDs: ODROID-GO
Has thanked: 19 times
Been thanked: 1 time
Contact:

Re: Shutdown process?

Unread post by pmprog » Sun Dec 29, 2019 5:05 pm

Thanks for the reply.

I hope the boot up time can be improved at some point too, though I think in the odroid video, emulation station took the same amount of time as Linux, so maybe an alternative to that might help

User avatar
rooted
Posts: 7335
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 494 times
Been thanked: 137 times
Contact:

Re: Shutdown process?

Unread post by rooted » Sun Jan 05, 2020 11:49 pm

pmprog wrote:Thanks for the reply.

I hope the boot up time can be improved at some point too, though I think in the odroid video, emulation station took the same amount of time as Linux, so maybe an alternative to that might help
It only takes about 13 seconds to reach the home screen, it could be sped up by a second or two but it's already fast.

Shutdown happens in less than two seconds.
These users thanked the author rooted for the post (total 2):
pmprog (Mon Jan 06, 2020 2:48 am) • crait (Thu Jan 09, 2020 5:28 am)

pmprog
Posts: 74
Joined: Thu Oct 18, 2018 4:01 am
languages_spoken: english
ODROIDs: ODROID-GO
Has thanked: 19 times
Been thanked: 1 time
Contact:

Re: Shutdown process?

Unread post by pmprog » Mon Jan 06, 2020 2:50 am

rooted wrote:
Sun Jan 05, 2020 11:49 pm
Shutdown happens in less than two seconds.
If you are mid-emulation, does the shutdown start as you press the button, or is there a delay?

kamots
Posts: 86
Joined: Sun Jul 01, 2018 6:05 am
languages_spoken: english
ODROIDs: ODROID-GO, C1+, ODROID-GO Advance
Has thanked: 16 times
Been thanked: 22 times
Contact:

Re: Shutdown process?

Unread post by kamots » Mon Jan 06, 2020 3:48 am

It shuts down right away. However, the button is recessed in the case and fairly small so it would be unlikely to get hit by accident while playing.

pmprog
Posts: 74
Joined: Thu Oct 18, 2018 4:01 am
languages_spoken: english
ODROIDs: ODROID-GO
Has thanked: 19 times
Been thanked: 1 time
Contact:

Re: Shutdown process?

Unread post by pmprog » Mon Jan 06, 2020 7:16 am

Cheers. It's just as I mentioned before, the GPI doesn't always react instantly to a shutdown, and is pretty irritating.

Is it still possible to power off if the system locks up? (ie holding the power button)

User avatar
rooted
Posts: 7335
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 494 times
Been thanked: 137 times
Contact:

Re: Shutdown process?

Unread post by rooted » Mon Jan 06, 2020 9:11 am

pmprog wrote:Cheers. It's just as I mentioned before, the GPI doesn't always react instantly to a shutdown, and is pretty irritating.

Is it still possible to power off if the system locks up? (ie holding the power button)
Yes, hold it for 6 seconds.
These users thanked the author rooted for the post:
pmprog (Tue Jan 07, 2020 2:12 am)

User avatar
crait
Posts: 6
Joined: Fri Jan 03, 2020 8:43 am
languages_spoken: english
Location: Austin, Texas
Has thanked: 5 times
Been thanked: 1 time
Contact:

Re: Shutdown process?

Unread post by crait » Thu Jan 09, 2020 5:29 am

rooted wrote:
Sun Jan 05, 2020 11:49 pm
pmprog wrote:Thanks for the reply.

I hope the boot up time can be improved at some point too, though I think in the odroid video, emulation station took the same amount of time as Linux, so maybe an alternative to that might help
It only takes about 13 seconds to reach the home screen, it could be sped up by a second or two but it's already fast.

Shutdown happens in less than two seconds.
Honestly, I hated Linux-based emulation devices (Pi-based, etc) because of the huge start-up time and shutdown times. If the ODroid is that fast, then I'd be very happy with one.

User avatar
rooted
Posts: 7335
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 494 times
Been thanked: 137 times
Contact:

Re: Shutdown process?

Unread post by rooted » Thu Jan 09, 2020 6:59 am

crait wrote:
rooted wrote:
Sun Jan 05, 2020 11:49 pm
pmprog wrote:Thanks for the reply.

I hope the boot up time can be improved at some point too, though I think in the odroid video, emulation station took the same amount of time as Linux, so maybe an alternative to that might help
It only takes about 13 seconds to reach the home screen, it could be sped up by a second or two but it's already fast.

Shutdown happens in less than two seconds.
Honestly, I hated Linux-based emulation devices (Pi-based, etc) because of the huge start-up time and shutdown times. If the ODroid is that fast, then I'd be very happy with one.
It's actually that fast, maybe even a touch faster. It's between 11 and 13 seconds.

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Thu Jan 09, 2020 9:30 am

crait wrote:
Thu Jan 09, 2020 5:29 am
Honestly, I hated Linux-based emulation devices (Pi-based, etc) because of the huge start-up time and shutdown times. If the ODroid is that fast, then I'd be very happy with one.
I agree. Fast boot time is one of big and important themes of Linux system (especially for consumer products).
But I think there are some available points for improvement of booting time stages (boot loaders / kernel / loading filesystem / run launcher)
even though immediate appearance of emulator launcher after power-on is not possible. ;)

For one example, with quiet option, booting time can be reduced around for 4~5 seconds.
Also kernel drivers probing time can be reduced by removing unused drivers assuming target product specification is fixed,
but I think it's not good approach in case of go advanced
because go advanced is for developers and it should support various types of drivers. :roll:

crashoverride
Posts: 4836
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 246 times
Contact:

Re: Shutdown process?

Unread post by crashoverride » Thu Jan 09, 2020 9:39 am

@joy
I think we should start investigating what is possible with a 'suspend' state. I have no data on the power draw / battery life when the system is suspended.

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Thu Jan 09, 2020 9:42 am

crashoverride wrote:
Thu Jan 09, 2020 9:39 am
@joy
I think we should start investigating what is possible with a 'suspend' state. I have no data on the power draw / battery life when the system is suspended.
@crashoverride,
Yes. You're right. :)
Suspend must be a best approach if possible.
First, let's check if it's available based on schematics design of go advanced.

crashoverride
Posts: 4836
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 246 times
Contact:

Re: Shutdown process?

Unread post by crashoverride » Thu Jan 09, 2020 9:44 am

A suggestion would be to enter suspend state when the power button is pressed. Then, if the device remains unused for a period of time (30 minutes?), enter shutdown. I do not currently know if this is possible.

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Thu Jan 09, 2020 9:47 am

crashoverride wrote:
Thu Jan 09, 2020 9:44 am
A suggestion would be to enter suspend state when the power button is pressed. Then, if the device remains unused for a period of time (30 minutes?), enter shutdown. I do not currently know if this is possible.
Sounds great and I think the scenario is possible if suspend is available.
Let me check suspend logic on rk3326.

User avatar
rooted
Posts: 7335
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 494 times
Been thanked: 137 times
Contact:

Re: Shutdown process?

Unread post by rooted » Thu Jan 09, 2020 9:52 am

Suspend would be nice, especially if the length of sleep time before shutdown could be adjusted.

Does the device have RTC?

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Thu Jan 09, 2020 10:05 am

rooted wrote:
Thu Jan 09, 2020 9:52 am
Suspend would be nice, especially if the length of sleep time before shutdown could be adjusted.

Does the device have RTC?
That's good idea.
Yes. RK817 has RTC inside and it supports rtc wakeup and interrupt generation.
These users thanked the author joy for the post:
rooted (Thu Jan 09, 2020 5:13 pm)

pmprog
Posts: 74
Joined: Thu Oct 18, 2018 4:01 am
languages_spoken: english
ODROIDs: ODROID-GO
Has thanked: 19 times
Been thanked: 1 time
Contact:

Re: Shutdown process?

Unread post by pmprog » Fri Jan 10, 2020 12:36 am

Wicked, I like the idea of default suspending with safety shutdown :)

The only potential problem I see with that is if you "shutdown" the GoAdv, and it's in suspend mode rather than power down, then you forget and take out the SD card to add/update/remove files, then boot it back up, that might cause corruption?

User avatar
rooted
Posts: 7335
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 494 times
Been thanked: 137 times
Contact:

Re: Shutdown process?

Unread post by rooted » Fri Jan 10, 2020 5:27 am

pmprog wrote:Wicked, I like the idea of default suspending with safety shutdown :)

The only potential problem I see with that is if you "shutdown" the GoAdv, and it's in suspend mode rather than power down, then you forget and take out the SD card to add/update/remove files, then boot it back up, that might cause corruption?
It shouldn't unless you change system files.

kamots
Posts: 86
Joined: Sun Jul 01, 2018 6:05 am
languages_spoken: english
ODROIDs: ODROID-GO, C1+, ODROID-GO Advance
Has thanked: 16 times
Been thanked: 22 times
Contact:

Re: Shutdown process?

Unread post by kamots » Sat Jan 11, 2020 6:20 pm

To that point, suspend should exit any running emulator (save and exit, of course) before suspending.

User avatar
mad_ady
Posts: 7558
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 391 times
Been thanked: 296 times
Contact:

Re: Shutdown process?

Unread post by mad_ady » Sat Jan 11, 2020 7:51 pm

@joy regarding having a fast kernel with useless things turned off - you could have two mutually exclusive deb packages for kernel - one fast, minimal, and one regular. The default could be the regular one with a simple menu-based method to switch to the fast one (though it needs network...)

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Tue Jan 14, 2020 8:41 am

mad_ady wrote:
Sat Jan 11, 2020 7:51 pm
@joy regarding having a fast kernel with useless things turned off - you could have two mutually exclusive deb packages for kernel - one fast, minimal, and one regular. The default could be the regular one with a simple menu-based method to switch to the fast one (though it needs network...)
That's one important point. Good idea.
We need to measure which drivers expend booting time first.

User avatar
rooted
Posts: 7335
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 494 times
Been thanked: 137 times
Contact:

Re: Idea for a gamelink type multiplayer functionality

Unread post by rooted » Tue Jan 14, 2020 9:07 am

joy wrote:
mad_ady wrote:
Sat Jan 11, 2020 7:51 pm
@joy regarding having a fast kernel with useless things turned off - you could have two mutually exclusive deb packages for kernel - one fast, minimal, and one regular. The default could be the regular one with a simple menu-based method to switch to the fast one (though it needs network...)
That's one important point. Good idea.
We need to measure which drivers expend booting time first.
I think minimal networking with only ext4, vfat, and NTFS would be several second faster to boot.

User avatar
mad_ady
Posts: 7558
Joined: Wed Jul 15, 2015 5:00 pm
languages_spoken: english
ODROIDs: XU4, C1+, C2, N1, H2, N2, Go, Go Advance
Location: Bucharest, Romania
Has thanked: 391 times
Been thanked: 296 times
Contact:

Re: Shutdown process?

Unread post by mad_ady » Tue Jan 14, 2020 3:01 pm

As far as I remember PCI probing is slow, but it's probably turned off. Userspace (systemd) may have useless things starting up. You can profile userspace startup times with http://manpages.ubuntu.com/manpages/xen ... yze.1.html

There's also this talk that I found educational: https://www.google.com/url?sa=t&source= ... qpSTijQC-O

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Tue Jan 14, 2020 5:19 pm

I've checked very basic operation of suspend and it looks current rk3326 kernel configuration has suspend option already.

Code: Select all

$ systemctl suspend
(system enters into suspend here)
Then, by pressing power-key shortly, system comes back to idle.

But there are many things to check, like...
- network lost after suspend and resume (need to check suspend/resume state of all mandatory drivers)
- system keeps at the state after resume. but I got rockchip-dmc error event and (need to check ddr self-refresh mode works normally.)
- Not too much current advantage : 480mA -> 200mA :roll:
- and so on...

Code: Select all

[   36.416973] PM: suspend entry 2020-01-14 07:30:38.793326139 UTC
[   36.417002] PM: Syncing filesystems ... done.
[   36.646478] PM: Preparing system for sleep (mem)
[   36.647034] Freezing user space processes ... (elapsed 0.001 seconds) done.
[   36.648700] Freezing remaining freezable tasks ... (elapsed 0.039 seconds) done.
[   36.688098] PM: Suspending system (mem)
[   36.688113] Suspending console(s) (use no_console_suspend to debug)
[   36.808451] PM: suspend of devices complete after 119.551 msecs
[   36.814972] PM: late suspend of devices complete after 1.323 msecs
[   36.816194] rockchip-pm-domain ff000000.power-management:power-controller: Looking up pd_sdcard-supply from device tree
[   36.816211] rockchip-pm-domain ff000000.power-management:power-controller: Looking up pd_sdcard-supply property in node /power-d
[   36.816282] rockchip-pm-domain ff000000.power-management:power-controller: Looking up pd_usb-supply from device tree
[   36.816292] rockchip-pm-domain ff000000.power-management:power-controller: Looking up pd_usb-supply property in node /power-mand
[   36.816401] rockchip-pm-domain ff000000.power-management:power-controller: Looking up pd_vo-supply from device tree
[   36.816410] rockchip-pm-domain ff000000.power-management:power-controller: Looking up pd_vo-supply property in node /power-manad
[   36.816704] PM: noirq suspend of devices complete after 1.719 msecs
[   36.816711] Disabling non-boot CPUs ...
[   36.817043] Invalid sched_group_energy for CPU3
[   36.817049] Invalid sched_group_energy for Cluster3
[   36.817052] Invalid sched_group_energy for CPU2
[   36.817055] Invalid sched_group_energy for Cluster2
[   36.817058] Invalid sched_group_energy for CPU0
[   36.817062] Invalid sched_group_energy for Cluster0
[   36.817619] CPU1: shutdown
[   36.831825] psci: Retrying again to check for CPU kill
[   36.831830] psci: CPU1 killed.
[   36.845757] Invalid sched_group_energy for CPU3
[   36.845763] Invalid sched_group_energy for Cluster3
[   36.845766] Invalid sched_group_energy for CPU0
[   36.845770] Invalid sched_group_energy for Cluster0
[   36.846028] IRQ5 no longer affine to CPU2
[   36.846298] CPU2: shutdown
[   36.859824] psci: Retrying again to check for CPU kill
[   36.859829] psci: CPU2 killed.
[   36.873464] Invalid sched_group_energy for CPU0
[   36.873471] Invalid sched_group_energy for Cluster0
[   36.873950] CPU3: shutdown
[   36.887815] psci: Retrying again to check for CPU kill
[   36.887820] psci: CPU3 killed.
[   36.901110] Enabling non-boot CPUs ...
[   36.920901] Detected VIPT I-cache on CPU1
[   36.920978] Invalid sched_group_energy for CPU1
[   36.920983] CPU1: update cpu_capacity 948
[   36.920988] CPU1: Booted secondary processor [410fd042]
[   36.921125] Invalid sched_group_energy for CPU1
[   36.921131] Invalid sched_group_energy for Cluster1
[   36.921134] Invalid sched_group_energy for CPU0
[   36.921137] Invalid sched_group_energy for Cluster0
[   36.921441] CPU1 is up
[   36.941189] Detected VIPT I-cache on CPU2
[   36.941261] Invalid sched_group_energy for CPU2
[   36.941266] CPU2: update cpu_capacity 948
[   36.941270] CPU2: Booted secondary processor [410fd042]
[   36.941414] Invalid sched_group_energy for CPU2
[   36.941420] Invalid sched_group_energy for Cluster2
[   36.941423] Invalid sched_group_energy for CPU1
[   36.941426] Invalid sched_group_energy for Cluster1
[   36.941429] Invalid sched_group_energy for CPU0
[   36.941433] Invalid sched_group_energy for Cluster0
[   36.941739] CPU2 is up
[   36.961408] Detected VIPT I-cache on CPU3
[   36.961480] Invalid sched_group_energy for CPU3
[   36.961484] CPU3: update cpu_capacity 948
[   36.961488] CPU3: Booted secondary processor [410fd042]
[   36.961645] Invalid sched_group_energy for CPU3
[   36.961651] Invalid sched_group_energy for Cluster3
[   36.961654] Invalid sched_group_energy for CPU2
[   36.961657] Invalid sched_group_energy for Cluster2
[   36.961660] Invalid sched_group_energy for CPU1
[   36.961663] Invalid sched_group_energy for Cluster1
[   36.961666] Invalid sched_group_energy for CPU0
[   36.961670] Invalid sched_group_energy for Cluster0
[   36.961878] Invalid sched_group_energy for CPU3
[   36.961883] Invalid sched_group_energy for Cluster3
[   36.961886] Invalid sched_group_energy for CPU2
[   36.961889] Invalid sched_group_energy for Cluster2
[   36.961892] Invalid sched_group_energy for CPU1
[   36.961895] Invalid sched_group_energy for Cluster1
[   36.961898] Invalid sched_group_energy for CPU0
[   36.961901] Invalid sched_group_energy for Cluster0
[   36.962268] CPU3 is up
[   36.963698] PM: noirq resume of devices complete after 1.191 msecs
[   36.964697] rockchip-dmc dmc: failed to get dfi event
[   36.965291] PM: early resume of devices complete after 1.129 msecs
[   36.974678] Suspended for 8.821 seconds
[   36.976632] rockchip-vop ff460000.vop: [drm:vop_crtc_enable] Update mode to 320x480p60, type: 16
[   36.976771] dw-mipi-dsi ff450000.dsi: final DSI-Link bandwidth: 450 x 1 Mbps
[   37.464298] PM: resume of devices complete after 495.866 msecs
[   37.470919] PM: Finishing wakeup.
[   37.470928] Restarting tasks ... 
[   37.471483] usb 1-1: USB disconnect, device number 2
[   37.471511] usb 1-1.4: USB disconnect, device number 4
[   37.488310] done.
[   37.495655] PM: suspend exit 2020-01-14 07:30:48.693648307 UTC
[   37.497284] rockchip-iodomain ff140000.syscon:io-domains: Setting to 3300000 done
[   37.497621] vccio_sd: ramp_delay not set
[   37.497657] rockchip-iodomain ff140000.syscon:io-domains: Setting to 3300000 done
[   37.512701] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[   37.860107] rockchip-iodomain ff140000.syscon:io-domains: Setting to 3300000 done
[   37.863053] vccio_sd: ramp_delay not set
[   37.863070] rockchip-iodomain ff140000.syscon:io-domains: Setting to 1800000 done
[   37.887599] mmc_host mmc0: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0)
[   38.195280] dwmmc_rockchip ff370000.dwmmc: Successfully tuned phase to 43

User avatar
odroid
Site Admin
Posts: 33649
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 500 times
Been thanked: 504 times
Contact:

Re: Shutdown process?

Unread post by odroid » Tue Jan 14, 2020 7:28 pm

@joy,

Nice findings!
Was the LCD backlight turned off in the suspend mode?

User avatar
rooted
Posts: 7335
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 494 times
Been thanked: 137 times
Contact:

Re: Shutdown process?

Unread post by rooted » Tue Jan 14, 2020 9:03 pm


joy wrote:I've checked very basic operation of suspend and it looks current rk3326 kernel configuration has suspend option already.

Code: Select all

$ systemctl suspend
(system enters into suspend here)
Then, by pressing power-key shortly, system comes back to idle.

But there are many things to check, like...
- network lost after suspend and resume (need to check suspend/resume state of all mandatory drivers)
- system keeps at the state after resume. but I got rockchip-dmc error event and (need to check ddr self-refresh mode works normally.)
- Not too much current advantage : 480mA -> 200mA :roll:
- and so on...
Haha I was just testing RTC sleep/wake.
rooted wrote:RTC sleep works but it breaks networking and sound, I guess the hardware isn't resetting.
@odroid When running this the screen does go off:

Code: Select all

sudo rtcwake -m mem -s 60
And the device wakes in 60 seconds, but you lose networking and sound when it wakes.

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Tue Jan 14, 2020 10:49 pm

rooted wrote:
Tue Jan 14, 2020 9:03 pm
Haha I was just testing RTC sleep/wake.
rooted wrote:RTC sleep works but it breaks networking and sound, I guess the hardware isn't resetting.
@odroid When running this the screen does go off:

Code: Select all

sudo rtcwake -m mem -s 60
And the device wakes in 60 seconds, but you lose networking and sound when it wakes.
Nice!!! :)
The result means basic PM operation on rk3326 works normally with RK817 pmic and RTC inside
and system resume from wake-up interrupt, too.
So now we need to check resume sequences (or suspend preparation routine) of the drivers
which work abnormally after resume like network and alsa drivers. ;)
Let's go on the next stage!
odroid wrote:
Tue Jan 14, 2020 7:28 pm
Was the LCD backlight turned off in the suspend mode?
@odroid,
Yes.
As @rooted says, LCD backlight goes off in suspend mode.
Some power rails and devices outside / IP blocks inside cpu may be still alive as your guess.

User avatar
rooted
Posts: 7335
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 494 times
Been thanked: 137 times
Contact:

Re: Shutdown process?

Unread post by rooted » Wed Jan 15, 2020 12:03 am


joy wrote: Nice!!! :)
The result means basic PM operation on rk3326 works normally with RK817 pmic and RTC inside
and system resume from wake-up interrupt, too.
So now we need to check resume sequences (or suspend preparation routine) of the drivers
which work abnormally after resume like network and alsa drivers. ;)
Let's go on the next stage!.
How are you monitoring power consumption, I'm guessing with the battery disconnected and a smart power?

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Wed Jan 15, 2020 7:49 am

rooted wrote:
Wed Jan 15, 2020 12:03 am
How are you monitoring power consumption, I'm guessing with the battery disconnected and a smart power?
No. Without battery connected to go advanced, I'm checking just current using a smart power that is connected to DC-jack in a temporary measure.
Last week, my DMM is dead. I will fix it.

kamots
Posts: 86
Joined: Sun Jul 01, 2018 6:05 am
languages_spoken: english
ODROIDs: ODROID-GO, C1+, ODROID-GO Advance
Has thanked: 16 times
Been thanked: 22 times
Contact:

Re: Shutdown process?

Unread post by kamots » Sat Jan 18, 2020 1:31 pm

Joy,

Do you want me to do any testing for you? I have a fairly good multimeter setup and the right equipment to put power monitoring in-line with a battery. I was planning on doing some power utilization testing anyway.

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Sat Jan 18, 2020 5:13 pm

Hi @kamots,
Before we check the whole power of board with current environment,
how about organizing available points that we can reduce power at, first,
then we need to measure each power consumption.
There are various conditions.

But surely, it will be very helpful if you check power monitoring in-line with a battery in case of (1) normal (2) suspend (3) after resume.
Thanks!

( This week I'm back in company office and I have another one there. Also I already ordered new one for my own. ;) )

kamots
Posts: 86
Joined: Sun Jul 01, 2018 6:05 am
languages_spoken: english
ODROIDs: ODROID-GO, C1+, ODROID-GO Advance
Has thanked: 16 times
Been thanked: 22 times
Contact:

Re: Shutdown process?

Unread post by kamots » Sat Jan 18, 2020 5:32 pm

Will do! I'll also check with minimum and maximum screen brightness as well.

kamots
Posts: 86
Joined: Sun Jul 01, 2018 6:05 am
languages_spoken: english
ODROIDs: ODROID-GO, C1+, ODROID-GO Advance
Has thanked: 16 times
Been thanked: 22 times
Contact:

Re: Shutdown process?

Unread post by kamots » Mon Jan 20, 2020 9:00 pm

First set of results (using reference build image but AreaScout PPSSPP)....

Image



Note for everyone that brightness ranges from 0 (off) to 255 (max). I'll do more brightness level testing later.

You guys may want to adjust the mA numbers on the wiki and web site as they say under 200mA for gaming which is not accurate. Ameridroid also copied that. The 250mA to 350mA original numbers were closer.

Clearly pushing the CPU and GPU uses a pretty decent amount of power. PPSSPP uses 2 CPU cores and certainly pushes the GPU.
These users thanked the author kamots for the post (total 2):
rooted (Tue Jan 21, 2020 3:13 am) • joy (Tue Jan 21, 2020 5:41 pm)

kamots
Posts: 86
Joined: Sun Jul 01, 2018 6:05 am
languages_spoken: english
ODROIDs: ODROID-GO, C1+, ODROID-GO Advance
Has thanked: 16 times
Been thanked: 22 times
Contact:

Re: Shutdown process?

Unread post by kamots » Mon Jan 20, 2020 11:25 pm

To be clear, these tests were done in-line with the battery. The results show what is pulled out of the battery during these use cases. Wiring between the battery and the board was under 12cm to avoid voltage drop during testing.
These users thanked the author kamots for the post (total 2):
odroid (Tue Jan 21, 2020 10:10 am) • joy (Tue Jan 21, 2020 5:44 pm)

User avatar
rooted
Posts: 7335
Joined: Fri Dec 19, 2014 9:12 am
languages_spoken: english
Location: Gulf of Mexico, US
Has thanked: 494 times
Been thanked: 137 times
Contact:

Re: Shutdown process?

Unread post by rooted » Tue Jan 21, 2020 3:15 am


kamots wrote:First set of results (using reference build image but AreaScout PPSSPP)....

Image



Note for everyone that brightness ranges from 0 (off) to 255 (max). I'll do more brightness level testing later.

You guys may want to adjust the mA numbers on the wiki and web site as they say under 200mA for gaming which is not accurate. Ameridroid also copied that. The 250mA to 350mA original numbers were closer.

Clearly pushing the CPU and GPU uses a pretty decent amount of power. PPSSPP uses 2 CPU cores and certainly pushes the GPU.
Did you have wireless powersave disabled? If not would you test that also?

And test with WiFi dongle in but not connected to an AP?

User avatar
odroid
Site Admin
Posts: 33649
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 500 times
Been thanked: 504 times
Contact:

Re: Shutdown process?

Unread post by odroid » Tue Jan 21, 2020 10:20 am

@kamots,
Thank you for the detail test.
I've updated the specification to 250 ~ 500mA.
These users thanked the author odroid for the post:
kamots (Tue Jan 21, 2020 5:19 pm)

kamots
Posts: 86
Joined: Sun Jul 01, 2018 6:05 am
languages_spoken: english
ODROIDs: ODROID-GO, C1+, ODROID-GO Advance
Has thanked: 16 times
Been thanked: 22 times
Contact:

Re: Shutdown process?

Unread post by kamots » Tue Jan 21, 2020 5:23 pm

rooted wrote:
Tue Jan 21, 2020 3:15 am
Did you have wireless powersave disabled? If not would you test that also?

And test with WiFi dongle in but not connected to an AP?
I didn't have wireless powersave disabled. I was using the ODROID-branded WiFi adapter. I can do more testing later on, the most important numbers were the emulation numbers and the suspend results.

I am also testing other WiFi adapters but not having much luck so far. Ideally I want to get one of the combo Bluetooth+WiFi ones working to give people more connectivity in one device.

joy
Posts: 1148
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 82 times
Been thanked: 129 times
Contact:

Re: Shutdown process?

Unread post by joy » Tue Jan 21, 2020 5:47 pm

@kamots,
Thank you so much for your tests.
It's very useful and detailed and can be a reference for our further progress for system suspend mode. :D

kamots
Posts: 86
Joined: Sun Jul 01, 2018 6:05 am
languages_spoken: english
ODROIDs: ODROID-GO, C1+, ODROID-GO Advance
Has thanked: 16 times
Been thanked: 22 times
Contact:

Re: Shutdown process?

Unread post by kamots » Tue Jan 21, 2020 8:12 pm

https://www.amazon.com/gp/product/B01KVZB3A4/

Got this one working. Will hopefully have the drivers loaded as part of the default image when shipments start :)

@joy,
Anytime, let me know if you need anything else. I have some fairly expensive test gear I can use to get more information.
These users thanked the author kamots for the post:
joy (Thu Jan 23, 2020 10:03 am)

User avatar
Etx
Posts: 51
Joined: Mon Jan 20, 2020 9:10 am
languages_spoken: english, chinese, russian, ukrainian
ODROIDs: ODROID-GO Advance
Has thanked: 0
Been thanked: 8 times
Contact:

Re: Shutdown process?

Unread post by Etx » Wed Jan 22, 2020 12:25 am

Do you boast of the high cost of equipment? Lol. The measurements that you've made don't need any expensive equipment. Almost any inexpensive multimeter will do the job fine.

kamots
Posts: 86
Joined: Sun Jul 01, 2018 6:05 am
languages_spoken: english
ODROIDs: ODROID-GO, C1+, ODROID-GO Advance
Has thanked: 16 times
Been thanked: 22 times
Contact:

Re: Shutdown process?

Unread post by kamots » Wed Jan 22, 2020 2:47 am

No, because much of it I don't own, I simply have access and use of it. I have a good multimeter which is my best personal test gear. I wanted to express that I have the capabilities of doing more then just volts/amps testing if needed.

Post Reply

Return to “General Topics”

Who is online

Users browsing this forum: No registered users and 2 guests