narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - Publicly Logged on https://irclog.whitequark.org/linux-amlogic
[TheBug] has quit [Ping timeout: 260 seconds]
[TheBug] has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 256 seconds]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
Barada has joined #linux-amlogic
ldevulder has joined #linux-amlogic
yann|work has quit [Ping timeout: 240 seconds]
a5m has joined #linux-amlogic
yann|work has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-amlogic
afaerber has quit [Client Quit]
<narmstrong> xdarklight: it booted on a s805x with no changes except the DT a pushed : [ 12.340274] soc soc0: Amlogic Meson GXL (Unknown) Revision 21:b (32:2) Detected
<xdarklight> narmstrong: nice - congrats :)
<xdarklight> narmstrong: does the lima driver also load (and does it render something for you)?
<narmstrong> xdarklight: did not test yet
<narmstrong> usb works
<xdarklight> at least something :)
<narmstrong> I'll need to check vdec and mali
<narmstrong> but there is no sdcard, so it's less easier to test :-)
<xdarklight> heh :)
<narmstrong> but with mainline u-boot, I can boot from USB ;-)
<xdarklight> :)
afaerber has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
sputnik_ has quit [Ping timeout: 260 seconds]
Barada has quit [Quit: Barada]
a5m has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik__ has quit [Read error: Connection reset by peer]
return0e has quit [Remote host closed the connection]
afaerber has quit [Quit: Leaving]
yann|work has quit [Ping timeout: 260 seconds]
vagrantc has joined #linux-amlogic
sputnik_ has quit [Read error: Connection reset by peer]
sputnik_ has joined #linux-amlogic
yann|work has joined #linux-amlogic
fedux_ has quit [Ping timeout: 245 seconds]
fedux has joined #linux-amlogic
nemunaire has quit [Ping timeout: 256 seconds]
nemunaire has joined #linux-amlogic
return0e has joined #linux-amlogic
return0e has quit [Remote host closed the connection]
vagrantc has quit [Ping timeout: 265 seconds]
<xdarklight> narmstrong: I think it would make sense to use CCF for clkmsr now that jbrunet's patchset almost allows exposing GEN_CLK (except for wiring up the clkmsr bit in the mux)
<xdarklight> what do you think?
<jbrunet> xdarklight: we've talked about it but it going take some thinking. Not all clock in clock measure exist in ccf.
<jbrunet> Sure it is a good idea, maybe as a second step ?
<xdarklight> jbrunet: can you give me some more details what you discussed? Neil's current suggestion is basically a flat list of clock measurements in debugfs, can't we do the same with CCF (for example: we have "clk81" which is managed by CCF, and we couuld have a clkmsr_clk81 which is read-only and obtained from clkmsr)?
<xdarklight> obtained = rate and accuracy are obtained from clkmsr
<xdarklight> using debugfs would work too, I just want to understand the "why"
vagrantc has joined #linux-amlogic
<jbrunet> xdarklight: there is not much more than that :) just that debugfs (as proposed - with clock that don't exist in ccf) could be useful, integration with ccf could also be nice to have. Perf counters is another idea
<jbrunet> Just thinking that ccf and perf could be done later on ... Debugfs is a good start IMHO
Guest19588 has quit [Ping timeout: 264 seconds]
vagrantc has quit [Ping timeout: 265 seconds]
mag has joined #linux-amlogic
mag is now known as Guest17345
Guest17345 is now known as mag
<jbrunet> Ohhh I understand (sorry I'm bit slow tonight) ... You are wondering why we need debugfs at all, and why not rely only on ccf ? Right ?
<xdarklight> jbrunet: yep, to me it looks like a duplication of what CCF provides - but then again, I might have missed something
<jbrunet> It is worth considering
<jbrunet> I'm bit concerned about how it will behave with ccf. Measuring a clock takes tens of uS
<jbrunet> Might be too much when ccf update the tree
<xdarklight> if that's really the case then I'm completely fine with debugfs (I don't know much about the perf framework, so I can't comment on that)
<xdarklight> that == being too slow when CCF updates it's tree
<jbrunet> Need to check it is a problem
<jbrunet> If
fedux has quit [Quit: fedux]
vagrantc has joined #linux-amlogic
vagrantc has quit [Ping timeout: 256 seconds]
fedux has joined #linux-amlogic
trem has joined #linux-amlogic
fedux has quit [Ping timeout: 240 seconds]
fedux has joined #linux-amlogic
fedux has quit [Ping timeout: 240 seconds]
fedux has joined #linux-amlogic
fedux has quit [Client Quit]
return0e has joined #linux-amlogic
vagrantc has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
vagrantc has quit [Ping timeout: 276 seconds]
vagrantc has joined #linux-amlogic
fedux has joined #linux-amlogic
trem has quit [Quit: Leaving]
fedux has quit [Client Quit]
fedux has joined #linux-amlogic
afaerber has joined #linux-amlogic
yann|work has quit [Ping timeout: 265 seconds]
return0e has quit [Remote host closed the connection]
ldevulder has quit [Ping timeout: 265 seconds]
sputnik_ has joined #linux-amlogic
return0e has joined #linux-amlogic
return0e has quit [Read error: Connection reset by peer]
return0e has joined #linux-amlogic
return0e has quit [Client Quit]
return0e has joined #linux-amlogic