<javier__>
wwilly: yes, that seems correct. I would add it in your dts and not the common dtsi since is only used in your board but shoulnd't make a dif
<javier__>
wwilly: same error?
<wwilly>
w1-gpio onewire_device: could not find pctldev for node /my-w1-pin, deferring probe
<javier__>
wwilly: in your first DTS is cleary why it fails, because the pinctrl config node doesn't have the proper pin controller parent. But in the second one I don't see why it would fail
<wwilly>
uhm ok
<wwilly>
do you know a pinctrl's guru that I could annoye to help me write this?
<javier__>
wwilly: it doesn't have to be a pinctrl guru, this is a very simple thing to do. Maybe I'm missing something obvious in your DTS but I don't see what could cause your issue
<javier__>
in principle, a resource not being available by the time is looked up is not an issue since it just causes the driver's probe to defer and latter when another driver registers it, it's re-tried
<javier__>
but in the case of the pinctrl drivers, these usually are registered in a very early initcall level so should be available by the time the drivers are probed
<wwilly>
when you say look at pinctrl/devicetree, you mean put some printk to trace what happend?
<javier__>
I'm testing with today's next so it should be about the same
<wwilly>
....... Problem Exists Between Keyboard And Chair
<wwilly>
since I git commit, the image isn't marked as dirty.... and then I booted the prior kernel
<wwilly>
......
<wwilly>
damn, I owe you a beer
<javier__>
wwilly: no worries, I'm glad that I could be of any help :)
paulk-blaze has quit [Quit: Leaving]
Vasco_O is now known as Vasco
Vasco has quit [Quit: changing servers]
Vasco has joined #linux-exynos
Vasco has quit [Max SendQ exceeded]
Vasco has joined #linux-exynos
Vasco has quit [Max SendQ exceeded]
Vasco has joined #linux-exynos
Vasco has quit [Max SendQ exceeded]
Vasco has joined #linux-exynos
Vasco has quit [Max SendQ exceeded]
Vasco has joined #linux-exynos
Vasco has quit [Max SendQ exceeded]
Vasco has joined #linux-exynos
Vasco has quit [Client Quit]
Vasco has joined #linux-exynos
Vasco has quit [Max SendQ exceeded]
wwilly has quit [Quit: Leaving]
wwilly has joined #linux-exynos
wwilly has quit [Quit: Leaving]
beeno has quit [Ping timeout: 260 seconds]
aballier has quit [Ping timeout: 264 seconds]
aballier has joined #linux-exynos
ssvb has joined #linux-exynos
leandrosansilva has joined #linux-exynos
LiquidAcid has joined #linux-exynos
paulk-collins has joined #linux-exynos
afaerber has quit [Quit: Leaving]
Vasco_O has joined #linux-exynos
<LiquidAcid>
can someone confirm that the exynos mixer internally works with YCbCr?
<LiquidAcid>
i did a bit of reverse engineering with the magic numbers if mixer_cfg_rgb_fmt() and they appear to be a rgb-to-yuv conversion matrix (the default values of the registers as well)