ChanServ changed the topic of #linux-msm to:
davidinux is now known as Guest5814
davidinux has joined #linux-msm
Guest5814 has quit [Ping timeout: 480 seconds]
Danct12 is now known as Guest5820
Danct12 has joined #linux-msm
cmeerw[m] has quit []
marvin24 has joined #linux-msm
marvin24_ has quit [Ping timeout: 480 seconds]
Guest5820 has quit [Remote host closed the connection]
vireshk has joined #linux-msm
vireshk has left #linux-msm [Leaving]
pespin has joined #linux-msm
Caterpillar has joined #linux-msm
junari has joined #linux-msm
junari_ has joined #linux-msm
junari has quit [Ping timeout: 480 seconds]
<ungeskriptet> Is it possible to make just one half of the panel work for now? So that I can ignore the dual DSI stuff and make it work later
<konradybcio> depends on your panel.. if you unteach all drivers about dsi1, half of it could work
<ungeskriptet> With the reset function removed I can see somewhat readable kernel log at the top. With the reset function the whole panel flashes green
junari_ has quit [Ping timeout: 480 seconds]
junari has joined #linux-msm
Danct12 has quit [Quit: WeeChat 4.0.0]
bhsharma- has joined #linux-msm
mani_s- has joined #linux-msm
bhsharma- has quit [Quit: ZNC 1.7.2 - https://znc.in]
mani_s- has quit []
bhsharma- has joined #linux-msm
mani_s- has joined #linux-msm
Danct12 has joined #linux-msm
junari_ has joined #linux-msm
junari has quit [Ping timeout: 480 seconds]
<konradybcio> djakov: hey, could you take a look at this gianormous patchset of mine that's been waiting for quite some time? https://lore.kernel.org/linux-arm-msm/20230526-topic-smd_icc-v7-0-09c78c175546@linaro.org/
<konradybcio> I think it should all go through qcom (if you don't object) due to the cross-dependencies
<bamse> djakov: would you be okay with acking the interconnect patches, then i can merge the whole series into an immutable branch and share that back with you?
junari_ has quit [Ping timeout: 480 seconds]
<djakov> konradybcio: hey, i looked at them i they look good. there a a few minor nits like spelling etc, but it's not worth doing another version just for this so let's get this merged as is.
<djakov> bamse: yes i was also thinking that an immutable branch would be best
<konradybcio> djakov thanks!
davidinux has quit [Ping timeout: 480 seconds]
<DylanVanAssche> @bamse I'm looking at the WCN3990 WiFi/Bluetooth module to have Bluetooth HFP working. For some reason the hardware declares it has no support for HFP to BlueZ, is that intended?
<bamse> DylanVanAssche: i don't know the details, feels odd that it would advertise that...that said, i believe the handset/headset profile uses a dedicated audio path, which isn't supported...i think that's where i ran into problems
<DylanVanAssche> bamse: Well it just never advertise HFP but does A2DP, the latter does not require the Bluetooth SCO stuff and can be done fully in software.
<DylanVanAssche> bamse: I found references in downstream to `INT_BT_SCO` things which is the Bluetooth HFP audio routing, but the first step would be that the controller even advertises support for HFP to even start routing audio to it.
<bamse> DylanVanAssche: i was able to get it into that state, but i'm afraid i don't know what i did or if anything has changes...
<bamse> changed*
<DylanVanAssche> bamse: Oh so it is really possible... Hmmmm. The thing I'm not sure of if the chip uses a bunch of QMI things as well here or only for the WiFi part.
<bamse> i don't think there's any qmi for the bt-side of things
<bamse> DylanVanAssche: fwiw it was on the lenovo yoga c630 that i was playing around with this...
<bamse> DylanVanAssche: ended up buying a decent usb microphone and used that together with a2dp...putting the remainder on the backburner
<DylanVanAssche> bamse: I saw in the audio routing that there were commands with AFE or something that set the number of channels, sample rate, etc. so I guess no QMI. Do you remember of playing with the audio routing to get into the state or not at all?
<DylanVanAssche> Well I would love to get calling working over HFP, used a lot in cars. I have the AT commands working so you can control calls from the car multimedia thing, just no audio yet
<bamse> no, i got the bt-side working, but never looked into the audio routing...so whatever came out was (bad) noise
<DylanVanAssche> Ah so it is probably another piece of the puzzle, I thought the audio routing would trigger something in the firmware to advertise support, guess not 😛
<bamse> if you get to the audio-part of the problem, check with srinik
<bamse> well, i can't rule that out...might have had a broken configuration that provided some state that was considered a working link...i don't know
<DylanVanAssche> I'm a bit confused in mainline what driver is actually driving this chip now. There's hci_qca which does the HCI specifics for Qualcomm stuff, but is there anything else? That driver does not have much regarding profiles etc. mostly firmware loading etc.
<bamse> the driver is split between hci_qca.c and btqca.c
<DylanVanAssche> Thanks! That makes my life so much easier 🙂
jhovold has quit [Ping timeout: 480 seconds]
Caterpillar has quit [Quit: Konversation terminated!]
pespin has quit []