mszyprow|home has joined #linux-exynos
libv_ has joined #linux-exynos
libv_ is now known as libv
libv has quit [*.net *.split]
nashpa has quit [*.net *.split]
dlezcano has quit [*.net *.split]
wiewo has quit [*.net *.split]
wiewo has joined #linux-exynos
nashpa has joined #linux-exynos
dlezcano has joined #linux-exynos
libv has joined #linux-exynos
<Viciouss> I'm trying to use the pwm-backlight with a galaxy note 10.1 (exynos 4412) and it works almost fine, except when I echo the maximum brightness into the sysfs node, this makes the display go dark. what could be the reason for this? I also tried setting the pwm gpio to 0x3 which is LCD_PWM in the manual but then the display doesn't work at all
<Viciouss> using kernel 5.8.x
<krzk> Viciouss: so 0 and 255 are dark?
<krzk> Viciouss: you could try with different drive strengths for this GPIO, or check whether regulator has proper values
libv has quit [Read error: Connection reset by peer]
libv has joined #linux-exynos
snawrocki has joined #linux-exynos
aballier has quit [Ping timeout: 264 seconds]
genii has joined #linux-exynos
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-exynos
<Viciouss> krzk: exactly, 0 and 255 are dark. I tried different drive strengths now but the result is the same. about the regulator, I'm not sure how the backlight is actually supplied. the display is mostly managed via mdnie in the old kernel and there are quite some magic numbers involved which I don't understand
mszyprow|home has quit [Ping timeout: 240 seconds]
mszyprow|home has joined #linux-exynos
<Viciouss> I also tried other periods but as soon as the duty % is at 100, the backlight turns off
Ultrasauce has quit [Quit: Ultrasauce]
Ultrasauce has joined #linux-exynos
_whitelogger has joined #linux-exynos
libv has quit [Ping timeout: 256 seconds]
genii has quit [Quit: See you soon.]
libv has joined #linux-exynos
libv has quit [Ping timeout: 260 seconds]