Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-msm
Daanct12 has quit [Remote host closed the connection]
<mort_>
I have an apq8016, somehow audio stuff just doesn't show up *at all* after a kernel upgrade. The config should be correct, CONFIG_SND_SOC_LPASS_APQ8016=m, CONFIG_SND_SOC_APQ8016_SBC=m, CONFIG_SND=y. My devicetree should be correct
<mort_>
is there anything I can do to debug why this doesn't work? Any more information I can provide?
<mort_>
on a 4.9 kernel, where I do have working sound, I see messages from qcom-apq8016-sbc 7702000.sound during boot, but I don't with the 5.10 kernel I'm trying to upgrade to
<mort_>
the 4.9 dts I've been using, which works, doesn't have a external-dai-link@0, even though the upstream apq8016-sbc.dtsi does have an external-dai-link@0, so I'm guessing it doesn't apply to this hardware
<mort_>
I think the biggest thing I'm surprised by is that there's no messages at all in dmesg from apq8016_sbc_sndcard, despite there being a status=okay devicetree node with it as its compatible string
<vknecht[m]>
which compatible ? not `qcom,sbc` by chance ?
<vknecht[m]>
could check with lsmod whether modules are loaded or not, and try loading them manually if not
<mort_>
I'm digging into the driver, seems like probing always exits with an error. Adding debug prints to figure out why. Will come back to it tomorrow but I at least have a direction to go now
<aka_[m]>
weird because i can recall sm6115 not having such issues?
<aka_[m]>
glink vs smd issue?
<konradybcio>
if it's a new dt, you should probably pass it to rpmcc via dt
<konradybcio>
and then use the rpm clock
<konradybcio>
legacy lookup will work too but that's not prefered
<konradybcio>
thinking about it, gotta resend 6375 with that
<aka_[m]>
you know i mean 8976 dtsi
<aka_[m]>
in theory i can just use xo_board into rpmcc
<aka_[m]>
and replace rest of xos with rpmcc
<aka_[m]>
but one has to stay
<konradybcio>
that's what your'e supposed to do
<aka_[m]>
but in theory its wrong
<aka_[m]>
because we shouldn't expose xo like that
<aka_[m]>
its not separate
<konradybcio>
what do you mean 'expose'?
<aka_[m]>
i mean fixed-clock
<konradybcio>
xo as in the physical crystal oscillator feeds the rpm xo clock
<konradybcio>
which actually feeds the rest of the soc
<konradybcio>
there's some pmic clock mess along the way but it doesn't really matter
<z3ntu>
I'm actually not aware of any separate crystal being somewhere on the board, or at least it's never mentioned on any schematic. Doesn't pmic have this stuff included in the package?
<aka_[m]>
its part of pm
<aka_[m]>
lines get out and its connected to various blocks