narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki - ml - Publicly Logged on
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #linux-amlogic
jakogut has quit [Quit: jakogut]
jakogut has joined #linux-amlogic
jakogut has quit [Remote host closed the connection]
jakogut has joined #linux-amlogic
vagrantc has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
_vaibhavingale_ has joined #linux-amlogic
_vaibhavingale_ has quit [Quit: Leaving.]
<lvrp16> list?
<lvrp16> i am not using the latest u-boot, i will update and check
fedux has quit [Quit: fedux]
mykdelta has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
fedux has joined #linux-amlogic
fedux has quit [Client Quit]
fedux has joined #linux-amlogic
fedux has quit [Quit: fedux]
fedux has joined #linux-amlogic
return0e has joined #linux-amlogic
return0xe has joined #linux-amlogic
return0e has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
<xdarklight> narmstrong: you mentioned that CLK_OF_DECLARE_DRIVER is being deprecated. do you have any reference for that? (I wanted to update my "clk: meson: meson8b: register the clock controller early" patch, but I couldn't find any reference how I am supposed to register the clock controller driver with core_initcall - all examples I found are simply registering it as platform device, which doesn't work as the driver itself is then probed too
<xdarklight> late which is what I'm trying to fix)
<xdarklight> while looking at it I also found that I can switch from CLK_OF_DECLARE_DRIVER to CLK_OF_DECLARE (the former is only needed when there's "early initialization" and a platform driver, which won't be the case anymore after my patch - the latter only handles early registration)
mykdelta has quit [Ping timeout: 276 seconds]