krzk changed the topic of #linux-exynos to: Samsung S3C24xx and S3C64xx planned deprecation and removal (see LKML) | Linux Samsung SoC Exynos | https://exynos.wiki.kernel.org | This channel is logged: https://libera.irclog.whitequark.org/linux-exynos
mszyprow has joined #linux-exynos
mszyprow has quit [Ping timeout: 256 seconds]
adjtm has quit [Quit: Leaving]
Viciouss has left #linux-exynos [The Lounge - https://thelounge.chat]
<Grimler_> For some regulators in for example exynos5422-odroid-core we are setting regulator-always-on, followed by regulator-state-mem { regulator-off-in-suspend; }, does this make sense? Sounds a bit contradictory, but not only exynos does this (some rockchip devices and a few devices from other brands does it as well) so I suppose it is alright(?)
Viciouss has joined #linux-exynos
<Grimler_> regulator driver seem to handle them independently so I guess regulator-always-on means that regulator should be always on, except perhaps when suspended
chewitt has joined #linux-exynos
<krzk> Grimler_: AFAIK, regulator-always-on does not have to mean it will be on in suspend. always-on rather refers to not allowed to disable the regulator during running, but suspend might have its own setting.
<Grimler_> krzk: alright, thanks
Viciouss has quit [Quit: Ping timeout (120 seconds)]
Viciouss has joined #linux-exynos
mszyprow has joined #linux-exynos
mszyprow has quit [Ping timeout: 268 seconds]
mszyprow has joined #linux-exynos
mszyprow^home has joined #linux-exynos
mszyprow has quit [Ping timeout: 240 seconds]
mszyprow^home has quit [Ping timeout: 256 seconds]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-exynos