JohnDoe_71Rus has quit [Ping timeout: 256 seconds]
klokken has quit [Remote host closed the connection]
klokken has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
nlhowell has joined #linux-rockchip
nlhowell has quit [Quit: WeeChat 2.8]
nlhowell has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
vicencb has joined #linux-rockchip
damex has joined #linux-rockchip
damex_ has quit [Ping timeout: 272 seconds]
matthias_bgg has quit [Ping timeout: 272 seconds]
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 264 seconds]
omegamoon[m] has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
<sphalerite>
How does linux know how to control the PWM backlight in gru chromebooks (ref. pwm-backlight in rk3399-gru-chromebook.dtsi)? I see that in rk3288-veyron.dtsi the pwm-backlight node has a "pwms" property, but the gru one doesn't
<sphalerite>
aaah got it. It's set in more specific device tree files — in my case, rk3399-gru-bob.dts