ChanServ changed the topic of #linux-msm to:
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
jhovold has joined #linux-msm
srinik has quit [Killed (NickServ (Too many failed password attempts.))]
srinik has joined #linux-msm
<z3ntu> Anyone have a suggestion how to handle btqca firmware names for new bluetooth chip that doesn't seem to follow existing naming guidelines with rom_ver?
<z3ntu> Based on downstream code these combos of the soc version, product id & rom version need the following firmware:
<z3ntu> So basically seems last bit of rom_ver seems to say whetver to use 10 or 11 in the filename
<z3ntu> So instead of `rom_ver = ((soc_ver & 0x00000f00) >> 0x04) | (soc_ver & 0x0000000f);` I could use `rom_ver = ((soc_ver & 0x00000f00) >> 0x05) | (soc_ver & 0x0000000f);` (so shift the left byte one more to the right)
pespin has joined #linux-msm
svarbanov has joined #linux-msm
svarbanov_ has quit [Read error: Connection reset by peer]
<aka_[m]> konradybcio: if icc driver supposed to be core_initcall shouldn't drivers like hfpll.c/apcs-msm8916.c also be?
jhovold has quit [Ping timeout: 480 seconds]
jnn has joined #linux-msm
jn has quit [Ping timeout: 480 seconds]
pespin has quit [Remote host closed the connection]
svarbanov has quit [Ping timeout: 480 seconds]
<konradybcio> having cpufreq very early on would be nice i guess
<konradybcio> interconnect is (supposed to be) a hard dependency for almost all other devices