Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
jhovold has joined #linux-msm
Daanct12 has quit [Quit: Leaving]
pevik has joined #linux-msm
abhinav__ has quit [Quit: Ping timeout (120 seconds)]
abhinav__ has joined #linux-msm
jessica_24 has quit [Quit: Ping timeout (120 seconds)]
bhsharma has quit [Read error: Connection reset by peer]
jessica_24 has joined #linux-msm
bhsharma has joined #linux-msm
gpiccoli has quit [Quit: Bears...Beets...Battlestar Galactica]
gpiccoli has joined #linux-msm
<Marijn[m]>
lumag: You want a spreadsheet with contributors mapped to SoC they own? Could be useful in general for testing :)
<lumag_>
Marijn[m], well, I was thinking about something closer to old Arnd's arm-soc or to Debian's arch qualification tables. Which SoCs have been updated to use DT clocks (and who is caring about the conversion). But you might evolve this idea as you see fit
<Mis012[m]>
wait, so converting msm-clk to using DT clocks is in the cards?
<Marijn[m]>
lumag: That sounds like a better idea, I don't think everyone wants to share exactly what hardware they have access to, and list if it's (in)convenient for them to perform tests. Let's have a table about the current status-quo instead
<Marijn[m]>
Mis012: We've already converted some drivers and new clock drivers are hopefully rejected if they rely on global names instead of being converted to DT
pespin has joined #linux-msm
<Mis012[m]>
Marijn: wouldn't that need rewriting the msm-clk core?
<Mis012[m]>
to do it like e.g omap
<Mis012[m]>
`compatible = "qcom,fabia-pll"`
<Marijn[m]>
Mis012: I don't have any `msm-clk` in my tree, what specifically are you referring to?
<Mis012[m]>
clk-msm?
<Mis012[m]>
I always forget which driver is which way around
<Marijn[m]>
If it isn't obvious, we're referring to `gcc` and related drivers (dsi phy, dispcc, etc) still using hardcoded clock names instead of reading the dependency from the tree
<Mis012[m]>
oh, I thought you were talking about different hardcoded things that should in the device tree
<Mis012[m]>
this for example looks like prime device tree material
<Marijn[m]>
Mis012: You mean specifically pulling gplls out of the gcc driver, or every individual clock branch?
<Mis012[m]>
every individual clock branch
<Mis012[m]>
you could argue that it's more organized like this, but technically it belongs in the dt based on general principles of what goes in the dt :P
<Mis012[m]>
I would expect this kind of hardcoding on ACPI systems because ACPI sucks, not sure if it's doable with the ACPI devicetree frankenstain spec but noone uses that anyway because Windows doesn't support it (afaik)